The PEP 370 (http://www.python.org/dev/peps/pep-0370) "per user site
packages directory" has several open questions:
* Are the directories for Windows, Mac and Unix fine?
* Mac: Should framework and non-framework builds of Python use
the same directories?
* The patch also adds a usecustomize hoo
On Thu, Jan 17, 2008 at 06:12:52AM +0900, Stephen J. Turnbull wrote:
-> Bill Janssen writes:
-> > > >> ~/Library/ is a Mac OS X thing.
-> > >
-> > > Bill> Sure, but it's clearly where this should be on an OS X
system, by
-> > > Bill> default.
->
-> > > [etc.]
->
-> > [tocatta
Bill Janssen writes:
> > >> ~/Library/ is a Mac OS X thing.
> >
> > Bill> Sure, but it's clearly where this should be on an OS X system, by
> > Bill> default.
> > [etc.]
> [tocatta and fugue ad lib]
Doesn't Apple publish standards for this? They do for everything
else, it se
I posted this on c.l.py but I didn't get a definite answer so I am
asking again here: is it documented anywhere that "from
.relative.module import *' is syntax error? Unless I missed it, PEP
328 doesn't mention anything about it. Also, while I understand the
general caveats and warnings against "im
> >> ~/Library/ is a Mac OS X thing.
>
> Bill> Sure, but it's clearly where this should be on an OS X system, by
> Bill> default.
>
> I think only for stuff that is a Mac-ish GUI app type of thing and/or that
> plays with Mac's distinct APIs (Carbon, Cocoa, whatever). Would you
> i
>> ~/Library/ is a Mac OS X thing.
Bill> Sure, but it's clearly where this should be on an OS X system, by
Bill> default.
I think only for stuff that is a Mac-ish GUI app type of thing and/or that
plays with Mac's distinct APIs (Carbon, Cocoa, whatever). Would you
install, for exa
