On 2019-09-30 16:30:53 +1000 (+1000), Ian Wienand wrote:
> On Fri, Sep 27, 2019 at 11:09:22AM +, Jeremy Stanley wrote:
> > I'd eventually love to see us stop preinstalling pip and virtualenv
> > entirely, allowing jobs to take care of doing that at runtime if
> > they need to use them.
>
>
On Fri, Sep 27, 2019 at 11:09:22AM +, Jeremy Stanley wrote:
> I'd eventually love to see us stop preinstalling pip and virtualenv
> entirely, allowing jobs to take care of doing that at runtime if
> they need to use them.
You'd think, right? :) But it is a bit of a can of worms ...
So pip
On Fri, Sep 27, 2019 at 7:11 AM Jeremy Stanley wrote:
>
> On 2019-09-27 17:26:15 +1000 (+1000), Ian Wienand wrote:
> [...]
> > Installing pip and virtualenv from upstream sources has a long history
> > full of bugs and workarounds nobody wants to think about (if you do
> > want to think about it,
On 2019-09-27 17:26:15 +1000 (+1000), Ian Wienand wrote:
[...]
> Installing pip and virtualenv from upstream sources has a long history
> full of bugs and workarounds nobody wants to think about (if you do
> want to think about it, you can start at [2]).
[...]
> I'm thinking that CentOS 8 is a
Hello,
All our current images use dib's "pip-and-virtualenv" element to
ensure the latest pip/setuptools/virtualenv are installed, and
/usr/bin/ installs Python 2 packages and
/usr/bin/ install Python 3 packages.
The upshot of this is that all our base images have Python 2 and 3
installed (even
