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

Groups > comp.lang.python > #71808 > unrolled thread

Putting Py 3.4.1 to work.

Back to article view | Back to comp.lang.python

Contents

  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

#71808 — Putting Py 3.4.1 to work.

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']
>>> ---
sys.path.append(r'C:\Python34\Lib\site-packages\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', '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'
>>> ---
sys.version
'3.4.1 (v3.4.1:c0e311e010fc, May 18 2014, 10:38:22) [MSC v.1600 32 bit (Intel)]'
>>> ---

jmf

[toc] | [next] | [standalone]

#71816

In <d195c26b-62f9-4240-8f3e-c579a288961d@googlegroups.com> wxjmfauth@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?

-- 
John Gordon         Imagine what it must be like for a real medical doctor to
gordon@panix.com    watch 'House', or a real serial killer to watch 'Dexter'.

[toc] | [prev] | [next] | [standalone]

#71818

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

[toc] | [prev] | [next] | [standalone]

#71821

Le 20/05/2014 19:38, Ian Kelly a écrit :
> On Tue, May 20, 2014 at 11:14 AM, John Gordon <gordon@panix.com> wrote:
>> In <d195c26b-62f9-4240-8f3e-c579a288961d@googlegroups.com> wxjmfauth@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.
What about:

from pyside import QtCore, QtGui

?

-- 
Vincent V.V.
Oqapy <https://launchpad.net/oqapy> . Qarte 
<https://launchpad.net/qarte> . PaQager <https://launchpad.net/paqager>

[toc] | [prev] | [next] | [standalone]

#71822

On Wed, May 21, 2014 at 4:02 AM, Vincent Vande Vyvre
<vincent.vandevyvre@swing.be> wrote:
> from pyside import QtCore, QtGui

Is it pyside or PySide? There seems to be some inconsistency here.

ChrisA

[toc] | [prev] | [next] | [standalone]

#71823

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

[toc] | [prev] | [next] | [standalone]

#71826

Le 20/05/2014 20:12, Chris Angelico a écrit :
> On Wed, May 21, 2014 at 4:02 AM, Vincent Vande Vyvre
> <vincent.vandevyvre@swing.be> wrote:
>> from pyside import QtCore, QtGui
> Is it pyside or PySide? There seems to be some inconsistency here.
>
> ChrisA
Yes PySide, off course. Sorry.

-- 
Vincent V.V.
Oqapy <https://launchpad.net/oqapy> . Qarte 
<https://launchpad.net/qarte> . PaQager <https://launchpad.net/paqager>

[toc] | [prev] | [next] | [standalone]

#71827

-----

Complete (re)Fresh install Stop Python34, PySide ok Stop
cx_freeze 4.3.3 for py34 seems to suffer, again, from the same
desease as with cx_freeze 4.3.2, Py 3.4.0 leading to a Py crash
Stop Python, PySide, cx_freeze, Windows issue? No idea Stop
Have some idea about the guilty msi installer Stop.

jmf

[toc] | [prev] | [next] | [standalone]

#71829

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.
>
> 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.

-- 
Zach

[toc] | [prev] | [next] | [standalone]

#71831

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

[toc] | [prev] | [next] | [standalone]

#71838

Le mercredi 21 mai 2014 00:19:37 UTC+2, Terry Reedy a écrit :
> 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.
> 
> >>
> 
> 
> > 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.
> 
> 

Sorry, *I* did not install, the *msi* installer
did it. I had a complete mismatch, python*.exe, in DLLs
and py*.exe in c:\python34 !

Usualy, I removed then I reinstall, I did no do it
this time.

I'm very aware about all this stuff, all my apps
are running on any wins from an usb strick, including
my interactive interpreters.

I have however some more serious concerns about
cx_freeze, will spend some time soon.

FYI:
On win7, "Program Files" does no more exist. The name
is a "fake" "Programs" (without any space (finally))
which carries the name of the "linguistic" win version,
in my case c:\Programmes (French).

jmf

[toc] | [prev] | [next] | [standalone]

#71841

I really expected I worked to quickly and I did a mistake
in freezing applications. But, no. cx_freeze just re-became
problematic, __file__, bootstap, importlib and so on.

My take on the subject.
Since the introduction of this uncecessary __pycache__ mess,
I'm experimenting a lot of problems (I'm not alone).
It was too simple, logical, let's make complicate. Pure Python
development style.

jmf

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web