Opened at 2015-07-21T19:04:20Z
Closed at 2016-03-26T23:17:12Z
#2473 closed enhancement (fixed)
stop using `setup_requires` on Windows
Reported by: | zooko | Owned by: | daira |
---|---|---|---|
Priority: | normal | Milestone: | 1.11.0 |
Component: | packaging | Version: | 1.10.1 |
Keywords: | setuptools windows | Cc: | |
Launchpad Bug: |
Description (last modified by daira)
If we removed the remaining use of setup_requires, which applies only to Windows, I think it would fix at least the following tickets:
- #2286 (the version of a library chosen for a setup requirement can conflict with a build requirement)
- #2066 (setup.py performs work without a command being specified)
and it would be the next-step on improving these ones:
Change History (3)
comment:1 Changed at 2015-07-21T20:07:52Z by daira
- Description modified (diff)
- Keywords windows added
- Summary changed from stop using `setup_requires` to stop using `setup_requires` on Windows
comment:2 Changed at 2015-10-27T22:13:16Z by daira
The Magic Folder branch, https://github.com/tahoe-lafs/tahoe-lafs/commits/1431.magic-folder-windows.2, does not use setup_requires.
comment:3 Changed at 2016-03-26T23:17:12Z by warner
- Milestone changed from undecided to 1.11.0
- Resolution set to fixed
- Status changed from new to closed
We've stopped using setup_requires= everywhere, so this can be closed out.
Note: See
TracTickets for help on using
tickets.
I think that we should press ahead with #2077 for non-Windows platforms and worry about removing the use of setup_requires on Windows later. This would avoid some thorny problems, including the fact that zetuptoolz does strange things on Windows to support running scripts.