[Python-modules-team] Bug#840084: Bug#840084: python-virtualenv: “Multiple .dist-info directories” when creating virtualenv

[Ben Finney]

On 18-Oct-2016, Barry Warsaw wrote:

> % python2 -m virtualenv /tmp/p2
> Already using interpreter /usr/bin/python2
> New python executable in /tmp/p2/bin/python2
> Also creating executable in /tmp/p2/bin/python
> Installing setuptools, pkg_resources, pip, wheel...done.

The difference turns out to be that, on the host where I encounter
this bug's behaviour, Pip has a build directory with some older build
artefacts remaining.

So this is an expression of the fact Pip seems unable to deal
gracefully with that, surely normal, condition.

When I clear the build directory (and there is another bug here, in
that the above error message gives no indication this is something
that needs to be done, or where to look), Pip no longer complains
about “Multiple .dist-info directories”, and successfully creates the
virtualenv as requested.

That shouldn't be needed, though. Surely the build directory should be
treated as a cache of generated files, and not impede future builds.

-- 
 \      “If you can't beat them, arrange to have them beaten.” —George |
  `\                                                            Carlin |
_o__)                                                                  |
Ben Finney <bignose at debian.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/python-modules-team/attachments/20161102/d4a493bb/attachment-0001.sig>