Thank you Michael, the fact is, I started with Python 2.7 some 4-5 years ago, and migrated to 3.x around mid-2015. The incriminated __init__.py contains only the following lines, as per instructions I had found somewhere (can't remember where):
> # this is a namespace package > from pkgutil import extend_path > __path__ = extend_path(__path__, __name__) I'll try to get rid of it entirely, as I don't wish to maintain Python 2.x compatibility. I like to burn my bridges sometimes ;) Thanks again, Laurent. > If the package has code in its `__init__.py` then it is no longer a real > namespace package and I think you've been getting "lucky" for this long > probably due to the order in which the packages were installed. A > namespace package is a grouping of submodules/subpackages, but the > top-level module in the package should always be empty and / or > identical to the module in every separately-distributed copy of that > file. Normally this means the file would just include a namespace > declaration required to make setuptools work, although in py3 you can > apparently get rid of the file entirely (meaning you shouldn't assume > you can put code in there). -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/427a7faa-812e-4d54-3e2f-1c1a88e9563a%40gmail.com. For more options, visit https://groups.google.com/d/optout.
