{"push_id":831544396,"size":1,"distinct_size":0,"ref":"refs/heads/uniq-pip-build-dir","head":"31dcd3e7ab60855d9664bd0aeb87b79eba94913f","before":"294161e3fee91017e2c671e75ea90ed4fbae556d","commits":[{"sha":"31dcd3e7ab60855d9664bd0aeb87b79eba94913f","author":{"email":"b6cfe3904a85eba46dfe8c6f1219f4698f9edd0b@redhat.com","name":"Ian Wienand"},"message":"Use unique build dir for pip installs\n\nThere is a bug in pip [1] where it will choose to install a package\nfrom an existing build-dir if it exists over the version actually\nrequested.\n\nThus if a prior component has installed a later version of the\npackage, the unpacked code is already in /tmp/$USER-pip-build; it gets\nre-installed and manifests in a confusing error along the lines of\n\n---\n Downloading/unpacking requests>=1.1,<1.2.3\n   (from -r /home/stack//python-cinderclient/requirements.txt (line 5))\n   Running setup.py egg_info for package requests\n   Requested requests>=1.1,<1.2.3 (from -r\n   /home/stack/python-cinderclient/requirements.txt (line 5)),\n    but installing version 1.2.3\n...\n  error: Installed distribution requests 1.2.3 conflicts with\n    requirement requests>=1.1,<1.2.3\n---\n\nI believe pip 1.4 fixes this problem, but it should always be safe to\nspecify a unique build-directory for pip installs to avoid picking up\nold versions.\n\nWe also add a cleanup_tmp function for clearing out anything that\nstack.sh might leave around when un-stacking, and add a catch-all for\nthe pip-build dir.\n\n[1] https://github.com/pypa/pip/issues/709\n\nChange-Id: I7ce919cddfd6d6175ae67bd864f82e256ebc7090","distinct":false,"url":"https://api.github.com/repos/ianw/devstack/commits/31dcd3e7ab60855d9664bd0aeb87b79eba94913f"}]}