On Tue, Mar 11, 2008 at 08:43:06AM +0100, Matthias Klose wrote:
Currently Debian's python has /usr/local/lib/python2.x/site-packages
in sys.path allowing for installation of local modules. Barry did
point out that this conflicts with a python installation, where
/usr/local is the default
Barry Warsaw wrote:
This is Debian policy (which is fine), but I don't think all distros
agree. I'm not a distro guy though. :) Mattias, didn't the Fedora guys
say they were going to try to create a mailing list for discussing these
kinds of cross-distro issues?
There's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 11, 2008, at 6:36 PM, Floris Bruynooghe wrote:
On Tue, Mar 11, 2008 at 09:45:21AM -0400, Barry Warsaw wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 11, 2008, at 3:43 AM, Matthias Klose wrote:
Currently Debian's python has
Barry Warsaw [EMAIL PROTECTED] writes:
On Mar 11, 2008, at 6:36 PM, Floris Bruynooghe wrote:
The sysadmin should never install things into /usr/ directly,
/usr/local/ is their playground.
This is Debian policy (which is fine), but I don't think all distros
agree.
Those distros that
Barry Warsaw wrote:
It also makes Debian the odd man out. Instructions we publish for
every other *nix have to have a caveat or FAQ for Debian's (and
derivatives) difference. These can go unnoticed until things break,
and then we can get difficult to debug problem reports. An
experienced
Matthias Klose wrote:
Currently Debian's python has /usr/local/lib/python2.x/site-packages
in sys.path allowing for installation of local modules. Barry did
point out that this conflicts with a python installation, where
/usr/local is the default prefix, and the system python gets modules
from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 11, 2008, at 3:58 AM, Wichert Akkerman wrote:
- add another path (e.g. /usr/local/python/lib2.x/site-packages),
and remove the /usr/local/lib/python2.x/site-packages path after
the next release. Does provide an upgrade path, but doesn't
On Tue, Mar 11, 2008 at 08:43:06AM +0100, Matthias Klose wrote:
Currently Debian's python has /usr/local/lib/python2.x/site-packages
in sys.path allowing for installation of local modules. Barry did
point out that this conflicts with a python installation, where
/usr/local is the default
[Matthias Klose, 2008-03-11]
- add another path (e.g. /usr/local/python/lib2.x/site-packages),
and remove the /usr/local/lib/python2.x/site-packages path after
the next release. Does provide an upgrade path, but doesn't solve
the probem immediately.
I would choose this option or
On Tue, Mar 11, 2008 at 06:58:56PM +0100, Piotr Ożarowski wrote:
I would choose this option or even remove /usr/local/* from sys.path
completely. If one wants to play with unsupported Python modules or
Eggs, he should sys.path.append(his_path) by hand, IMHO.
I would not consider installing
Matthias Klose wrote:
- add an env var to not include /usr/local/lib/python2.x/site-packages
when the env var is set. Keeps standard behaviour without
modifications and allows people to remove it from sys.path. But
requires the user to know about that option.
I would much prefer
[Sebastian Rittau, 2008-03-11]
On Tue, Mar 11, 2008 at 06:58:56PM +0100, Piotr Ożarowski wrote:
I would choose this option or even remove /usr/local/* from sys.path
completely. If one wants to play with unsupported Python modules or
Eggs, he should sys.path.append(his_path) by hand, IMHO.
On Tue, Mar 11, 2008 at 09:45:21AM -0400, Barry Warsaw wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 11, 2008, at 3:43 AM, Matthias Klose wrote:
Currently Debian's python has /usr/local/lib/python2.x/site-packages
in sys.path allowing for installation of local modules. Barry
13 matches
Mail list logo
