You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes (like in my case) there are different requirements.txt files for different python versions. Currently the only way to enforce package installation based on python version is in the requirements.txt file level i.e.: requirements.txt
And add this capability to [tool.hatch.metadata.hooks.requirements_txt] as well as to [tool.hatch.metadata.hooks.requirements_txt.optional-dependencies]
The text was updated successfully, but these errors were encountered:
Sometimes (like in my case) there are different
requirements.txt
files for different python versions. Currently the only way to enforce package installation based on python version is in therequirements.txt
file level i.e.:requirements.txt
requirements-python-37.txt
It will be much cleaner setting the
python_version
on thehatch
level similar to this:And add this capability to
[tool.hatch.metadata.hooks.requirements_txt]
as well as to[tool.hatch.metadata.hooks.requirements_txt.optional-dependencies]
The text was updated successfully, but these errors were encountered: