/usr/bin/yum -d 0 -e 0 -y list python3

[sbelenky]

I'm trying to upgrade Python. Here is the manifest:

class { 'python' :
  version    => '3',
  pip        => false,
  #dev        => true,
  #virtualenv => true,
  #gunicorn   => true,
}

I've tried various things. I get this error:

/usr/bin/yum -d 0 -e 0 -y list python3

What can I do to fix it?

[petems]

@sbelenky Whats the Operating system and Operating system version?

[busayr]

Hi, I have a same problem. I'm trying to python 2.6.6 to 2.7.

OS: Oracle EL 6.6

class { 'python' : version => '2.7', }

[root@puppettest ~]# puppet agent --test Info: Retrieving pluginfacts Info: Retrieving plugin Info: Loading facts Error: Could not retrieve catalog from remote server: Error 400 on SERVER: validate_re(): "2.7" does not match ["system", "pypy", "3"] at /etc/puppet/modules/python/manifests/init.pp:84 on node puppettest.ej.local Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run

[fndiaz]

I have a same problem, to install python version 2.7

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: validate_re(): "2.7" does not match ["system", "pypy", "3"]

[cihann]

you need to add puppetlabs/stdlib to modules. maybe we can make a Vagrantfile and add stdlib module as dependency?

https://forge.puppet.com/puppetlabs/stdlib

[7yl4r]

If this is a missing dependency, then installing from the forge with puppet shouldn't see this because of the dependencies declared here.

If this problem is arising from installing from the repo directly, perhaps the appropriate fix is to make the dependency list more accessible by putting it in the readme? Adding a Vagrantfile seems like a fix that would only cover users deploying with vagrant, and I'm not sure that is what people are asking about here.