Pipx backend allows dev release to satifisfy non-dev release request #8784
Replies: 1 comment 2 replies
-
|
A few observations on this one: Unrelated to pinning Order-dependent behavior Step 1: Use a dev version in one folder Step 2: Use a non-dev version in another folder The behavior here is order-dependent. In the above sequence, the non_dev folder will use the dev version to satisfy its dependency (not expected). But if you reverse the above steps, the non_dev folder will use the non_dev version (as expected). Inconsistent with remote version resolution |
Beta Was this translation helpful? Give feedback.
-
|
Is this because the VERSION_REGEX has -dev but not .dev? |
Beta Was this translation helpful? Give feedback.
-
|
Created #8849 with a proposed fix |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I have notices that after switching a dependency version pin to a dev release and then switching back to the non-dev release of the version, the dev release persists and satisfies that requirement. Here is an example:
The user intent here is to switch back to the non-dev release with the
mise use --pin pipx:yt-dlp@2026.3.3invokation.I understand that this can be fixed with a combination of
mise uninstallandmise clear cache, or using mise.lock files (though that requires opting into experimental), but it is an undesirable situation that a user can get in where they expect to be in a particular version after a specific request (in this case the released version) and still in a dev release.Beta Was this translation helpful? Give feedback.
All reactions