13 messages in org.python.pythonmac-sig[Pythonmac-SIG] .pydistutils.cfg (was...
FromSent OnAttachments
Mike HansenJan 4, 2005 3:40 am 
Robert KernJan 4, 2005 4:25 am 
Bob IppolitoJan 4, 2005 5:13 am 
Robert KernJan 4, 2005 5:57 am 
Bob IppolitoJan 4, 2005 6:03 am 
Robert KernJan 4, 2005 7:11 am 
Jack JansenJan 4, 2005 2:09 pm 
Bob IppolitoJan 4, 2005 2:42 pm 
Bob IppolitoJan 4, 2005 2:50 pm 
Ronald OussorenJan 4, 2005 3:18 pm 
Jack JansenJan 4, 2005 10:17 pm 
Bob IppolitoJan 4, 2005 10:30 pm 
Mike HansenJan 5, 2005 2:56 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[Pythonmac-SIG] .pydistutils.cfg (was: pychecker)Actions...
From:Jack Jansen (Jack@cwi.nl)
Date:Jan 4, 2005 10:17:00 pm
List:org.python.pythonmac-sig

On 4-jan-05, at 14:42, Bob Ippolito wrote:

On Jan 4, 2005, at 8:09 AM, Jack Jansen wrote:

I'd never even heard of .pydistutils.cfg. I've added a note to the FAQ pointing to it.

It has some more features in Python 2.4, you can use it to add new build command packages to distutils out-of-tree (like py2app, bdist_mpkg, etc.). Of course, very few distutils extensions are implemented in away that is compatible with this new feature, but it's there and I'll probably end up making py2app and bdist_mpkg compatible.

Interesting... Although: you only need py2app and bdist_mpkg on the supplier-side (right?), so it doesn't really buy us all that much except a bit of convenience.

Then I looked at the distutils code, and noticed that there's also an optional distutils.cfg inside the package. So that made me wonder: we could install a symlink in /System/yaddayaddayadda/lib/python2.3/distutils/distutils.cfg that points to, say, /Library/Python/2.3/distutils.cfg, and put an (admin-editable) file there that directs scripts tot the right place system wide (/usr/local/bin by default, probably).

+1 on the idea +1 for /usr/local/bin as the "right place"

Not so sure about install-data pointing to /usr/local/share (earlier on in the thread), because some packages might try and locate their data files using means other than distutils (sys.prefix relative).

Yeah, I was wondering about that one too. I'll leave it out, if the end user wants it s/he can edit the file.

Another thing that would be nice is to have some admin-writable place to put header files (in addition to Python's own headers) too. But that would require a patch to distutils and might need to happen in the 2.5 tree.