Putting Py 3.4.1 to work.

[Ian Kelly]

On Tue, May 20, 2014 at 11:14 AM, John Gordon <gordon at panix.com> wrote:
> In <d195c26b-62f9-4240-8f3e-c579a288961d at googlegroups.com> wxjmfauth at 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.