Opened at 2014-08-30T00:35:57Z
Closed at 2016-03-26T23:15:49Z
#2286 closed defect (fixed)
the version of a library chosen for a setup requirement can conflict with a build requirement
Reported by: | daira | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 1.11.0 |
Component: | packaging | Version: | 1.10.0 |
Keywords: | setuptools build install | Cc: | |
Launchpad Bug: |
Description
This problem happens because setuptools decides on the version of a package specified as a setup_requires dependency, before computing all of the (transitive) install_requires dependencies. So it can happen that it drops an egg into the current directory of the build that then conflicts with a build requirement.
I don't know whether this bug is specific to zetuptoolz or still exists in more recent setuptools versions.
In any case, setuptools delenda est.
Change History (3)
comment:1 Changed at 2015-05-13T11:56:22Z by Daira Hopwood <daira@…>
comment:2 Changed at 2015-07-21T19:05:16Z by zooko
I think a good next-step on this is #2473 (stop using setup_requires).
comment:3 Changed at 2016-03-26T23:15:49Z by warner
- Milestone changed from undecided to 1.11.0
- Resolution set to fixed
- Status changed from new to closed
We no longer use setup_requires=, so we can close this one now.
In 07aa5e76b5faea91f55fc5f566e8b766c7685c51/trunk: