Hi Van, 2014-12-05 16:38 GMT+01:00 VanL <van.lindb...@gmail.com>:
> Hi all, > > I’ve been doing some experiments with pypy and I would interested in > making parts of the codebase more 3x compatible. As a first step, I notice > that there are slight differences between the lib_pypy shipped in the 2.7 > and 3.2 releases. How would people feel about reducing the duplication by > consolidating the lib_pypy implementations? > lib_pypy is a portion of the stdlib. It contains the modules that CPython implements in C, and that PyPy decided to implement in pure Python. They describe a different version of Python, and have different features. And why would you want to consolidate the code there, and not say in urllib2.py or unicodeobject.py? The strategy would be: > > - vendor six.py within lib_pypy > - unify implementation as much as possible, using either compatible syntax > or six helpers > - if the implementation cannot be unified, putting individual > implementations behind six.PY2 or six.PY3 conditionals > > Thoughts? > > Thanks, > Van > > > _______________________________________________ > pypy-dev mailing list > pypy-dev@python.org > https://mail.python.org/mailman/listinfo/pypy-dev > > -- Amaury Forgeot d'Arc
_______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev