[reportlab-users] ReportLab 3.x packaging and deployment

Robin Becker robin at reportlab.com
Tue Jan 14 11:37:44 EST 2014

On 14/01/2014 14:46, Stephan Richter wrote:

> On Tuesday, January 14, 2014 10:22:02 AM Robin Becker wrote:

>> 3) modify setup.py to override distutils setup with setuptools.setup


> I am not sure what your hesitation about requiring setuptools is. Is anyone

> not using it these days? (I feel very sorry for those people.)


> So I would just use and require setuptools.

I don't use it. Nor Pip, I prefer to download and compile from source which
often works, but not always. For packaging I use distutils directly. It seems to
me that every extra requirement that has to be handomatically done is an extra
step that can be forgotten, botched or fail to complete.

If there were really a consensus that setuptools is the one way to do it, it
would have won over everyone a long time ago and already be in the standard
library. I don't like complicated pth files; they are yet another error vector
and are not really required if 'the way to go' is virtualenv/venv.

The official guide (dated November 2013)


suggests that pip will likely be in 3.4, but it's not certain. If that's the
case then that should take care of the end user side of things. I can use
setuptools if that is required on the packaging side, but I don't like the name
changing it does to the site-packages target.
Robin Becker

More information about the reportlab-users mailing list