Randy Döring

I don't have a strong opinion if we need such a feature and if it should be some explicit `update --force` or `--reinstall-path-dependencies` so waiting for opinions from other maintainers...

pre-commit.ci autofix

> Is there a way to specify a target path for a file to end up in during include? Seems like it is (will be in 1.8) only possible for...

What if you explicitly exclude the versions you don't want, i.e. replacing `version = "0.4.4"` with `version = "==0.4.4,!=0.4.4+cuda11.cudnn86"`?

In the stack trace you can see that `python_full_version` is the culprit. According to [PEP 508](https://peps.python.org/pep-0508/#environment-markers) `python_full_version` is equal to `platform.python_version()`, which is `3.11+` in this case. Although I could...

I re-read PEP 508 and there seems to be an escape hatch for non-compliant versions: > The operators use the [PEP 440](https://peps.python.org/pep-0440) version comparison rules when those are defined (that...

I wouldn't strip the "+" in general in the code parsing versions because it's definitively not valid for package versions (and at least a bad choice for the python version)....

> Is this PR still a possibility? Short-term: no. Mid-term: maybe. See #8562

I don't think an extra changes much. We still have a circular dependency (only if the extra is used but nevertheless...). I think a general solution for plugins that are...

This is quite similar to the issue described in #4695 however not the same. The issue here is that a restricted dependency actually is kind of a hidden multiple constraint...