[MacPorts] #47088: Portfile for pypy-pip
#47088: Portfile for pypy-pip -----------------------+-------------------------------- Reporter: rlmaers@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: -----------------------+-------------------------------- Hi, I've installed pypy, and would greatly appreciate a port for pip. That is: pip for pypy, such that I could install additional modules which are recognized by pypy. -- Ticket URL: <https://trac.macports.org/ticket/47088> MacPorts <https://www.macports.org/> Ports system for OS X
#47088: Portfile for pypy-pip ------------------------+-------------------------------- Reporter: rlmaers@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: | ------------------------+-------------------------------- Changes (by ionic@…): * cc: rlmaers@… (removed) Comment: The reporter always gets notifications on changes. -- Ticket URL: <https://trac.macports.org/ticket/47088#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X
#47088: Portfile for pypy-pip ------------------------+-------------------------------- Reporter: rlmaers@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: | ------------------------+-------------------------------- Comment (by ryandesign@…): This would be different somehow from the existing py27-pip port? -- Ticket URL: <https://trac.macports.org/ticket/47088#comment:4> MacPorts <https://www.macports.org/> Ports system for OS X
#47088: Portfile for pypy-pip ------------------------+-------------------------------- Reporter: rlmaers@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: | ------------------------+-------------------------------- Comment (by larryv@…): Presumably the new port would depend on and install modules for [https://www.python.org/download/alternatives PyPy instead of CPython]. -- Ticket URL: <https://trac.macports.org/ticket/47088#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X
#47088: Portfile for pypy-pip ------------------------+-------------------------------- Reporter: rlmaers@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: | ------------------------+-------------------------------- Comment (by rlmaers@…): That is correct. As of right now, there is no way to install additional modules without tampering with the MacPorts installation or installing pypy outside of the scope of MacPorts (at least as far as I know). -- Ticket URL: <https://trac.macports.org/ticket/47088#comment:6> MacPorts <https://www.macports.org/> Ports system for OS X
#47088: Portfile for pypy-pip ------------------------+-------------------------------- Reporter: rlmaers@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: | ------------------------+-------------------------------- Comment (by petr@…): I believe this request is formally not completely accurate. What we probably want here is an enhancement of the Python Portgroup, so that `py-` ports could be configurable to install modules against the PyPy interpreter. That is something like ``` python.versions py 27 34 ``` (or `python.add_pypy yes`, or what ever) would enable a `pypy-` subport, and `pypy-pip` (or `pypy-setuptools`) would be only one of these. Note also, that it is probably not desirable users use pip directly into a site-packages location. -- Ticket URL: <https://trac.macports.org/ticket/47088#comment:7> MacPorts <https://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts