[issue15434] __import__() problem in 3.3

Brett Cannon added the comment: The a/b case is legitimate in Python 3.3; namespace packages are delineated by not defining an __init__.py file. Closing as invalid. -- resolution: -> invalid status: open -> closed ___ Python tracker

[issue15434] __import__() problem in 3.3

Stefan Krah added the comment: Argh. __init__.py was missing in the top directory. For some reason Python 3.2 does not throw the error. Also, 3.3 does not raise in the case of the a/b directory structure: $ tree a a `-- b |-- __init__.py `-- xyz.py $ ~/usr/bin/python3.3 a/b/__init__.py

[issue15434] __import__() problem in 3.3

Changes by Chris Jerdonek : -- nosy: +cjerdonek ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue15434] __import__() problem in 3.3

Brett Cannon added the comment: It might be a runpy thing as Nick has been tweaking that lately to deal with pkgutil issues. And this is of course ignoring the fact that __import__ should never be called directly over importlib.import_module(). -- nosy: +ncoghlan ___

[issue15434] __import__() problem in 3.3

Stefan Krah added the comment: This is not a distutils issue. I want to know why this does not throw an exception ... python3.2 distutils/command/__init__.py ... while this raises ImportError: ~/usr/bin/python3.3 distutils/command/__init__.py For the path structure please see my previous

[issue15434] __import__() problem in 3.3

Éric Araujo added the comment: Could you explain what is it you’re trying to achieve? -- ___ Python tracker ___ ___ Python-bugs-list

[issue15434] __import__() problem in 3.3

Changes by Brett Cannon : -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue15434] __import__() problem in 3.3

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue15434] __import__() problem in 3.3

Stefan Krah added the comment: It looks like distutils/command from the stdlib is searched first despite the fact that the first path entry is '/home/stefan/tmp'. If distutils/command is replaced with a/b, the import works: $ pwd /home/stefan/tmp $ $ ls a/b/ __init__.py xyz.py $ ls distutils

[issue15434] __import__() problem in 3.3

New submission from Stefan Krah : Using b127046831e2, I'm experiencing an import problem during the NumPy build. I've reduced it to this scenario, which works in 3.2 but not in 3.3. Note that in NumPy's setup.py, the equivalent of /home/stefan/tmp is the first entry in sys.path. I'm not sure if