From owner-freebsd-python@freebsd.org Mon Apr 24 08:18:08 2017 Return-Path: Delivered-To: freebsd-python@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8C5F8D4CA8C for ; Mon, 24 Apr 2017 08:18:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 7583F7FE for ; Mon, 24 Apr 2017 08:18:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 71B1ED4CA8B; Mon, 24 Apr 2017 08:18:08 +0000 (UTC) Delivered-To: python@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6FB3FD4CA8A for ; Mon, 24 Apr 2017 08:18:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 498EE7FD for ; Mon, 24 Apr 2017 08:18:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v3O8I7V3019786 for ; Mon, 24 Apr 2017 08:18:08 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 217044] devel/py-setuptools: Upgrade to 34.1.1 Date: Mon, 24 Apr 2017 08:18:08 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: needs-patch X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: python@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? exp-run? X-Bugzilla-Changed-Fields: blocked Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Apr 2017 08:18:08 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217044 Kubilay Kocak changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |216953 --- Comment #16 from Kubilay Kocak --- 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.=