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
So in this case the current version would be list(package.req.specifier)[0].version -> "24.0.0"
Happy to do a PR, but but wasn't sure what we'd want for current_version if the Specifier operator is something other than ==. @achillesrasquinha any thoughts?
If `--requirements` or `--project` flags are used, current_version for
Packages was equal to the specifier in the requirements file
eg. requests==2.24.0 showed current_version as `==2.24.0` rather than
just `2.24.0`
This then caused the `upgrade_type` check later to fail (as the `==`
version prefix made the version difference calculation incorrect
Requirements will now include the version only if an exact version is
specified, otherwise the installed version is used.
If not installed, the entire specifier is used (eg. `~=1.0`)
What's the bug all about?
Upgrade type is ignored when running
--requirements
or--project
(all upgrades included rather than just the specified/default of minor/patch)current version
includes the specifier (in this case==
) not just the numberWhat command led to this issue?
Logs
The text was updated successfully, but these errors were encountered: