Re: [PATCH] gitlab: force allow use of pip in Cirrus jobs

2024-02-23 Thread Peter Maydell
On Thu, 22 Feb 2024 at 11:41, Daniel P. Berrangé wrote: > > Python is transitioning to a world where you're not allowed to use 'pip > install' outside of a virutal env by default. The rationale is to stop > use of pip clashing with distro provided python packages, which creates > a major headache

Re: [PATCH] gitlab: force allow use of pip in Cirrus jobs

2024-02-22 Thread Thomas Huth
On 22/02/2024 12.40, Daniel P. Berrangé wrote: Python is transitioning to a world where you're not allowed to use 'pip install' outside of a virutal env by default. The rationale is to stop use of pip clashing with distro provided python packages, which creates a major headache on distro upgrades

Re: [PATCH] gitlab: force allow use of pip in Cirrus jobs

2024-02-22 Thread Philippe Mathieu-Daudé
On 22/2/24 12:40, Daniel P. Berrangé wrote: Python is transitioning to a world where you're not allowed to use 'pip install' outside of a virutal env by default. The rationale is to stop use of pip clashing with distro provided python packages, which creates a major headache on distro upgrades.

[PATCH] gitlab: force allow use of pip in Cirrus jobs

2024-02-22 Thread Daniel P . Berrangé
Python is transitioning to a world where you're not allowed to use 'pip install' outside of a virutal env by default. The rationale is to stop use of pip clashing with distro provided python packages, which creates a major headache on distro upgrades. All our CI environments, however, are 100% dis