Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Ensure pip's release process automation works on Windows
See original GitHub issueGiven the recent automation added to our release process (see #2314 for details), I know that it’ll work on MacOS (and, likely Linux) systems because I’ve tested that. I expect that it works on Windows, but I’ve not been able to test that.
It’d be great if someone could try it out on Windows, to make sure things work as expected there as well. This is basically someone running the prepare-release and build-release nox commands, to make sure they work well on Windows.
I’ve assigned folks that I know run Windows machine and informally agreed to try this when they’d find time to tackle this. If a new contributor wants to try this out, please go through step 1-4 here: https://pip.pypa.io/en/latest/development/release-process/#creating-a-new-release
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@pradyunsg We only care about Python 3 for the release script, right? I’ve filed #7600 for the line ending thing, but there are some… complications on Python 2.
#7598 created for the version file issue. It’s failing on MacOS, which I assume is not the fault of the PR, as we don’t have tests for the automation scripts. I’ll try to look at the failures later on or maybe tomorrow,