doc: Update comparison with hatch in README #2210
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
frostming
approved these changes
Aug 29, 2023
pawamoy
requested changes
Aug 29, 2023
| @@ -66,7 +66,7 @@ instead using a custom `[tool.poetry]` table. This is partly because Poetry came | |||
|
|
|||
| ### [Hatch](https://hatch.pypa.io) | |||
|
|
|||
| Hatch can also manage environments (it allows multiple environments per project, but it does not allow to put them in the project directory), and it can manage packages (but without lockfile support). Hatch can also be used to package a project (with PEP 621-compliant pyproject.toml files) and upload it to PyPI. | |||
| Hatch can also manage environments, allowing multiple environments per project. By default it has a central location for all environments but it can be configured to put a project's environment(s) in the project root directory. It can manage packages but without lockfile support. It can also be used to package a project (with PEP 621/631-compliant pyproject.toml files) and upload it to PyPI. | |||
There was a problem hiding this comment.
Suggested change
| Hatch can also manage environments, allowing multiple environments per project. By default it has a central location for all environments but it can be configured to put a project's environment(s) in the project root directory. It can manage packages but without lockfile support. It can also be used to package a project (with PEP 621/631-compliant pyproject.toml files) and upload it to PyPI. | |
| Hatch can also manage environments, allowing multiple environments per project. By default it has a central location for all environments but it can be configured to put a project's environment(s) in the project root directory. It can manage packages but without lockfile support. It can also be used to package a project (with PEP 621-compliant pyproject.toml files) and upload it to PyPI. |
From the PEP itself:
This PEP has been accepted and was merged into PEP 621.
So I don't think 631 should be listed here 🙂
There was a problem hiding this comment.
Yes, you are right. I thought it was the other way round and 621 was merged into 631.
|
Ha, @frostming too fast! 😅 |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #2204.
Pull Request Checklist
- [ ] A news fragment is added innews/describing what is new.- [ ] Test cases added for changed code.Describe what you have changed in this PR.
Update to README.