On Thu, Apr 30, 2009 at 3:32 PM, David Lyon <david.lyon@preisshare.net> wrote:
On Thu, 30 Apr 2009 14:43:42 +0200, Tarek Ziadé <ziade.tarek@gmail.com> wrote:
That's true that they can be installed anywhere. But there always needs to be an entry in a .PTH file along the python path to specify where the files were installed to.
You don't specify in this pth file that the package "foo" installed the script "bar" in the bin/ directory of your python installation.
But during package installation, this information will be written into a .PTH file somewhere along the python path...
No, you just have a list of relative paths to installed package there that's it.
If you have a deinstallation facility, then it must work for new packages as well as old. Otherwise, imho there's just no point.
See David C. comment. How do you expect such a system to properly install a project that was installed in an unknown manner in the past ? You don't even know what packages were installed for your project unless you digg into the source distribution. For example, if a project installs two packages in your Python, how do you know it ? A project is not a self-contained directory we can remove recursively Cheers Tarek -- Tarek Ziadé | http://ziade.org