Releases: JonasPammer/ansible-role-pip
regenerate galaxy readme.md
No real change.
1.0.4
- fix: rockylinux9 no longer has a virtualenv package to install by @JonasPammer in #49
Full Changelog: 1.0.3...1.0.4
cruft update
new version primarily because of JonasPammer/cookiecutter-ansible-role#41
Full Changelog: 1.0.3...1.0.3+1
1.0.3
What's Changed
- fix: use
python -m pip
instead of wrapper scriptpip
by @JonasPammer in #6
Full Changelog: 1.0.2...1.0.3
1.0.2 - ensure pip is actually installed in defined version using forcereinstall
... and add own logic to re-add proper idemponency even when using forcereinstall.
i still do not get how every pip recommends doing just pip install --upgrade pip
when it just fucking breaks itself on EOL python's, but hey
(especially when you know that a normal pip package has functionality to prevent this with python_requires
in its setup.cfg
)
NOTE / Summary:
Dynamic "<"-versions added in 1.0.1 may have fixed broken install behaviour as ranted above, but installation using just "<" ends up doing no install if it's already met, which is obviously always going to be the case with pip itself as pip is always present if you have pip ;)
I chose not do go with a combination of > and < but rather with a combination of < and forcereinstall because that ensures latest patch is installed
(e.g. otherwise if 20.1 is installed, the specifier is ">20,<21" and there is a 20.2, pip would do nothing. same goes for ">=")