That's a straw man, this has enough inconsistency potential to break many edge
cases in ugly ways,
So global setup is out.
Projects themselves can really just switch to pip commands, same goes for
packagers and other tool makers
Explicit is better than implicit, and in this case it also won't cost
additional maintenance on setuptools.
Please keep in mind, that setuptools is completely on volunteer time, and the
time given to it is scarce.
Am 7. Dezember 2015 05:36:42 MEZ, schrieb Nick Coghlan <ncogh...@gmail.com>:
>On 4 December 2015 at 17:55, Ronny Pfannschmidt
><opensou...@ronnypfannschmidt.de> wrote:
>> But it still needs a change in command
>> A direct switch to a real pip command comes with a free
>implementation and zero additional features to maintain in setuptools
>
>The key point here is that opting in to this new behaviour would just
>mean setting a new configuration flag in pydistutils.cfg on the system
>doing the build/install, or adding a new option to the list of options
>passed to the install command. That's a significantly lower barrier to
>entry than finding all of the occurrences of "./setup.py install" in
>existing packaging and deployment scripts and converting them over to
>use "pip install" instead, especially since all the *other* command
>line flags would continue to be the setuptools flags rather than the
>pip ones.
>
>Cheers,
>Nick.
>
>--
>Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig
