Changes Backported To 1.5.0

[benedikt-brandtner-bikemap]

Hey,

It seems like when you pushed version 1.6 a few hours ago it also updated the prebuilt 1.5 on pypi with the breaking change for python <3.9 (#266).

Might have had something to do with the separate update of the __version__ file but i'm not sure.

[wadevries]

It seems the 1.6.0 version was (also) pushed somehow to the 1.5.0 version on pypi. This spontaneously broke my deployment, even having pinned gpxpy==1.5.0.

The only difference between the installed sources of 1.5.0 and 1.6.0 respectively seems to be the value of __version__:

$ python -m venv gpx150
$ python -m venv gpx160
$ gpx150/bin/pip install gpxpy==1.5.0
$ gpx160/bin/pip install gpxpy==1.6.0
$ diff -r gpx150/lib/python3.11/site-packages/gpxpy gpx160/lib/python3.11/site-packages/gpxpy
diff -r gpx150/lib/python3.11/site-packages/gpxpy/__init__.py gpx160/lib/python3.11/site-packages/gpxpy/__init__.py
19c19
< __version__ = '1.5.0'
---
> __version__ = '1.6.0'

[tkrajina]

That push with the wrong version created a wheel file in addition to the 1.5.0 build file, sorry for that.

Obviously pip prefers the wheel files, and you got the wrong build. I manually deleted the 1.5.0 wheel build from pypi, so it should all work fine now.