Releases: ido50/morgan
Bugfix: some wheels not downloaded
Some package wheels were not downloaded due to overly strict Python interpreter version matching. This version fixes this bug, but comes with a known issue that a small number of unnecessary wheels may also be downloaded. This will be fixed in a future version.
Bugfix: parsing 'requires_python' of certain dependencies may fail
v0.14.3 Version 0.14.3
Upgrade "packaging" dependency to solve issues with non-standard file names
v0.14.2 Bump version
Bugfix: platform_tag should be optional
v0.14.1 Bump version
Multiple mirrors, multi-line values and more
Bugfix: mirroring will fail if no matched files found
v0.13.4 Bump version to 0.13.4
Bugfix: mirroring can fail for some packages
When filtering files of a package to mirror, Morgan checks whether the file's required Python version matches all environments. If a package defines its required version as a simple number instead of an actual specifier (e.g. '3' instead of the correct '==3'), then Morgan would fail when determining whether the file should be downloaded.
This release fixes the issue by forcing such files to have a valid specifier, and also ignoring files that still fail Morgan's verification.
Bugfix: downloaded files may not match all environments
When Morgan mirrors packages, it chooses the most recent version that satisfies the requirement strings, and the environments. However, when matching environments, it would select files (and therefore version) that matches at least one of the Python versions of the environments, which could lead to Morgan choosing versions that do not support all of the Python versions.
This commit fixes this bug by requiring the selected versions match ALL of the Python versions defined in the environments. This could potentially lead to Morgan not finding matches at all, but this would be fixed in a subsequent release by treating each environment independently of the others.
Support any 1.x metadata version when mirroring
This release updates Morgan's mirroring code to support any package metadata version in the 1.x family, not just 1.0.
Allow disabling serving of metadata files
The server will now accept a --no-metadata flag, which will disable serving of metadata files
when provided. This can be useful if installing packages via pip but not providing normalized
names (e.g. pip install FastAPI instead of pip install fastapi). This is to workaround an issue
with pip: when it is provided a non-normalized name, it sends it to the server normalized, but
expects the metadata file returned to have the non-normalized name. However, the server
cannot know what the non-normalized name is. The only way to work around this is to disable
serving of metadata files altogether.