[Bug 485944] Re: Upgrade to virtualenv 1.4.5

[Barry Warsaw]

In order to request a sync of Debian python-virtualenv 1.4.5 for Lucid we'll
need an FFe, and to do that, we'll need to know whether any of the
Ubuntu-specific changes in the python-virtualenv 1.3.3-1ubuntu2 are still
necessary.  I've analyzed the three bugs fixed since the last sync to Debian's
python-virtualenv 1.3.3-1.

Bug 520337 - This does not seem to be necessary.  When I built a virtualenv
with a simple test package (e.g. the one in bug 517390) I did not get the
crash described in bug 520337.  However, I did need to modify the virtualenv
command to add the --distribute flag:

% virtualenv --distribute xx
% xx/bin/python setup.py install

This makes sense as our default setuptools is now distribute.  I think we'll
need a patch to enable --distribute by default.

Bug 339904 - This one is no longer necessary because upstream virtualenv
contains this fix in 1.3.4:

 * Added support for the Debian/Ubuntu /usr/lib/pythonX.Y/dist-packages
   directory.

Bug 347203 - This one is no longer necessary either.  I had no problems
building the Debian testing source package on Lucid with pbuilder.

In summary, I think we can and should approve an FFe to sync Debian
python-virtualenv 1.4.5 for Lucid, with a patch to enable --distribute by
default.  I will create a branch for the latter, link it to this bug, and
request the FFe and sync.

-- 
Upgrade to virtualenv 1.4.5
https://bugs.launchpad.net/bugs/485944
You received this bug notification because you are a member of MOTU,
which is a bug assignee.