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
When the same version of a requirement is found in multiple find-links, the reverse lexicographic order is applied.
So no matter if the parameters are:
--find-links ~/release --find-links ~/snapshot
or
--find-links ~/snapshot --find-links ~/release
the version in the snapshot directory will always be used.
Preserving explicit ordering of --find-links would allow specifying a release directory in front so that is always preferred over next links.
This allows promoting a version to the 'release' directory without caring if an automated build accidentally replaces the snapshot version.
This shouldn't matter. If two files have the same name and version, they should be equivalent. If they aren't, that's a problem with the files.
In your case, the snapshots should have different version numbers from the release version. If that's not what you're doing, you're not conforming to the semantics of Python package version numbers.
Agreed, if both files have the same version, the location should be irrelevant.
In your case, the snapshots should have different version numbers from the release version. If that's not what you're doing, you're not conforming to the semantics of Python package version numbers.
When the same version of a requirement is found in multiple find-links, the reverse lexicographic order is applied.
So no matter if the parameters are:
or
the version in the snapshot directory will always be used.
Preserving explicit ordering of --find-links would allow specifying a release directory in front so that is always preferred over next links.
This allows promoting a version to the 'release' directory without caring if an automated build accidentally replaces the snapshot version.
I think I found at least one place at https://github.com/pypa/pip/blob/develop/pip/index.py#L226 where the present code:
could be something like:
The text was updated successfully, but these errors were encountered: