[Python-Dev] Issue20846 [was: Cherry-pick between Python 3.4 RC2 and final?] (original) (raw)

Ned Deily nad at acm.org
Tue Mar 4 00:47:37 CET 2014

In article <CADiSq7ftyqu9+RgLCk54gMTWkTCcak97pVAfDJSzQ9NjQfuc8g at mail.gmail.com>, Nick Coghlan <ncoghlan at gmail.com> wrote:

On 4 Mar 2014 08:40, "Mark Lawrence" <breamoreboy at yahoo.co.uk> wrote: > Will this impact on the decision http://bugs.python.org/issue20846 ? No. I never claimed pip was bug free (any more than CPython itself is), merely the best available option.

File a bug against pip (assuming there isn't one already), get it fixed, and we'll bundle the fixed version with the next CPython maintenance release.

FTR, the behavior documented in Issue20846 has nothing to do with either pip, setuptools, or python3.4. See updates to the issue.

One could argue about whether pip should check and, by default, not offer to download and install packages that are marked in PyPI as not being compatible with the Python version being used, e.g. trying to install a Python 2 only package with a Python 3 or vice versa. AFAIK, neither pip nor easy_install (setuptools) has ever done that. And, in any case, it would not have helped with the package in question as it does not specify in its package metadata (as shown on PyPI) with which versions of Pythons it is supported. I don't know whether a request for such a feature has ever been made for pip; I didn't see any on a quick search of the pip tracker. But this is off-topic for python-dev.

-- Ned Deily, nad at acm.org

More information about the Python-Dev mailing list