On Tue, May 20, 2014 at 9:31 AM,  <wxjmfa...@gmail.com> wrote:
> Experimented users have certainly noticed a lot of
> things have changed.
> Short. I installed Py3.4.1, it overwrites c:\Python34 which
> contained eg. PySide in ...\site-packages.
> So far, so good. I can launch Python, IDLE and my interactive
> interpreter I wrote with tkinter via a cmd in dos, .bat, ...
> Now the questions. It seems all packages in \site-packages
> are no more recognized.
> What am I doing wrong? Why is "site-packages" no more
> recognized, "forcing" sys.path does not seem to help.
> From my interactive interpreter:
>>>> ---
> import PySide
> Traceback (most recent call last):
>   File "<smid last command>", line 1, in <module>
> ImportError: No module named 'PySide'
>>>> ---
> 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']

This looks like something went weird in your installation, like you
installed to 'C:\Python34\DLLs' instead of 'C:\Python34'.  What path
does sys.executable give?  The usual location for site-packages is
C:\Python34\Lib\site-packages, which is not listed.


Reply via email to