Pip does not find older versions

[psarka]

It seems that only recent versions of this library are available on Pypi. This breaks my build every week or so, as I pin down the exact version dependencies in my requirements.txt file, like:

PyGeodesy==17.5.25

I would guess this is a reasonably standard practice, so maybe the older versions of the library could be kept on Pypi?

[mrJean1]

My apologies. There was an issue serious enough to remove older versions. But I will refrain from doing that in the future.

[psarka]

Great, thank you!

[mrJean1]

Another rev 17.6.14, no package changes, only fixes of some ellipsoidal and other tests and for running tests in Pythonista on iOS. Rev 17.6.4 is still there as well as 17.5.30.

[mrJean1]

PyGeodesy-17.6.19 replaces all previous 17.6.* versions. No functionality changes, only refactoring of the tests, renaming of the 'test' directory and a new module unitTestSuite to run unittest. The only previous, obsolete versions still present on PyPI are PyGeodesy-17.6.4 and -17.5.30.

[mrJean1]

New method unregister for Datums, Ellipsoids and Transforms in PyGeodesy-17.6.21. Several other changes in the tests.

[mrJean1]

PyGeodesy-17.6.23 with more test-only updates replaces -17.6.21.

[GliderGeek]

i had the same problem, thanks for taking action on this 👍

[mrJean1]

My apologies, I removed PyGeodesy-17.9.22 from PyPI by accident and can't restore it with the original name.

[mrJean1]

PyGeodesy-17.11.26 replaces -17.11.24 to fix another nearestOn2 bug and the latter has been removed from PyPI.

[GliderGeek]

i thought you decided to no longer delete versions?

an alternative versioning system is semantic versioning: https://semver.org/

this enables automatic updates on only patch versions (bug fixes):
https://stackoverflow.com/a/8811418/4629173

[mrJean1]

A few releases with a serious bugs have been removed, there is no point keeping those.

[psarka]

I would suggest keeping all the versions, even the ones with serious bugs -- they will always be there and it's fine. This way you would leave it up to downstream users to decide when to update, instead of forcing their hand by breaking installation scripts :)