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
Before proceeding, please make sure to follow these steps:
I have checked for similar issues in the project's issue tracker.
I have searched closed issues to see if a similar problem was reported
before.
Issue Details
The licensecheck library is scanning the latest version from pypi instead of scanning the specific version from pyproject.toml file
Description
When we ran the licenscecheck against the pyproject.toml file and we have specified versions for the packages.
But it always scanning the latest version of package instead of specific version in pyproject.toml file
example: In pyproject.toml file, we have mongomock-motor==0.0.19
Before You Begin
Before proceeding, please make sure to follow these steps:
before.
Issue Details
The licensecheck library is scanning the latest version from pypi instead of scanning the specific version from pyproject.toml file
Description
When we ran the licenscecheck against the pyproject.toml file and we have specified versions for the packages.
But it always scanning the latest version of package instead of specific version in pyproject.toml file
example: In pyproject.toml file, we have mongomock-motor==0.0.19
Scanned version:
Command used:
licensecheck -u poetry:dev --only-licenses "APACHE SOFTWARE LICENSE" "BSD LICENSE" "ISC LICENSE (ISCL)" "MIT LICENSE" "MOZILLA PUBLIC LICENSE 2.0 (MPL 2.0)" "PUBLIC DOMAIN" "Python Licence 2.0" --ignore-licenses "MOZILLA PUBLIC LICENSE 2.0 (MPL 2.0)" "THE UNLICENSE (UNLICENSE)" -f json
Expected Behavior
It should scan specific version of package mentioned in file.
Actual Behavior
It's not scanning the specific version of package, instead it's scans latest version of package
System Information
Please provide the following additional information about your system or
environment:
The text was updated successfully, but these errors were encountered: