Re: [chirp_devel] Invalid version: 'py3dev' breaks build.

Barry Jackson via chirp_devel wrote:

Hi Dan, Since our (Mageia) most recent python3 updates sometime this month chirp-next builds fail with:

packaging.version.InvalidVersion: Invalid version: 'py3dev'

Since you do not make releases it's difficult to decide on any sort of versioning that makes sense for our packages.

I use 0.4.0 as version and add the date from git into the release, which keeps our packages in order but means little outside of the distro. e.g. chirp-0.4.0-0.20230125.2

The date stamp alone (20230125) is a valid version for Python packaging purposes, which should also work for RPMs. Once PEP-517 support is implemented (for the Python package build process), this will become more of an issue as checks will be stricter.