upstream/certbot
1
0
Fork 0
mirror of https://github.com/certbot/certbot.git synced 2026-06-06 23:32:06 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 2
certbot/certbot-compatibility-test
History
Florian Klink 25e79e4aca
tree-wide: use LooseVersion instead of StrictVersion (#8081) 
According to `distutils/version.py`, StrictVersion is pretty strict in
what version numbers to accept:

> A version number consists of two or three dot-separated numeric
> components, with an optional "pre-release" tag on the end.  The
> pre-release tag consists of the letter 'a' or 'b' followed by a number.

This assumption already fails for some pretty basic python libraries
itself, like setuptools, also available in `46.1.3.post20200610`, a
completely valid version number according to
https://www.python.org/dev/peps/pep-0440/#post-releases.

There doesn't seem to be a particular reason on why StrictVersion has
been used here, so let's use LooseVersion, to be compatible with these
versions.

Co-authored-by: Adrien Ferrand <adferrand@users.noreply.github.com>
2020-06-19 17:11:35 +02:00
..
certbot_compatibility_test Do not require mock in Python 3 in certbot-compatibility-test module (#7899) 2020-04-15 11:40:03 -07:00
nginx Reorganize imports (#7616) 2019-12-09 15:50:20 -05:00
Dockerfile Remove --no-site-packages outside of certbot-auto. (#7832) 2020-03-09 13:05:35 -07:00
Dockerfile-apache Add certbot-compatibility-test Dockerfiles 2016-08-10 16:08:30 -07:00
Dockerfile-nginx Add certbot-compatibility-test Dockerfiles 2016-08-10 16:08:30 -07:00
LICENSE.txt s/letsencrypt/certbot letsencrypt-compatibility-test 2016-04-13 16:58:21 -07:00
MANIFEST.in Remove unused certbot-compatibility-test docs (#7577) 2019-11-22 12:54:18 -08:00
README.rst Rename misc files 2016-04-14 10:20:23 -07:00
setup.cfg Tell the world we're Python 3 compatible (#4568) 2017-04-28 16:06:45 -07:00
setup.py tree-wide: use LooseVersion instead of StrictVersion (#8081) 2020-06-19 17:11:35 +02:00

README.rst 

Compatibility tests for Certbot