[Pythonmac-SIG] py2app with wxpython

[Brendan Simon (eTRIX)]

On 23/02/2011 1:18 AM, Ronald Oussoren wrote:
>
> On 22 Feb, 2011, at 12:03, Brendan Simon (eTRIX) wrote:
>
>> On 22/02/11 8:57 PM, Ronald Oussoren wrote:
>>> On 21 Feb, 2011, at 12:33, Brendan Simon (eTRIX) wrote:
>>>
>>>> On 21/02/11 10:00 PM, pythonmac-sig-request at python.org wrote:
>>>>> Subject:
>>>>> Re: [Pythonmac-SIG] py2app with wxpython
>>>>> From:
>>>>> Ned Deily <nad at acm.org>
>>>>> Date:
>>>>> Sun, 20 Feb 2011 15:46:05 -0800
>>>>>
>>>>> To:
>>>>> pythonmac-sig at python.org
>>>>>
>>>>>
>>>>> In article<4D61918E.1010308 at etrix.com.au>,
>>>>>   "Brendan Simon (eTRIX)"<brendan.simon at etrix.com.au>  wrote:
>>>>>> >  Do you need to specify 'pythonw' as the interpreter ??
>>>>>> >  It may depend on python version.  I found (on OS X) that Python 2.7
>>>>>> >  requires pythonw rather than python to run my wxPython apps.
>>>>> That sounds very suspicious.  On OS X installs, bin/python and
>>>>> bin/pythonw are supposed to be identical.
>>>> Indeed you are right.  The python and pythonw varieties are 
>>>> identical for Python 2.7 and my wxPython application works fine 
>>>> with either.
>>>>
>>>> I tried again with my Python 2.5.4 install and that does have the 
>>>> problem.
>>>
>>> Which python 2.5.4 is that (that is, how did you install it)? Are 
>>> you sure that 'python' and 'pythonw' refer to the same python 
>>> installation (what is sys.prefix for these two commands)?
>> I'm using standard python.org <http://python.org> builds.
>>
>>
>> brendan$ python
>> Python 2.5.4 (r254:67917, Dec 23 2008, 14:57:27)
>> [GCC 4.0.1 (Apple Computer, Inc. build 5363)] on darwin
>> Type "help", "copyright", "credits" or "license" for more information.
>> >>> import sys
>> >>> print sys.prefix
>> /Users/brendan/virtualenv/xxx-py25/bin/..
>>
>>
>> brendan$ pythonw
>> Python 2.5.4 (r254:67917, Dec 23 2008, 14:57:27)
>> [GCC 4.0.1 (Apple Computer, Inc. build 5363)] on darwin
>> Type "help", "copyright", "credits" or "license" for more information.
>> >>> import sys
>> >>> print sys.prefix
>> /Library/Frameworks/Python.framework/Versions/2.5
>>
>>
>> Hmmm, it might be something to do with my virtualenv setup (I've only 
>> just started using virtualenv).
>>
>> brendan$ ls -l ~/virtualenv/xxx-py25/bin/python*
>> -rwxrwxr-x  1 brendan  staff  30028 27 Jan 22:11 
>> /Users/brendan/virtualenv/xxx-py25/bin/python
>> lrwxr-xr-x  1 brendan  staff      6 27 Jan 22:11 
>> /Users/brendan/virtualenv/xxx-py25/bin/python2.5 -> python
>> lrwxr-xr-x  1 brendan  staff     61 27 Jan 22:20 
>> /Users/brendan/virtualenv/xxx-py25/bin/pythonw -> 
>> /Library/Frameworks/Python.framework/Versions/2.5/bin/pythonw
>
>
> AFAIK pythonw doesn't work in virtualenvs and within a virtualenv the 
> python command is the real embedded interpreter, not the pythonw 
> wrapper you get otherwise.
>
> This is something that needs to be fixed by someone. I'm more likely 
> to work on a simular tool that supports both 2.x and 3.x and doesn't 
> install crap I didn't ask for and isn't mentioned in the documentation.

I'm not clear which tool you are referring too.  I'm presuming 
virtualenv, right ??  or are you referring to the pythonw wrapper ??

Does virtualenv have some downsides that I'm not aware of ??
It seems like a great idea to be able to install separate modules into 
separate virtual environments so that each project can use different 
modules, or different versions of the same module, etc.

Cheers, Brendan.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pythonmac-sig/attachments/20110223/fa4a261a/attachment.html>