-
-
Notifications
You must be signed in to change notification settings - Fork 307
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
Feature: Support dynamic optional-dependencies
in hatch env
#1349
Comments
hatch env
hatch env
hatch env
optional-dependencies
in hatch env
Can you please try master to see if this fixes it? #1387 |
Tried, seems it still does not work for airflow:
to:
Change back pyproject.toml tpo
Re-install airflow in
|
This is a very draft proposal on how to fix pypa#1348 and pypa#1349 - more to see if this is a good direction. It should likely be split to two PRs (and of course tests and docs are needed): * extending custom metadata plugin to allow different versions for standard and editable builds (also including extending the hatchling CLIs. * extending hatchling interface used by hatch to include standard/ editable version when querying hatchling for available dependencies Not all changes have been yet applied, this is more to check if this is the right direction.
This is a very draft proposal on how to fix pypa#1348 and pypa#1349 - more to see if this is a good direction. It should likely be split to two PRs (and of course tests and docs are needed): * extending custom metadata plugin to allow different versions for standard and editable builds (also including extending the hatchling CLIs. * adding version to CLI where hatch queries hatchling to include standard/ editable version when querying for available dependencies. Not all changes have been yet applied, this is more to check if this is the right direction.
This is a very draft proposal on how to fix pypa#1348 and pypa#1349 - more to see if this is a good direction. It should likely be split to two PRs (and of course tests and docs are needed): * extending custom metadata plugin to allow passing version through hook's version property to distinguish standard and editable builds (also including extending the hatchling CLIs. * adding version to CLI where hatch queries hatchling to include standard/ editable version when querying for available dependencies. Not all changes have been yet applied, this is more to check if this is the right direction.
This is a very draft proposal on how to fix pypa#1348 and pypa#1349 - more to see if this is a good direction. It should likely be split to two PRs (and of course tests and docs are needed): * extending custom metadata plugin to allow passing version through hook's version property to distinguish standard and editable builds (also including extending the hatchling CLIs. * adding version to CLI where hatch queries hatchling to include standard/ editable version when querying for available dependencies. Not all changes have been yet applied, this is more to check if this is the right direction.
This is a very draft proposal on how to fix pypa#1348 and pypa#1349 - more to see if this is a good direction. It should likely be split to two PRs (and of course tests and docs are needed): * extending custom metadata plugin to allow passing version through hook's version property to distinguish standard and editable builds (also including extending the hatchling CLIs. * adding version to CLI where hatch queries hatchling to include standard/ editable version when querying for available dependencies. Not all changes have been yet applied, this is more to check if this is the right direction.
This is a very draft proposal on how to fix pypa#1348 and pypa#1349 - more to see if this is a good direction. It should likely be split to two PRs (and of course tests and docs are needed): * extending custom metadata plugin to allow passing version through hook's version property to distinguish standard and editable builds (also including extending the hatchling CLIs. * adding version to CLI where hatch queries hatchling to include standard/ editable version when querying for available dependencies. Not all changes have been yet applied, this is more to check if this is the right direction.
Currently when project defines "optional-dependencies" as
dynamic
property, hatch cannot use such dynamic property inenv
definition.Example is Apache Airflow. After we turned optional-dependencies to
dynamic
field, we had to removedevel
from features:https://github.com/apache/airflow/blob/main/pyproject.toml#L159
When you try to use
devel
feature:The
hatch env
command almost immediately fails with:The text was updated successfully, but these errors were encountered: