On 20/05/2014 18:38, Ian Kelly wrote:
On Tue, May 20, 2014 at 11:14 AM, John Gordon <gor...@panix.com> wrote:
In <d195c26b-62f9-4240-8f3e-c579a2889...@googlegroups.com> wxjmfa...@gmail.com
writes:
sys.path
['D:\\jm\\jmpy\\smid\\smid50beta1', 'C:\\Windows\\system32\\python34.zip',
'C:\\Python34\\DLLs\\DLLs', 'C:\\Python34\\DLLs\\lib', 'C:\\Python34\\DLLs',
'C:\\Python34\\DLLs\\lib\\site-packages',
'C:\\Python34\\Lib\\site-packages\\PySide']
---
import PySide
Traceback (most recent call last):
File "<smid last command>", line 1, in <module>
ImportError: No module named 'PySide'
Is there a file named __init__.py in the PySide directory?
Did 'import PySide' used to work on Python 3.4.0?
Or maybe some .pth file got clobbered.
I always reinstall packages after upgrading Python on Windows. I
don't know whether the scenario of reinstalling Python on top of an
existing site-packages directory is supposed to work or not.
I've never bothered to reinstall packages after upgrading Python on
Windows and I've never had a problem. I can't see how Python can do
anything with site-packages as it knows nothing about it, other than
that it exists, so it strikes me that it has to work, or am I missing
something?
--
My fellow Pythonistas, ask not what our language can do for you, ask
what you can do for our language.
Mark Lawrence
---
This email is free from viruses and malware because avast! Antivirus protection
is active.
http://www.avast.com
--
https://mail.python.org/mailman/listinfo/python-list
