Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #71831

Re: Putting Py 3.4.1 to work.

Show all headers | View raw

On 5/20/2014 4:55 PM, Zachary Ware wrote:
> On Tue, May 20, 2014 at 9:31 AM,  <wxjmfauth@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.

I installed 3.4.1 on top of 3.4.0, Win 7, both 64-bit versions.

 >> contained eg. PySide in ...\site-packages.

The installer is careful to only overwrite or delete files it installed. 
The only problem one will have is if you modify a file Python installed 
or add a new file where Python subsequently adds one (but that is 
unlikely in bug-fix releases anyway).

>> 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']

 >>> sys.path
['', 'C:\\Programs\\Python34\\Lib\\idlelib', 
'C:\\Windows\\system32\\python34.zip', 'C:\\Programs\\Python34\\DLLs', 
'C:\\Programs\\Python34\\lib', 'C:\\Programs\\Python34', 
'C:\\Users\\Terry\\AppData\\Roaming\\Python\\Python34\\site-packages', 
'C:\\Programs\\Python34\\lib\\site-packages', 'F:\\Python'

Delete \Programs to match what you should have.

> This looks like something went weird in your installation, like you
> installed to 'C:\Python34\DLLs' instead of 'C:\Python34'.

I suspect you nailed it.

>  What path does sys.executable give?

 >>> sys.executable
'C:\\Programs\\Python34\\pythonw.exe' (from Idle)

 > The usual location for site-packages is
> C:\Python34\Lib\site-packages, which is not listed.

whereas the new 'C:\\Programs\\Python34\\lib\\site-packages' will be empty.

-- 
Terry Jan Reedy

Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Putting Py 3.4.1 to work. wxjmfauth@gmail.com - 2014-05-20 07:31 -0700
  Re: Putting Py 3.4.1 to work. John Gordon <gordon@panix.com> - 2014-05-20 17:14 +0000
    Re: Putting Py 3.4.1 to work. Ian Kelly <ian.g.kelly@gmail.com> - 2014-05-20 11:38 -0600
    Re: Putting Py 3.4.1 to work. Vincent Vande Vyvre <vincent.vandevyvre@swing.be> - 2014-05-20 20:02 +0200
    Re: Putting Py 3.4.1 to work. Chris Angelico <rosuav@gmail.com> - 2014-05-21 04:12 +1000
    Re: Putting Py 3.4.1 to work. Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-05-20 19:13 +0100
    Re: Putting Py 3.4.1 to work. Vincent Vande Vyvre <vincent.vandevyvre@swing.be> - 2014-05-20 21:11 +0200
      Re: Putting Py 3.4.1 to work. wxjmfauth@gmail.com - 2014-05-20 12:26 -0700
  Re: Putting Py 3.4.1 to work. Zachary Ware <zachary.ware+pylist@gmail.com> - 2014-05-20 15:55 -0500
  Re: Putting Py 3.4.1 to work. Terry Reedy <tjreedy@udel.edu> - 2014-05-20 18:19 -0400
    Re: Putting Py 3.4.1 to work. wxjmfauth@gmail.com - 2014-05-20 22:52 -0700
      Re: Putting Py 3.4.1 to work. wxjmfauth@gmail.com - 2014-05-20 23:36 -0700

csiph-web