manage_pip_packages

History

Bertrand Lanson 35da3a0870 All checks were successful test / Linting (push) Successful in 31s Details test / Molecule tests (default, ubuntu2004) (push) Successful in 1m13s Details test / Molecule tests (default, debian12) (push) Successful in 1m37s Details test / Molecule tests (default, debian11) (push) Successful in 1m40s Details test / Molecule tests (default, ubuntu2204) (push) Successful in 1m9s Details test / Molecule tests (with_custom_packages, debian12) (push) Successful in 1m18s Details test / Molecule tests (with_custom_packages, debian11) (push) Successful in 1m21s Details test / Molecule tests (with_custom_packages, ubuntu2004) (push) Successful in 59s Details test / Molecule tests (with_custom_packages, ubuntu2204) (push) Successful in 1m13s Details feat(task): do not try to update pip if manage_pip_packages_allow_break_system_packages is true It might fail on newer distribution (ubuntu 24+, debian 12+), because of the stupid PEP668		2024-09-01 14:19:47 +00:00
..
main.yml	added option to bypass pep668 error	2023-08-27 18:13:08 +02:00
prerequisites.yml	feat(task): do not try to update pip if manage_pip_packages_allow_break_system_packages is true	2024-09-01 14:19:47 +00:00