Closed robert-schmidtke closed 2 years ago
Hi @robert-schmidtke, since version 1.28.2. pg8000 queries its own metadata to find pg8000.version, so it does something very like the code you wrote above:
from importlib.metadata import version
version("pg8000")
If you unzip the Wheel file for pg8000 you'll see a /pg8000-1.29.1.dist-info/
directory and within it a METADATA
file where the version is contained.
I'm not too sure how conda works, but as I understand it, it has its own package format, which includes a version. I guess one question is: is the version in the conda package correct? If it isn't correct then that would need to be corrected, if it is correct then it seems that it's done in a way that the python metadata library doesn't understand. Either way, hopefully my answer helps a bit :-)
This was due to a misconfigured conda-forge build setup and is fixed in https://github.com/conda-forge/pg8000-feedstock/pull/50. The issue here can be closed.
Looks like this has been fixed now so I'll close the bug, but feel free to reopen if it's still a problem.
Disclaimer: I posted this issue on the conda feedstock already, as I thought it would be related to
conda
, aspip
works just fine: https://github.com/conda-forge/pg8000-feedstock/issues/49Issue
Not sure when this was introduced, but when installing the conda package, the pg8000 version is reported as 0.0.0. pip is fine.
I noticed there was something related to the package version fixed earlier this year in pip, so maybe this is related?
Installed packages
Environment info