Message166230
| Author |
skrah |
| Recipients |
Arfrever, brett.cannon, chris.jerdonek, eric.araujo, ncoghlan, pitrou, skrah |
| Date |
2012年07月23日.15:52:33 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1343058754.54.0.929461822705.issue15434@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
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
['/home/stefan/tmp', '/home/stefan/tmp/a/b', '/home/stefan/usr/lib/python33.zip', '/home/stefan/usr/lib/python3.3', '/home/stefan/usr/lib/python3.3/plat-linux', '/home/stefan/usr/lib/python3.3/lib-dynload', '/home/stefan/.local/lib/python3.3/site-packages', '/home/stefan/usr/lib/python3.3/site-packages']
With the added __init__.py, also the (fake) distutils package is OK:
$ tree distutils/
distutils/
|-- __init__.py
`-- command
|-- __init__.py
`-- xyz.py
$ ~/usr/bin/python3.3 distutils/command/__init__.py
['/home/stefan/tmp', '/home/stefan/tmp/distutils/command', '/home/stefan/usr/lib/python33.zip', '/home/stefan/usr/lib/python3.3', '/home/stefan/usr/lib/python3.3/plat-linux', '/home/stefan/usr/lib/python3.3/lib-dynload', '/home/stefan/.local/lib/python3.3/site-packages', '/home/stefan/usr/lib/python3.3/site-packages']
Brett, if this all looks good to you, this issue can be closed. The
original NumPy build error must be due to something else.
Perhaps 3.3 should raise in the a/b case, too? |
|