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

Rename the project to pyproject-hooks and trim scope #151

Merged
merged 9 commits into from
Oct 31, 2022

Conversation

pradyunsg
Copy link
Member

@pradyunsg pradyunsg commented Oct 29, 2022

Toward #136
Closes #142, by removing the functionality it is requesting changes to.
Closes #91, by removing the functionality that it is tracking removal of.
Closes #49, by removing the functionality it is requesting changes to.

This is the first step, listed in #136 (comment).

This more clearly indicates the files that will eventually become
importable.
This functionality does not need to be maintained after this project is
renamed.
This template is not going to be necessary since this project will have
dropped these bits of functionality.
This more accurately reflects what this project is for.
This is a better name for the functionality provided by this class.
This makes the imports for this package cleaner.
This makes it clearer that this sub-package is intended to be a private
implementation detail.
This Python version is post-EOL.
@pradyunsg pradyunsg marked this pull request as ready for review October 30, 2022 04:11
@pradyunsg
Copy link
Member Author

There are a few more "obvious" improvements, like moving to [project] metadata, automated formatting, improving the documentation and adding type annotations.

I suggest that we make those improvements in follow ups.

quiet_subprocess_runner,
)

__version__ = '0.13.0'
Copy link
Member

Choose a reason for hiding this comment

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

Wouldn't this call for either a major version bump or versioning reset, since this practically makes this a new project from an end-user perspective?

Copy link
Member

Choose a reason for hiding this comment

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

I don't think it's required, because with the name change there's no risk of unwittingly upgrading. But I'd be happy enough to call it 1.0 now that we're cutting off the deprecated bits of API.

README.rst Outdated Show resolved Hide resolved
@takluyver takluyver merged commit 1ea3e23 into pypa:main Oct 31, 2022
@takluyver
Copy link
Member

Thanks @pradyunsg !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants