[Pythonmac-SIG] New Page, first proposal
Ronald Oussoren
ronaldoussoren at mac.com
Sat Feb 11 22:14:53 CET 2006
On 10-feb-2006, at 21:37, Christopher Barker wrote:
> Bob Ippolito wrote:
>>> Let's have py2app be a standard part of the 2.4 package. It'd be
>>> great
>>> if the standard upgrade package had and did everything you need
>>> to get
>>> started. I suggest easy-install as well.
>>
>> I'd prefer to wait on that until it's more mature.
>
> Why? it's what we use now, and it's the best there is. Anyone
> wanting to
> create stand-alones is going to need it. There's always room for it to
> be upgraded in the future.
I guess that depends on what the Python 2.4 package is. I'd like to keep
it as close as possible to python.org source distribution.
>
>> Shipping setuptools isn't a bad idea, but it's a one-liner to
>> install
> it..
>
> Yes, but it then puts the scripts in the weird bin directory buried in
> the Framework, and one extra step is one extra step too many.
That is not an issue if the installer for Python places that weird
bin directory
on the PATH.
>
>> The extension thing we can hack around by installing two copies of
>> the
>> Makefile and having distutils pick a PPC-only Makefile if it
>> detects 10.3.
>
> OK. as long as that hack is built in to the installer, that's great.
It should be build into distutils, not the installer, but otherwise I
agree.
>
>> Since we're going to manipulating the PATH with the installer, should
>> we still bother with the symlinks in /usr/local/bin? We definitely
>> want the Framework's bin dir on the PATH because that's where scripts
>> will be installed to... so the /usr/local/bin links seem a bit
>> redundant. If we do this, then the Python installation process is
>> completely self-contained except for the Applications dir.
>
> hmmm. In general, I'm not thrilled with every app creating it's own
> addition to the PATH, it reminds me of DOS pain. I really like that in
> *nix, there are only a few, standard, places for executables. Given
> that, another option is to Create a ~/.pydistutils.cfg file with:
If we'd do that we'd have to create a distutils.cfg somewhere in
the python library (e.g. the system-wide version of .pydistuls.cfg).
As I've mentioned before I prefer having every app in it's own
directory,
that makes it a lot easier to muck about with multiple versions of
python.
BTW. In most modern unices 3th-party apps are supposed to install in
their
own directory in /opt ;-)
Ronald
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2157 bytes
Desc: not available
Url : http://mail.python.org/pipermail/pythonmac-sig/attachments/20060211/2936b282/attachment.bin
More information about the Pythonmac-SIG
mailing list