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
fix(pypi): correctly handle different package versions (#3186)
After merging #3058, I wanted to try creating a `universal` requirements
file for our `sphinx` setup and have an integration test in that way. It
seems that `alabaster` has different versions for different python
versions and we were not handling this correctly. In #3058 I have
attempted adding a unit test for this but it escaped me that the only
time where this bug manifests itself is when the `parse_requirements` is
used multiple times, once per each `python_version`.
With this I think it is safe to say that the #2797 is fixed, because we
found a bug, where we were not skipping requirements.
As an added counter measure, I have added an extra check elsewhere to
catch a regression.
Fixes#2797
logger.warn(lambda: "requirement file has been generated without hashes, will use all hashes for the given version {} that could find on the index:\n {}".format(version, shas_to_use))
378
+
logger.warn(lambda: "requirement file has been generated without hashes, will use all hashes for the given version {} that could find on the index:\n {}".format(version, shas_to_use))
382
379
383
380
forsha256inshas_to_use:
384
381
# For now if the artifact is marked as yanked we just ignore it.
0 commit comments