[WIP] Use 'semantic_version' module instead of 'semver' module - Githubissues

ansible / mazer

Experimental Ansible Galaxy Content Manager

GNU General Public License v3.0

114 stars 18 forks source link

[WIP] Use 'semantic_version' module instead of 'semver' module #184

Closed alikins closed 5 years ago

alikins commented 5 years ago

SUMMARY

WIP, replacing use of 'semver' module with 'semantic_version' because

galaxy uses it (and 'semver')
the 'Spec' support in semantic_version is more useful than 'semver' limited support
the 'semantic_version' Version is a little easier to deal with than semver.VersionInfo (mostly the 'partial' support)

MAZER VERSION

name = mazer
version = 0.3.0
config_file = /home/adrian/.ansible/mazer.yml
uname = Linux, newswoop, 4.18.16-100.fc27.x86_64, #1 SMP Sun Oct 21 09:33:00 UTC 2018, x86_64
executable_location = /home/adrian/venvs/galaxy-cli-py3-2/bin/mazer
python_version = 3.6.6 (default, Jul 19 2018, 16:29:00) [GCC 7.3.1 20180303 (Red Hat 7.3.1-5)]
python_executable = /home/adrian/venvs/galaxy-cli-py3-2/bin/python

ADDITIONAL INFORMATION