Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
On Wed, 13 Jun 2012 11:16:45 +0200
Dirkjan Ochtman <djc@g.o> wrote:
> Additionally, the new eclass seems to think of pypy1_7, pypy1_8 as
> different. We should probably have something that says, "this ebuild
> supports python-2.7-equivalent pypy".
Are they equivalent API-wise? In other words, is it guaranteed that if
a particular Python extension (written in C) compiles with 1.8, it will
compile with 1.7 and vice-versa?
> Proposal:
>
> - Add python2_7_pypy atom for PYTHON_COMPAT, expands to a list of pypy
> versions which is fixed in the eclass.
Maybe we could just assume pypy1_7 means 1.7+ but older than next
pypy1_x defined.
--
Best regards,
Michał Górny
|
|
