Hi! Maybe a possible way is that you have "major" releases of cffi without backward incompatible changes that correspond to PyPy releases - so that any cffi 1.x works on PyPy 2.0, and any cffi 2.x works on PyPy 2.1, etc. And than you can complain if there is major version mismatch of cffi. So there will be two cffi branches active at any time - the one that works with released PyPy, and the one that works with nightly.
Thank you for cffi :) 2013/3/1 Armin Rigo <ar...@tunes.org>: > Hi all, hi Jeremy, > > I'm thinking about merging the curses_cffi branch, and I see efforts > going on in sqlite-cffi. Great :-) > > We need to think about how we want to support cffi-based modules in > PyPy. So far the idea is to include the official release of CFFI > together with regular PyPy installations. Then, how can we disable > "pip install cffi" from breaking everything up by installing a > different release of cffi on top of PyPy? Is it enough to detect in > cffi's setup.py "oh, it's PyPy and cffi is already installed, so I'll > do nothing"? Should it still check that the version number matches, > and complain if it doesn't? > > > A bientôt, > > Armin. > _______________________________________________ > pypy-dev mailing list > pypy-dev@python.org > http://mail.python.org/mailman/listinfo/pypy-dev _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
