| Summary: | dev-python/pypy: Missing rpython binary | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Patrick Lauer <patrick> |
| Component: | New packages | Assignee: | Python Gentoo Team <python> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | normal | CC: | alicef, mgorny |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
well ImportError: No module named pypy generally spells you gotta set PYTHONPATH for whatever silly reason it lost its way, but in this case it appears a non standard manouver. I proposed in IRC to just install the pypy folder under /usr/lib/pypy${SLOT}/pypy, rather than try to shoehorn it into site-packages. It's more of a build system than a shared package.
This would require any consumers to set PYTHONPATH to utilize the modules contained therein.
(In reply to Patrick Lauer from comment #0) > Would be very nice to have these components (rpython + pypy/ folder) > installed too. What's the rationale for having it? No reply for 4+ years now. |
After fiddling with the 2.0_beta ebuild to install pypy/bin/rpython: # /usr/lib64/pypy2.0/rpython Traceback (most recent call last): File "app_main.py", line 52, in run_toplevel File "/usr/lib64/pypy2.0/rpython", line 11, in <module> from pypy.translator.goal.translate import main ImportError: No module named pypy Would be very nice to have these components (rpython + pypy/ folder) installed too. If I figure out how to cleanly do that I'll just fix it