Install order when using: pip install --upgrade somepackage

[vbabiy]

It looks like pip is installing the package to be updated before upgrading the dependencies. Aside from being kind of strange behavior, consider the following:

• mymodule requires Twisted
• Twisted has a plugins/ directory in which all third-party modules must copy their plugins.
• pip install mymodule installs the dependencies, then mymodule as expected.
• pip install --upgrade mymodule removes, re-installs mymodule first, then the dependencies. This means that Twisted is removed, then re-installed, wiping that plugins directory. It won't be repopulated, since mymodule has already been upgraded.

I'm not sure if this should be a bug, but I can't figure out why we'd want this order instead of the inverse. Whether it be fixing the "bug" or providing a flag to tell pip to install dependencies first, this would save me a whole lot of headache. I'm using Twisted here as a convenient example, but this scenario can hinder other projects as well.

If I didn't explain this well enough, reply and let me know. Thanks!

---

• Bitbucket: https://bitbucket.org/ianb/pip/issue/222
• Originally Reported By: Greg Taylor
• Originally Created At: 2011-03-03 19:57:09

[dustinlacewell]

I am currently dealing with this issue as well for my own package. Plugins overwrite the namespace package. Let's upgrade dependencies first - like vbabiy says, or add a flag.

[bersace]

Hi,

Same issue here. Is it possible to have a path entry for each egg installed ? Easy_install did like this. As long as pip doesn't do te same way, it will break existing projects that use the loosly designed plugin system of twisted.

Any plan to support back per egg directory ?

Regards,
Étienne

[bersace]

I fixed the issue by having a custom "site-package" dir in my project, containing twisted/plugins/.

[dstufft]

I believe this is fixed now.