Author paul.moore
Recipients georg.brandl, paul.moore
Date 2014-02-13.20:50:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1392324636.47.0.967775665476.issue20621@psf.upfronthosting.co.za>
In-reply-to
Content
There appears to be a significant issue with importing from zip files on Python 3.3.4. I have tested this on Windows 7, 64-bit, using the MSI installer from python.org.

To reproduce, download virtualenv and extract the C:\Work\Scratch\virtualenv-pfm\virtualenv_support\pip-1.5.2-py2.py3-none-any.whl file. Set PYTHONPATH to the full path of that wheel.

python -c "import pip" should work without error, but I see

PS 20:44 C:\Work\Scratch\virtualenv-pfm
>$env:PYTHONPATH="C:\Work\Scratch\virtualenv-pfm\virtualenv_support\pip-1.5.2-py2.py3-none-any.whl"
PS 20:49 C:\Work\Scratch\virtualenv-pfm
>C:\Apps\Python33\python.exe -c "import pip"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ImportError: No module named 'pip'

For comparison, the 32-bit version works perfectly:

PS 20:44 C:\Work\Scratch\virtualenv-pfm
>$env:PYTHONPATH="C:\Work\Scratch\virtualenv-pfm\virtualenv_support\pip-1.5.2-py2.py3-none-any.whl"
PS 20:49 C:\Work\Scratch\virtualenv-pfm
>C:\Apps\Python33\python.exe -c "import pip"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ImportError: No module named 'pip'
History
Date User Action Args
2014-02-13 20:50:36paul.mooresetrecipients: + paul.moore, georg.brandl
2014-02-13 20:50:36paul.mooresetmessageid: <1392324636.47.0.967775665476.issue20621@psf.upfronthosting.co.za>
2014-02-13 20:50:36paul.moorelinkissue20621 messages
2014-02-13 20:50:35paul.moorecreate