-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
✨ universal locks across environments #17
Conversation
a399534
to
eeb5544
Compare
I see there are some missed assumptions about "default" stuff in Hatch. https://hatch.pypa.io/1.7/config/environment/overview/#inheritance Hatch environments have inheritance of all values. Any environment can choose to inherit from another environment. Multiple levels of inheritance are possible. The config for that is called The environment named "default" has only these special things about it:
I can create a new environment named "shmefault" and never use "default". And here's an example of 2-level-deep inheritance: [envs.shmefault]
template = "shmefault"
dependencies = ["dep1"]
[envs.env2]
template = "shmefault"
extra-dependencies = ["dep2"]
[envs.env3]
template = "env2"
Further: [envs.default]
skip-install = true
dependencies = ["dep1"]
[envs.env2]
skip-install = false
extra-dependencies = ["dep2"] So here the "default" env will have only |
Separate comment: the config |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good stuff!
🎉 This PR is included in version 1.1.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Closes #12
Summary
pip-compile-strip-extras
feature as all lock files will need to be constraints compatible.lock.PipCompileLock
. This will help to eventually integrate the header functionality into a CLI outside of a hatch pluginSee requirements-docs.txt as an example.