Hi, So just to get a quick sanity check before I start.
We are missing lzma in py3.3 (or to be more precise we have the beginnings of the module, but it's not passing any tests yet). Philip hinted to me recently that it would make sense to integrate lzmaffi. I would like to work on that, but I will probably get stuck a few times, so I'm planning to do some writeups on my blog as I go along (both for note taking and debugging). Since it's an external project I was planning to follow the same procedure that we use for stdlib, which is described in stdlib-upgrade.txt. So start out with vendor/lzmaffi, then branch off to py3.3-lzmaffi for integration work, finally merge into py3.3. Does that seem like a good approach? Martin 2014-07-23 19:20 GMT+02:00 Peter Cock <p.j.a.c...@googlemail.com>: > Thanks - that will be a useful companion to my backport > for using lzma on C Python 2.6, 2.7 and early Python 3 :) > https://pypi.python.org/pypi/backports.lzma > > Peter > > On Wed, Jul 23, 2014 at 5:14 PM, Armin Rigo <ar...@tunes.org> wrote: >> Hi all, >> >> A module mentioned today in a EuroPython lightning talk: "lzma" >> reimplemented in cffi (compatible with the one from Python 3.3's >> stdlib). >> >> https://pypi.python.org/pypi/lzmaffi >> >> >> A bientôt, >> >> Armin. >> _______________________________________________ >> 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 _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
