[issue13991] namespace packages depending on order

Brett Cannon added the comment: It's not working because when you import a.b you calculate __path__ at import time, so when you modify sys.path it won't make a difference since import will look at a.__path__ after your a.b import and simply ignore sys.path. But when you put everything on sys.

[issue13991] namespace packages depending on order

Changes by andrea crotti : -- resolution: invalid -> ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue13991] namespace packages depending on order

andrea crotti added the comment: I reopen the ticket because I'm still not convinced.. I tried to substitute the setuptools namespace declaration with the more standard python: from pkgutil import extend_path __path__ = extend_path(__path__, __name__) It behaves exactly in the same way, whic

[issue13991] namespace packages depending on order

andrea crotti added the comment: About the binary file, in theory I agree with you, but that archive contains 5 or 6 subdirectories with a few almost empty files. Of course I can write a script that recreates that situation, but does it make sense when I can just tar and untar it? And what sh

[issue13991] namespace packages depending on order

Éric Araujo added the comment: > There is nothing binary in the archive The archive is a binary file. We tend to dislike those because we need to download and process them instead of just reading them in a browser tab, and in some cases (Windows .exe files) there are also security reasons. I

[issue13991] namespace packages depending on order

andrea crotti added the comment: There is nothing binary in the archive, just a simple example of namespace packages, which was the minimal example that I could create to make things fail. I use the standard pkg_resources way to do things: __import__('pkg_resources').declare_namespace(__name__

[issue13991] namespace packages depending on order

Éric Araujo added the comment: Are you using pure-stdlib namespace packages, i.e. things using distutils and pkgutil.extend_path, or setuptools’ notion of namespace packages? (I didn’t check your archive, in general we dislike binary files on this tracker and use text all the time.) ---

[issue13991] namespace packages depending on order

Changes by Eric Snow : -- nosy: +eric.snow ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue13991] namespace packages depending on order

New submission from andrea crotti : I am not really sure that it is a bug, but for me it's at least not the expected behaviour. In short supposing I have two namespace packages ab and ac (as seen in the tar file), this works perfectly: import sys from os import path sys.path.append(path.abspat