#41591: py-setuptools @1.4.1: easy_install-3.4 is already provided by python34 ----------------------------+------------------- Reporter: mojca@… | Owner: jmr@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-setuptools | ----------------------------+------------------- Changes (by mojca@…): * cc: Peter.Danecek@… (added) -- Ticket URL: <https://trac.macports.org/ticket/41591#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X

#41591: python34 @3.4.0b1_1 conflicts with py34-setuptools @1.4.1 on easy_install-3.4 ---------------------------------------+------------------- Reporter: mojca@… | Owner: jwa@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: python34 py34-setuptools | ---------------------------------------+------------------- Comment (by nad@…): See last paragraph of #41549. r113947 did not address that part. -- Ticket URL: <https://trac.macports.org/ticket/41591#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X

#41591: python34 @3.4.0b1_1 conflicts with py34-setuptools @1.4.1 on easy_install-3.4 ---------------------------------------+-------------------- Reporter: mojca@… | Owner: jwa@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: python34 py34-setuptools | ---------------------------------------+-------------------- Comment (by nad@…): Python PEP 453 has a section with [http://www.python.org/dev/peps/pep-0453 /#recommendations-for-downstream-distributors recommendations for downstream distributors]. The basic ideas are that: (1) upstream python- dev has now blessed the third-party `pip` project as "the one obvious way" to install packages (outside of a package management system like MacPorts). (2) python-dev wants to ensure that `pip` is always available to end-users (for the upcoming 3.4 release, at least). (3) To that end, there is now the bundled version of `pip` in the source release ensuring that there is a minimum level of `pip` available for install. (4) It is not the intent of the PEP to preclude installing newer versions of `pip` as they are released. (5) Thus, the best solution for distributors like MacPorts would be to disable the install of the built-in version of `pip`, as was done in r114107, and to make a `py34-pip` port as a run dependency of `python34`. `setuptools` is only included in the built-in wheel for `pip` because it currently supplies some resources for `pip` but the `pip` project is looking to remove that dependency in the future. So `py34-pip` should declare a dependency on `py34-setuptools`, but `python34` should not. Also, PEP 453 originally proposed implementing `ensurepip` for the current maintenance releases, `python33` and `python27`, as well. That requirement was reluctantly removed from the final approved PEP so as not to violate the python-dev policy of no new features in maintenance releases. However, there is nothing preventing third-party distributors from taking the user-friendly step of adding `py33-pip` and `py27-pip` as dependencies for their respective Pythons. -- Ticket URL: <https://trac.macports.org/ticket/41591#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X