[reportlab-users] Moving to Bitbucket, and development roadmap..

Andy Robinson andy at reportlab.com
Thu Mar 21 09:11:05 EDT 2013

>> That's one of the main reasons I want to "pull the ladder up" to 2.7.


> BTW if you


> from __future__ import unicode_literals


> then you can use b'byte strings' and 'unicode strings', and have it work

> on all Pythons starting with 2.6.

Yes, but the main way to improve productivity is to have less to worry
about, so we will make it 2.7.

I think that from April we're looking at a 'stable support branch'
which starts with 'reportlab 2.7' release and only gets bug fixes that
actually bit people; and a radical branch that sees some aggressive
changes. The latter will be Python 2.7 and 3.3 - although seeing how
it works on pypy will be intriguing.

> Ensuring you have good test coverage also helps with porting efforts.

> I assume you already know about the best-of-breed solution for this,

> which is https://pypi.python.org/pypi/coverage

Well, when I tried to use it about 8 years ago, it certainly didn't
seem best-of-breed, but it's definitely worth hooking up to our test
suite post release.

> https://pypi.python.org/pypi/tox

> https://pypi.python.org/pypi/detox

Thank you very much for these, which I did not know about. They look
really useful - even for our current release on 25/26/27. Will give
them a try ASAP.

- Andy

More information about the reportlab-users mailing list