that's how cffi works FYI. +1 from me
On Wed, Jul 19, 2017 at 12:33 AM, <wlavrij...@lbl.gov> wrote: > Hi, > > any objections to renaming cppyy into _cppyy? > > I want to be able to do a straight 'pip install cppyy' and then use it > w/o further gymnastics (this works today for CPython), but then I can't > have 'cppyy' be a built-in module. > > (You can pip install PyPy-cppyy-backend, but then you'd still have to deal > with LD_LIBRARY_PATH and certain cppyy features are PyPy version dependent > even as they need not be as they are pure Python.) > > The pip-installed cppyy will still use the built-in _cppyy for the PyPy > specific parts (low-level manipulations etc.). > > I'm also moving the cppyy documentation out of the pypy documentation and > placing it on its own (http://cppyy.readthedocs.io/), given that the > CPython side of things now works, too. > > Yes, no, conditional? > > Thanks, > Wim > -- > wlavrij...@lbl.gov -- +1 (510) 486 6411 -- www.lavrijsen.net > _______________________________________________ > pypy-dev mailing list > pypy-dev@python.org > https://mail.python.org/mailman/listinfo/pypy-dev _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
