On 10/02/2005, at 1:04 PM, Bob Ippolito wrote:
You should never, ever, ever, ever, ever write inside of a bundle
anyway. You should make this runtime directory in /tmp,
/Library/Application Support/, etc.
Oh, OK :)
I readily admit that I was being slack (actually, mostly I'm in a
hurry) in usin
On 10/02/2005, at 12:38 PM, Bob Ippolito wrote:
I tried to reproduce this problem by dropping your Python dylib into
my framework, and it worked fine.. what version of Mac OS X are you
using and have you tried it a second time after killing build and
dist?
That was it - I needed to clean out
On 10/02/2005, at 10:35 AM, Bob Ippolito wrote:
The current svn trunk of py2app is probably suitable for this. It now:
- Strips by default. -S and --strip are still there for
compatibility, but they are a no-op (does anyone care if I remove this
compatibility?)
I get the following error durin
On 10/02/2005, at 10:35 AM, Bob Ippolito wrote:
- Adds a Python interpreter to the bundle to where sys.executable is
(only supported for framework builds right now)
Thanks Bob!
I'll have a play straight away :)
Richard
___
Pythonmac-SIG maillist -
On 04/02/2005, at 12:05 PM, Bob Ippolito wrote:
I'll see about adding an optional regular Python interpreter to the
bundle, but that probably won't happen for a few weeks.
No sweat - I've just introduced our target users to running Zope from
the command-line which will suffice for now :)
Ric
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 4 Feb 2005 01:34 am, Bob Ippolito wrote:
> No, py2app just doesn't give you a regular Python interpreter.. so,
> that's a problem I guess. I'm not sure what to suggest.
Yep, looks like it's the killer for the py2app'ed Zope.
I'm going to inv
On 03/02/2005, at 6:12 PM, Bob Ippolito wrote:
On Feb 2, 2005, at 19:08, Richard Jones wrote:
OK, starting at it again this morning, I've made some progress
getting things configured correctly to start up Zope.
I've hit another roadblock though -- Zope needs to fork/exec off new
pr
OK, starting at it again this morning, I've made some progress getting
things configured correctly to start up Zope.
I've hit another roadblock though -- Zope needs to fork/exec off new
processes. I can't actually find a Python interpreter in the app
generated by py2app, and I suspect one isn't
On 02/02/2005, at 8:04 PM, Bob Ippolito wrote:
On Feb 2, 2005, at 4:01 AM, Richard Jones wrote:
On 02/02/2005, at 7:45 PM, Bob Ippolito wrote:
Creating both a zip and a directory is perfectly normal and expected.
"fails to find some stuff" is probably unrelated.
More specifically,
On 02/02/2005, at 7:45 PM, Bob Ippolito wrote:
Creating both a zip and a directory is perfectly normal and expected.
"fails to find some stuff" is probably unrelated.
More specifically, the "smart" xml.sax.saxexts module fails to find any
parsers for parsing XML. I need to look more closely at wha
On 02/02/2005, at 3:10 PM, Richard Jones wrote:
My app is a simple GUI thing which controls Zope through the
zdaemon.zdctl module. It's attached. The Zope libs (and some
supporting libs) are installed in the app's Resources folder in a
"runtime" subdirectory (historical n
On 02/02/2005, at 4:24 PM, Bob Ippolito wrote:
If you zip -r9 that I bet its 10 times smaller, at least.
23MB :)
I could make that available if you're willing to look at it.
It could be some exception gone wrong, a bug in zope, a bug in PyObjC,
etc. At the absolute least, I need to see a gdb ba
On 02/02/2005, at 3:28 PM, Bob Ippolito wrote:
Could be a lot of things. I can't really start to guess unless I can
see it.
Unfortunately:
short:~/src/cg/Zope-OSX richard$ du -sk dist/
80560 dist/
:(
I've figured that it is Zope that's causing the problems. I guess
there's maybe just another m
On 02/02/2005, at 3:10 PM, Richard Jones wrote:
Fatal Python error: PyThreadState_Get: no current thread
Abort trap
Changing::
import objc
to::
import objc
objc.enableThreading()
didn't help.
Richard
___
Pythonmac-SIG mai
I've just switched from running py2app with -A to not using it. After
fleshing out the "includes" option so that my required modules were
included, I finallly got the app to start up. It promptly quits, with
the following message:
Fatal Python error: PyThreadState_Get: no current thread
Abort t
On 28/01/2005, at 3:42 PM, Bob Ippolito wrote:
On Jan 27, 2005, at 11:26 PM, Richard Jones wrote:
On 28/01/2005, at 2:45 PM, Bob Ippolito wrote:
On Jan 27, 2005, at 7:31 PM, Richard Jones wrote:
1. I can't find source for PyObjC (though I think it might come
with Python?)
Ever tried google?
On 28/01/2005, at 2:45 PM, Bob Ippolito wrote:
On Jan 27, 2005, at 7:31 PM, Richard Jones wrote:
1. I can't find source for PyObjC (though I think it might come with
Python?)
Ever tried google? Even clicking "I'm feeling lucky" will take you to
the right place.. which
On 28/01/2005, at 12:14 AM, Bob Ippolito wrote:
On Jan 26, 2005, at 23:49, Richard Jones wrote:
2. install the PyObjC stuff alongside a manually compiled Python?
That works fine.
Two hitches here:
1. I can't find source for PyObjC (though I think it might come with
Python?)
2. I can't
On 27/01/2005, at 5:50 PM, Pierre Thibault wrote:
I just made an install of Python 2.4 on my machine. The 'README' is
saying that the install is going to take place on /usr/bin but in
reality things were installed in /usr/local/bin'.
If you built it from scratch, it'll configure to go in /usr/loc
I'm starting on the path to PyObjC, and have made some progress. I'm
developing a very simple GUI control panel to allow starting, stopping
and status display of a Zope server running on the machine. I've hit a
nasty roadblock though - Zope (2.7.4) *requires* Python 2.3.3.
Unfortunately, becaus
20 matches
Mail list logo
