[Python-Dev] PEP 376

[Tarek Ziadé]

On Wed, Jul 1, 2009 at 10:35 AM, Paul Moore<p.f.moore at gmail.com> wrote:
> 2009/7/1 Tarek Ziadé <ziade.tarek at gmail.com>:
>>> That (at least as I read it) is a function, not a command.
>>> If it is a command, give an example of its use from the command line
>>> for us poor "don't want to research" people.  If the following works:
>>>
>>>    $ python setup.py uninstall some_package
>>>
>>> Then explicitly say so for us poor schlubs.
>>>
>>
>> Right, I'll add that. Although it will be a reference implementation only.
>
> -1. Where does the setup.py file come from? If I have docutils
> installed, and want to remove it, must I download the source again so
> that I can get the setup.py, so I can run the uninstall? This is daft
> - particularly given that the point of PEP 376 is to ensure that all
> of the required information is available from the installed package!
>
> As I suggested before:
>
>    python -m distutils.uninstall packagename

yes sorry if it was unclear, I was not thinking about adding something
based on setup.py,
but just saying that I was going to add this feature in the PEP. and
it will be of the form:

 python -m distutils.uninstall packagename

>
> Calling it a "reference implementation" should not imply that it's not
> built to be usable and complete. If it's there,m people should be able
> to use it.

It will be usable and complete, but very limited. As someone mentioned,
it will not take care of dependencies and prevent you from removing a
distribution that is mentioned in another distrubution in a
setuptools' install_requires
metadata.

That said, when PEP 345 evolves like we have planned to (adding
install_requires in the metadata)
Then we should be able to provide this kind of warning with no pain.