Re: [openstack-dev] [requirements][infra] Maintaining constraints for several python versions

2018-07-12 Thread Tony Breeds
On Thu, Jul 12, 2018 at 11:31:34AM -0500, Monty Taylor wrote: > there is also > > https://review.openstack.org/#/c/580730/ > > which adds a role to install docker and configure it to use the correct > registry. shiny! That'll take care of all the docker setup nice! Can I create a job that

Re: [openstack-dev] [requirements][infra] Maintaining constraints for several python versions

2018-07-12 Thread Tony Breeds
On Thu, Jul 12, 2018 at 11:05:09AM -0500, Matthew Thode wrote: > I'm of the opinion that we should decouple from distro supported python > versions and rely on what versions upstream python supports (longer > lifetimes than our releases iirc). Using docker/pyenv does this decoupling but I'm not c

Re: [openstack-dev] [requirements][infra] Maintaining constraints for several python versions

2018-07-12 Thread Tony Breeds
On Thu, Jul 12, 2018 at 11:31:34AM -0500, Monty Taylor wrote: > FWIW, I use pyenv for python versions on my laptop and love it. I've > completely given up on distro-provided python for my own usage. Hmm okay I'll look at that and how it'd play with the generate job. It's quite possible I'm being

Re: [openstack-dev] [requirements][infra] Maintaining constraints for several python versions

2018-07-12 Thread Tony Breeds
On Thu, Jul 12, 2018 at 01:52:56PM +, Jeremy Stanley wrote: > On 2018-07-12 06:37:52 -0700 (-0700), Clark Boylan wrote: > [...] > > I think most of the problems with Fedora stability are around > > bringing up a new Fedora every 6 months or so. They tend to change > > sufficiently within that t

Re: [openstack-dev] [requirements][infra] Maintaining constraints for several python versions

2018-07-12 Thread Tony Breeds
On Thu, Jul 12, 2018 at 06:37:52AM -0700, Clark Boylan wrote: > On Wed, Jul 11, 2018, at 9:34 PM, Tony Breeds wrote: > > 1. Build pythons from source and use that to construct the venv > >[please no] > > Fungi mentions that 3.3 and 3.4 don't build easily on modern linux distros. > However, 3.

Re: [openstack-dev] [requirements][infra] Maintaining constraints for several python versions

2018-07-12 Thread Monty Taylor
On 07/12/2018 11:05 AM, Matthew Thode wrote: On 18-07-12 13:52:56, Jeremy Stanley wrote: On 2018-07-12 06:37:52 -0700 (-0700), Clark Boylan wrote: [...] I think most of the problems with Fedora stability are around bringing up a new Fedora every 6 months or so. They tend to change sufficiently

Re: [openstack-dev] [requirements][infra] Maintaining constraints for several python versions

2018-07-12 Thread Monty Taylor
On 07/12/2018 08:37 AM, Clark Boylan wrote: On Wed, Jul 11, 2018, at 9:34 PM, Tony Breeds wrote: Hi Folks, We have a pit of a problem in openstack/requirements and I'd liek to chat about it. Currently when we generate constraints we create a venv for each (system) python supplied on the co

Re: [openstack-dev] [requirements][infra] Maintaining constraints for several python versions

2018-07-12 Thread Matthew Thode
On 18-07-12 13:52:56, Jeremy Stanley wrote: > On 2018-07-12 06:37:52 -0700 (-0700), Clark Boylan wrote: > [...] > > I think most of the problems with Fedora stability are around > > bringing up a new Fedora every 6 months or so. They tend to change > > sufficiently within that time period to make t

Re: [openstack-dev] [requirements][infra] Maintaining constraints for several python versions

2018-07-12 Thread Jeremy Stanley
On 2018-07-12 06:37:52 -0700 (-0700), Clark Boylan wrote: [...] > I think most of the problems with Fedora stability are around > bringing up a new Fedora every 6 months or so. They tend to change > sufficiently within that time period to make this a fairly > involved exercise. But once working the

Re: [openstack-dev] [requirements][infra] Maintaining constraints for several python versions

2018-07-12 Thread Clark Boylan
On Wed, Jul 11, 2018, at 9:34 PM, Tony Breeds wrote: > Hi Folks, > We have a pit of a problem in openstack/requirements and I'd liek to > chat about it. > > Currently when we generate constraints we create a venv for each > (system) python supplied on the command line, install all of > global-

[openstack-dev] [requirements][infra] Maintaining constraints for several python versions

2018-07-11 Thread Tony Breeds
Hi Folks, We have a pit of a problem in openstack/requirements and I'd liek to chat about it. Currently when we generate constraints we create a venv for each (system) python supplied on the command line, install all of global-requirements into that venv and capture the pip freeze. Where this