We have tags for v00.01.07 and v00.02.00, so the python package information is out of date. The version field should have been updated in the commit that was tagged with each version.
I think there are some limitations on the formatting of the value for the version field in setup.py so we'll have to figure out what the best way forward is there.
We should at least tag a v00.02.01 that bumps the package version to move beyond the current situation.
amboar
commented
3 years ago
We have tags for v00.01.07 and v00.02.00, so the python package information is out of date. The version field should have been updated in the commit that was tagged with each version.
I think there are some limitations on the formatting of the value for the version field in setup.py so we'll have to figure out what the best way forward is there.
We should at least tag a v00.02.01 that bumps the package version to move beyond the current situation.