We've noticed with @befeleme that when a custom version is specified, some metadata only relevant to the latest release is obtained from PyPI API.
More specifically, whenever pyp2conf.py accesses self.package_data["info"], the information is relevant to the latest release and not to the one the packager tries to package.
We've noticed with @befeleme that when a custom version is specified, some metadata only relevant to the latest release is obtained from PyPI API.
More specifically, whenever pyp2conf.py accesses
self.package_data["info"]
, the information is relevant to the latest release and not to the one the packager tries to package.Examples:
https://github.com/befeleme/pyp2spec/blob/71d6dae7d85cacf0c47d5a49aebb0357d6996573/pyp2spec/pyp2conf.py#L171-L173
https://github.com/befeleme/pyp2spec/blob/71d6dae7d85cacf0c47d5a49aebb0357d6996573/pyp2spec/pyp2conf.py#L134