Cannot define an OSM pre-built data version that isn't also a float

[brynpickering]

Version Checks (indicate both or one)

• I have confirmed this bug exists on the lastest release of PyPSA-Eur.

• I have confirmed this bug exists on the current master branch of PyPSA-Eur.

Issue Description

If you want to define a custom OSM build in data/versions.csv, you are forced to define a valid float version as there is a check def get_osm_archive_files that otherwise fails.

E.g., if I have my own custom build that is an extension of v0.7 that I want to retrieve, I can't call it something like 0.7.1, 0.7-patch or anything like that as they will all fail the check.

Reproducible Example

.

Expected Behavior

Being able to use any versioning scheme I like. This probably requires inverting the current check, to omit map.html if the version is in [0.5, 0.4, 0.3, 0.2, 0.1]

Installed Versions

Details

Replace this line.