Hi,
One for Bob really, but I'm trying to figure out how to build a
non-standalone app using py2app. This was easy (albeit clumsy) with
bundlebuilder - just set both 'standalone' and 'semi-standalone'
options to False. I see a 'semi-standalone' option in py2app, but
that still includes a big wa
On Dec 16, 2004, at 2:14 PM, has wrote:
Bob wrote:
[py2app] still does the dependency scan for third party python code
and dependent libraries/frameworks. If you want to depend on third
party stuff in site-packages, too bad, you'll have to exclude them
all individually and use --site-packages.
Bob wrote:
[py2app] still does the dependency scan for third party python
code and dependent libraries/frameworks. If you want to depend on
third party stuff in site-packages, too bad, you'll have to
exclude them all individually and use --site-packages.
Why?
Because I don't care about your use
On Dec 16, 2004, at 2:35 PM, Chris Barker wrote:
Bob Ippolito wrote:
The way to tell it to include nothing is to build an alias bundle
(-A), which is for development only and doesn't create something
suitable for redistribution.
Can you tell us more about what an Alias bundle is? Is like the old
On Dec 16, 2004, at 2:40 PM, has wrote:
Bob wrote:
[py2app] still does the dependency scan for third party python code
and dependent libraries/frameworks. If you want to depend on third
party stuff in site-packages, too bad, you'll have to exclude them
all individually and use --site-packages.
On Dec 16, 2004, at 3:07 PM, Chris Barker wrote:
Bob Ippolito wrote:
Rare enough that I can't justify writing the code and adding yet
another option.
That, of course, is your judgment. However, I'm not sure it's a rare
as you think. I, for one, want to be able to distribute apps to folks
whose e
Bob Ippolito wrote:
Rare enough that I can't justify writing the code and adding yet another
option.
That, of course, is your judgment. However, I'm not sure it's a rare as
you think. I, for one, want to be able to distribute apps to folks whose
environment I have control over, so I know that th
Bob wrote:
Because I don't care about your use case. It's rare and is very
often not what people want.
How rare?
Rare enough that I can't justify writing the code and adding yet
another option.
If you don't need a redistributable application, then use an alias
bundle. If you want a redistrib
Bob wrote:
Adding this option causes more problems than it solves.
Such as?
Feel free to do it yourself, either by subclassing py2app (then
using the cmdclass argument to setup(...)), or by writing a patch
against py2app that makes this option available.
Aye well, I'm not really up to digesting
On Dec 16, 2004, at 11:47 AM, has wrote:
One for Bob really, but I'm trying to figure out how to build a
non-standalone app using py2app. This was easy (albeit clumsy) with
bundlebuilder - just set both 'standalone' and 'semi-standalone'
options to False. I see a 'semi-standalone' option in py2a
Bob wrote:
[py2app] still does the dependency scan for third party python code
and dependent libraries/frameworks. If you want to depend on third
party stuff in site-packages, too bad, you'll have to exclude them
all individually and use --site-packages.
Why?
has
--
http://freespace.virgin.net/
Bob Ippolito wrote:
The way to tell it to include nothing is to build an alias bundle (-A),
which is for development only and doesn't create something suitable for
redistribution.
Can you tell us more about what an Alias bundle is? Is like the old
MacPython applet?
What I would like is a bundl
On Dec 16, 2004, at 6:00 PM, has wrote:
Bob wrote:
Because I don't care about your use case. It's rare and is very
often not what people want.
How rare?
Rare enough that I can't justify writing the code and adding yet
another option.
If you don't need a redistributable application, then use an
13 matches
Mail list logo
