Discovered whilst testing #113 and #111, and present in version 2.15.1.
Due to some Python projects not always historically adhering to Python Standards, the situation can currently arise whereby a user is viewing a Python Project version (e.g. https://pypi.org/project/Twisted/19.2.0/) and no Remediation is returned by Sonatype Lifecycle and thus no Remediation path is presented to the user.
This has been tracked to the fact that the source distributions for this Python project have changed extension over time, and when we ask Sonatype Lifecycle for the next safe version against pkg:pypi/twisted@19.2.0?extension=tar.bz2, there are none returned, as the next safe version of Twisted is pkg:pypi/twisted@23.10.0?extension=tar.gz - note the change in extension.
Describe the bug
Discovered whilst testing #113 and #111, and present in version 2.15.1.
Due to some Python projects not always historically adhering to Python Standards, the situation can currently arise whereby a user is viewing a Python Project version (e.g. https://pypi.org/project/Twisted/19.2.0/) and no Remediation is returned by Sonatype Lifecycle and thus no Remediation path is presented to the user.
Conversely a working version is https://pypi.org/project/Twisted/22.8.0/.
This has been tracked to the fact that the source distributions for this Python project have changed extension over time, and when we ask Sonatype Lifecycle for the next safe version against
pkg:pypi/twisted@19.2.0?extension=tar.bz2, there are none returned, as the next safe version of Twisted ispkg:pypi/twisted@23.10.0?extension=tar.gz- note the change in extension.