Re: [Pythonmac-SIG] avoiding system's "easy-install.pth" with custom distribution

2013-09-13 Thread Nat Echols
On Tue, Sep 10, 2013 at 11:16 PM, Ned Deily wrote: > The behavior is the result of a feature added in 2.7 for Issue4865 which > appends the site-packages directory for the Apple-supplied system Python > to sys.path of a Python framework build. With hindsight, I don't think > this was a good idea

[Pythonmac-SIG] avoiding system's "easy-install.pth" with custom distribution

2013-09-10 Thread Nat Echols
I'm distributing a large cross-platform Python-based application, for which we bundle Python 2.7 and a number of dependencies (wxPython, matplotlib, etc.). We've tried to make it as self-contained as possible, to prevent either a) polluting the user's environment and potentially breaking other pro

Re: [Pythonmac-SIG] py2app failure with framework build of 2.7

2013-04-05 Thread Nat Echols
On Thu, Apr 4, 2013 at 11:28 PM, Ronald Oussoren wrote: > Packagemaker should't be problem here, although the build procedure might > be problematic: IIRC the app bundle contains symlinks where the target > is an absolute path, and therefore you need to create the app from > sources that are alrea

Re: [Pythonmac-SIG] py2app failure with framework build of 2.7

2013-04-04 Thread Nat Echols
On Thu, Apr 4, 2013 at 5:46 AM, Ronald Oussoren wrote: >> Replying to my own post: after sending this, I read the section in the >> documentation about "alias mode". This seems to work fine, and >> produces an app that is 50KB instead of nearly 9MB. Since I'm running >> this script as part of a

Re: [Pythonmac-SIG] py2app failure with framework build of 2.7

2013-04-03 Thread Nat Echols
the path to the interpreter and all modules is frozen by the time I need to make my app, it would seem that alias mode should work fine for actually *deploying* my software. Is there any drawback to doing this? thanks, Nat On Wed, Apr 3, 2013 at 3:45 PM, Nat Echols wrote: > I'm trying to

[Pythonmac-SIG] py2app failure with framework build of 2.7

2013-04-03 Thread Nat Echols
I'm trying to make a simple iconified Python launcher for a shell script, and something I'm doing isn't working, despite having used py2app successfully before. The target Python program ("my_program_wrapper.py") consists of this: import os import sys os.environ["PYTHONPATH"] = "" os.spawnv(os.P_

Re: [Pythonmac-SIG] broken symlinks when building framework

2013-02-15 Thread Nat Echols
On Fri, Feb 15, 2013 at 1:11 PM, Ned Deily wrote: > Framework builds can be confusing. Without seeing exactly what > "configure" options and "make" commands you are using, I can only > speculate. But, normally, the versioned symlinks in the framework bin > directory for things like 2to3-2 are cr

Re: [Pythonmac-SIG] Is this a reasonable way to do multiprocessing?

2011-04-19 Thread Nat Echols
On Tue, Apr 19, 2011 at 10:11 AM, Lou Pecora wrote: > But as many of you probably know that raises a pickle error. I did a > little > research and don't fully understand, but I thought of a way around this > that is > pedestrian, but it works on my toy example. I just make (deep) copies of my >

Re: [Pythonmac-SIG] py2app improperly using system framework

2011-04-06 Thread Nat Echols
On Wed, Apr 6, 2011 at 1:26 PM, Ronald Oussoren wrote: > Could you try the latest release on PyPI? This is just to check if that > version also has the problem you describe, which I haven't seen before even > though I have a number of versions installed on my machine. > Actually, I finally fixed

[Pythonmac-SIG] py2app improperly using system framework

2011-04-05 Thread Nat Echols
I'm using py2app from the latest SVN, along with an installation of Python 2.7 in a non-standard location. I don't get any error messages during running either py2applet or 'setup.py py2app', but at some point during app building, it starts copying over parts of the system's Python (2.6!) installa