On Sun, Jan 20, 2008 at 07:34:02PM +0100, Jan Claeys wrote:
> Op zondag 20-01-2008 om 20:46 uur [tijdzone +0300], schreef Oleg
> Broytmann:
> > On Sun, Jan 20, 2008 at 06:46:31PM +0100, Jan Claeys wrote:
> > > Op woensdag 16-01-2008 om 02:33 uur [tijdzone +0100], schreef Christian
> > > Heimes:
>
Op zondag 20-01-2008 om 20:46 uur [tijdzone +0300], schreef Oleg
Broytmann:
> On Sun, Jan 20, 2008 at 06:46:31PM +0100, Jan Claeys wrote:
> > Op woensdag 16-01-2008 om 02:33 uur [tijdzone +0100], schreef Christian
> > Heimes:
> > > ~/Library/ is a Mac OS X thing. I haven't seen it on other Unix sy
On Sun, Jan 20, 2008 at 06:46:31PM +0100, Jan Claeys wrote:
> Op woensdag 16-01-2008 om 02:33 uur [tijdzone +0100], schreef Christian
> Heimes:
> > Bill Janssen wrote:
> > > Good point, but I prefer ~/Library/Python to either of these.
> >
> > ~/Library/ is a Mac OS X thing. I haven't seen it on
Op woensdag 16-01-2008 om 02:33 uur [tijdzone +0100], schreef Christian
Heimes:
> Bill Janssen wrote:
> > Good point, but I prefer ~/Library/Python to either of these.
>
> ~/Library/ is a Mac OS X thing. I haven't seen it on other Unix systems.
There is (at least) one linux distro using it, but
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
> >> ~/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
Bill Janssen wrote:
> Sure, but it's clearly where this should be on an OS X system, by
> default. And I'm sure there's a different "best place" on Windows
> (for instance, all of our accounts are network roaming accounts, and
> you don't want to put anything in ~). And there are probably various
> Bill Janssen wrote:
> > Good point, but I prefer ~/Library/Python to either of these.
>
> ~/Library/ is a Mac OS X thing. I haven't seen it on other Unix systems.
> I *could* add yet another environment variable PYTHONUSERHOME to set the
> base path but I prefer not.
>
> Christian
Sure, but it
Bill Janssen wrote:
> Good point, but I prefer ~/Library/Python to either of these.
~/Library/ is a Mac OS X thing. I haven't seen it on other Unix systems.
I *could* add yet another environment variable PYTHONUSERHOME to set the
base path but I prefer not.
Christian
_
Oleg Broytmann writes:
> On Wed, Jan 16, 2008 at 06:31:42AM +0900, Stephen J. Turnbull wrote:
> > I think both for UI reasons (given above) and for API reasons (given
> > by others) there should be a separate ~/SOMETHING/{bin,etc,lib,share}
> > hierarchy for user-specific packaged contents. I like
Oleg>Why not use GNU stow?
Thanks for the reference. I'd never heard of it before. I suspect our IT
folks may not have as well.
Skip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscr
Oleg Broytmann writes:
> On Wed, Jan 16, 2008 at 06:31:42AM +0900, Stephen J. Turnbull wrote:
> > I think both for UI reasons (given above) and for API reasons (given
> > by others) there should be a separate ~/SOMETHING/{bin,etc,lib,share}
> > hierarchy for user-specific packaged contents. I
On Wed, Jan 16, 2008 at 06:31:42AM +0900, Stephen J. Turnbull wrote:
> I think both for UI reasons (given above) and for API reasons (given
> by others) there should be a separate ~/SOMETHING/{bin,etc,lib,share}
> hierarchy for user-specific packaged contents. I like ~/.local a
> little better tha
Oleg Broytmann writes:
>~/.python
To me, this strongly suggests user configuration files, not a place
where an app can store user-specific packages.
True, there are apps that store their stuff in such places, like most
GNOME apps. But they have no user-servicable parts (including config
fi
On Tue, Jan 15, 2008 at 02:34:02PM -0600, [EMAIL PROTECTED] wrote:
> Oleg>~/.python
> Oleg>~/.python/bin
> Oleg>~/.python/lib
> Oleg>~/.python/lib/python2.5
>
> The drawback of this approach is that it implies that Perl, Tcl, IPython,
> etc. belong in their own .wha
Oleg>~/.python
Oleg>~/.python/bin
Oleg>~/.python/lib
Oleg>~/.python/lib/python2.5
The drawback of this approach is that it implies that Perl, Tcl, IPython,
etc. belong in their own .whatever directory. The IT folks here at work do
things that way (though not in ho
Daniel> I use ~/local, with a layout analogous to /usr, ...
Ditto. Makes things nice and clear. I install stuff without becoming root
or polluting central directories.
Daniel> To those folks who favor creating ~/bin, ~/lib, ~/share, ad
Daniel> nauseum, I point out that non-hidden,
On Tue, Jan 15, 2008 at 12:11:37PM -0800, Daniel Arbuckle wrote:
> I use ~/local, with a layout analogous to /usr, all the time. It's not
> a standard, but in my experience it is by far the best solution to
> installing things in the home directory. It doesn't matter much
> whether you call it loca
On Tue, 15 Jan 2008 06:57:02 -0500, Kevin Jacobs wrote:
> On Jan 15, 2008 6:24 AM, Oleg Broytmann <[EMAIL PROTECTED]> wrote:
>
> > On Mon, Jan 14, 2008 at 11:41:47PM +, Jon Ribbens wrote:
> > > It makes sense, but personally I have never heard before of ~/.local.
> > > Whereas ~/bin is somethin
21 matches
Mail list logo
