Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecate bdist_wininst #2040

Merged
merged 2 commits into from
Apr 21, 2020
Merged

Deprecate bdist_wininst #2040

merged 2 commits into from
Apr 21, 2020

Conversation

hugovk
Copy link
Contributor

@hugovk hugovk commented Mar 22, 2020

Deprecate bdist_wininst

For #1988.

Already deprecated in CPython 3.8's distutils.

The deprecation method, message and tests are modelled on the recent #1764 (deprecate "eggsecutable" scripts).

I had a go at the other bdists mentioned in #1988, but had a hard time with the tests, so here's just one to be getting on with.

Pull Request Checklist

  • Changes have tests
  • News fragment added in changelog.d. See documentation for details

Copy link
Member

@jaraco jaraco left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

@pganssle
Copy link
Member

@hugovk I made a change to the news fragment and I've changed the test in two ways:

  1. Flattened it so that it is no longer part of a class (I've noticed we don't usually do this in other test suites, and this one seems particularly unnecessary).
  2. Added the assertion that the original bdist_wininst.run command is invoked as a sanity check.

Let me know if you disagree with these changes, otherwise I'll go ahead and squash my fixup commits into your commits and merge.

@hugovk
Copy link
Contributor Author

hugovk commented Apr 21, 2020

Thanks, both look good!

Do you use some tool for fixing up (I noticed the "fixup! XXX" comments), or just vanilla Git?

@pganssle pganssle force-pushed the deprecate-bdist_wininst branch from cc1b53c to 8487f1a Compare April 21, 2020 18:09
@pganssle
Copy link
Member

Do you use some tool for fixing up (I noticed the "fixup! XXX" comments), or just vanilla Git?

This is vanilla git, you can use git commit --fixup to mark a commit as a fixup for another commit, and then git rebase --autosquash to automatically squash the fixups into the relevant commits. Here's an article I found on it: https://thoughtbot.com/blog/autosquashing-git-commits

There is a fancy tool that I've been starting to use lately (I got hooked on it when using hg at work), called git-absorb: https://github.com/tummychow/git-absorb

This will automatically determine what parts of whatever you've staged belongs with what commits and create fixup commits for it. Very handy for my workflow.

@mergify mergify bot merged commit 92ca9ea into pypa:master Apr 21, 2020
@hugovk hugovk deleted the deprecate-bdist_wininst branch April 21, 2020 19:14
@hugovk hugovk mentioned this pull request Sep 9, 2021
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants