On 31 May, 2010, at 23:25, Johan Gyllenspetz wrote:
Hi,
What is the status on py2app - snow leopard - x86_64 and ports.
What ports?
Do I
really need to build all port packages with the flag +universal, it
seems like it seems the application when inspected returns.
file
On Tue, Jun 1, 2010 at 11:30 AM, Ronald Oussoren ronaldousso...@mac.com wrote:
On 31 May, 2010, at 23:25, Johan Gyllenspetz wrote:
Hi,
What is the status on py2app - snow leopard - x86_64 and ports.
What ports?
Sorry I ment macports.
Do I
really need to build all port packages with
On 1 Jun, 2010, at 11:36, Johan Gyllenspetz wrote:
On Tue, Jun 1, 2010 at 11:30 AM, Ronald Oussoren ronaldousso...@mac.com
wrote:
On 31 May, 2010, at 23:25, Johan Gyllenspetz wrote:
Hi,
What is the status on py2app - snow leopard - x86_64 and ports.
What ports?
Sorry I ment
On 1 Jun, 2010, at 12:35, Michiel de Hoon wrote:
I tried this again on Mac OS X 10.5 and found that the Python inside
Python.app works as a framework, but python and pythonw do not:
$
/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python
Python
I tried this again on Mac OS X 10.5 and found that the Python inside Python.app
works as a framework, but python and pythonw do not:
$
/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python
Python 2.7b2+ (trunk:81635, Jun 1 2010, 20:39:42)
[GCC 4.0.1
I've been trying to test a new app I'm working on and it appears that my
sys.path has been corrupted somehow, because Python doesn't see things
in my site-packages directory.
My $PATH is correctly set up:
which python
/Library/Frameworks/Python64.framework/Versions/Current/bin/python
On 6/1/10 11:06 AM, Kevin Walzer wrote:
Does anyone have any idea what might cause my framework build of Python
to see sys.path only in the build directory of one of my apps? I don't
typically jigger my Python settings with .pth files so I have no idea
what to look for.
I solved the problem
On 1 Jun, 2010, at 13:25, Ronald Oussoren wrote:
On 1 Jun, 2010, at 12:35, Michiel de Hoon wrote:
I tried this again on Mac OS X 10.5 and found that the Python inside
Python.app works as a framework, but python and pythonw do not:
$
