Installing an updated bundle doesn't install updated code

[sblask]

How to reproduce:

• create a bundle
• install the bundle (in a virtualenv)
• change code, recreate the bundle
• reinstall the updated bundle with --upgrade --force-reinstall
• code in installation is not updated

I verified the bundle is actually updated. The problem seems to stem from the build directory that pip created in the virtualenv. It is not removed after installation and not updated during the installation. The --upgrade and --force-reinstall do actually have an effect (without it returns right away saying requirements are fulfilled), but pip seems to reinstall from the build directory. Removing the build directory fixes the problem for the next install.

pip version: 1.0 (the one coming with virtualenv in Ubuntu 12.10, given there is nothing about bundles in the changelog, I assume it's still the same)

[qwcode]

this is related to #709, which desperately needs to be "fixed" finally.
closing as a dupe to that.

as for bundles, that feature is very likely to be dropped in v1.4 due to it not catching on, and nobody really maintaining it.

[sblask]

That would be a pity as it's very handy and I don't see an alternative to my use case (see my comment on #236 ). I can imagine that just too few people know about it, just like I've got the impression that use of pip and virtualenv are not very widespread. Is there so much to maintain? One would think it's not much more than zipping and unzipping downloaded requirements.

[Diaoul]

bundles is the only way to easily make sdists with dependencies. wheel is cool but it does bdist which doesn't replace sdists.

Is the support really dropped in 1.4?