-----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 solve the probem immediately.That just means you will break people's python at a later point again. That certainly can not be the right thing to do.
Depends on how you look at it I guess. I see it as eventually fixing everyone's Python ;).
Iff we really must come up with a way to make it a bit easier for people to install their own python version make it a system-wide switch in /etc/default/python2.x and keep the default behaviour as it is now so you will not break existing installations.
I'm not sure what the "it" is you want to make a system-wide switch. Would that be which Python to use, or whether to add the sys.path hack?
I don't know who's going to be at Pycon later this week, but if enough distro people are around, I'd be very happy to have a discussion about how to make this more consistent across distros, more amenable to users and developers, and how to make things less mysterious, confusing, or fragile. Given how many system tools are being built in Python now (a good thing!), there should be some agreement on the right way to do it.
I'll be at Pycon and would be willing to chat about this at a BOF, over lunch, or over beers. :)
- -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iQCVAwUBR9aPNHEjvBPtnXfVAQJCzgP/QaadzyGxnvA6WqT8B3QsouSVvZvsmg9n LAOnoLYzZOhcLzSUlYiukPcU6DMX8HAA8AaAvwpiyCLmk6IZDGMJxDZH+R8u4+w7 9E4KRdt3yxa5nbcJAMa/fWzjpDTlXSecZBAHw7IAYngy55+fv7cJ7UvWgNqsPdIB h4mUoEU32CU= =I8kv -----END PGP SIGNATURE-----