part of what cpython does (did?) in this sort of cases is to ship a *.egg-info for the package that has an external existence as well, like in CPython2.7 you can see there are .egg-info files for wsgiref and argparse in the stdlib dir.
On Fri, Mar 1, 2013 at 11:54 AM, Armin Rigo <ar...@tunes.org> wrote: > 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
