On Sun, Sep 20, 2009 at 20:52 +0200, Piotr Ożarowski wrote:
> If user/administrator is not following FHS and touching files outside
> /usr/local, it's his problem. /usr/local and /etc is where administrator
> can do his changes/improvements.
I completely agree! Did I give you reason to believe that I actually
propose such insane actions? All I did is to give a very *extreme*
example of insane actions that could be taken by admin managing their
Python environments.
> Sure there are *many* insane Python developers who suggest
> "sudo easy_install Foo"[0] to their users, but then, when these users
> come to me[1] all I'm proposing is to reinstall[2] their system (which you
> should almost[3] never do on Debian).
>
> [0] which installs eggs system wide (sic!)
> [1] believe me, after tracking 10th problem that was caused by local
> modifications, first thing you check next time is:
> `grep \.egg bug_report_with_traceback`
> [2] think twice before you will try to convince me you can uninstall
> eggs
> [3] last time I reinstalled my system was when I changed architecture,
> and believe me - my system is one huge playground
I am totally with you on that. Which is why I try to avoid setuptools
as hard as I can and use plain distutils to package my software and
urge users to install them to PREFIX /usr/local or use
--install-layout=deb. And if they insist on using python package
managers i suggest them to use pip w/ virtualenv instead of
easy_install which luckily does not install eggs and will not
contaminate the global environment.
I don't see how this is related to the intention of my original post
which was the *suggestion* for a policy change to require *either*
'/usr/bin/python' or '/usr/bin/env python' so that Python programs
installed with apt* show consistent behaviour.
And to reiterate another point: If I as a user change my Python
environment is it unreasonable to assume that all Python software will
run in that environment?
Are there *any* reasons that I am not aware of to use '/usr/bin/python'
instead of '/usr/bin/env python' ?
with kind regards
Wolodja Wentland
Attachment:
signature.asc
Description: Digital signature