Date: Mon, 24 Apr 2017 08:18:08 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 217044] devel/py-setuptools: Upgrade to 34.1.1 Message-ID: <bug-217044-21822-6HewufBAN1@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-217044-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-217044-21822@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217044 Kubilay Kocak <koobs@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |216953 --- Comment #16 from Kubilay Kocak <koobs@FreeBSD.org> --- For what it's worth, and albeit belatedly, I'm strongly -1 on using ensurep= ip to boostrap instead of the setuptools/pip ports for the same and additional reasons as John someone captures in comment 3 and comment 3. Namely:=20 - static versions - per python port (currently 4, but at best 3 (the number of concurrently supported upstream bugfix branches at any one time) - that receive no bugfixes (unless we backport them) and - unless they are manually hacked/updated in the pythonXY ports by ourselves Instead I would have the pythonXY ports depend on the setuptools/pip ports = so that they are guaranteed to be provided in a new installation (as PEP453 [1] recommends): "Ensure that whenever Python is installed pip is either installed or is otherwise made readily available to end users. " It appears that the only requirement here is that setuptools/pip is guarant= eed to be available for the framework (USES=3Dwheel or otherwise) to use. There= is no apparent or explicitly mentioned requirement for that to happen via the private/vendored setuptools/pip (ensurepip) module. Further, having the framework utilise one version of setuptools/pip and oth= er parts of a users environment (site-packages and/or virtual environments) potentially or actually use another is a major issue.=20 Addressing that issue by manually upgrading private/vendored copies of pip/setuptools in lang/pythonXY ports with patches or framework in-place upgrades is also likely to cause issues. It also means multiple (one per python port) combinations of setuptools/pip= to maintain, bug check, test and upgrade than one. Finally, setuptools/pip (the upstream separate PyPI packages) are intended = to support all currently supported Python branches at once within the same version, and breakages are considered bugs/regressions. We should leverage = that level of support by using them. [1] https://www.python.org/dev/peps/pep-0453/ Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216953 [Bug 216953] devel/py-setuptools: egg_info fails under python 3.4.6 on nonexistent MANIFEST graft --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-217044-21822-6HewufBAN1>