Re: py2app -A and virtual environments

> On 28 Sep 2018, at 13:08, Ronald Oussoren <[email protected]> wrote:
> 
> 
> 
>> On 28 Sep 2018, at 10:34, Just van Rossum <[email protected]> wrote:
>> 
>> Following up to this: it seems line 1832 in py2app/build_app.py isn’t correct anymore, with Python 3 venv behavior:
>> 
>>       if os.path.exists(os.path.join(sys.prefix, ".Python")):
>> 
>> Not sure how to fix it. If I force this code path to be taken, I get an AttributeError on sys.real_prefix, so I guess a bit more needs to be done.
> 
> The line of code is for virtualenv support. I’ll have to check the code to see what’s needed to support venv here as well.

Yes, it’s checking to see whether we’re running from a venv, but it’s not triggering as it should, I think. Somehow this “.Python” path doesn’t exist in my case, even though I am running from a venv.

Just


> 
> Ronald
> 
>> 
>> Just
>> 
>>> On 27 Sep 2018, at 16:05, Just van Rossum <[email protected]> wrote:
>>> 
>>> Hi all,
>>> 
>>> py2app seems to do the right thing from an activated virtual env when building a full app. However, for speedy development I use the py2app -A option a lot, and when running such an alias bundle it appears to use the global Python install instead of the virtual env. Is there a way around that?
>>> 
>>> Just
>>> 
>> 
> 

_______________________________________________
Pythonmac-SIG maillist  -  [email protected]
https://mail.python.org/mailman/listinfo/pythonmac-sig
unsubscribe: https://mail.python.org/mailman/options/Pythonmac-SIG