System python on CentOS 8 is not "python"
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- devops, operating-systems
Research direction
Start with the module's package-installation logic and reproduce the issue using the Puppet class shown on CentOS 8. Check how the system Python choice is translated into package names and verify the result with the reported pip and virtualenv settings. Done means system Python installs successfully on CentOS 8 and the existing system-based virtualenv workflow no longer requires version-specific overrides.
Written by the indexing model from the issue text.
Description
Affected Puppet, Ruby, OS and module versions/distributions
- Puppet: 6.11.1
- Ruby: 2.5.7p206
- Distribution: CentOS 8
- Module version: 4.0.0
How to reproduce (e.g Puppet code you use)
class { 'python':
ensure => 'present',
pip => 'present',
virtualenv => 'present',
use_epel => false,
}
What are you seeing
Error: Execution of '/bin/dnf -d 0 -e 1 -y install python' returned 1: Error: Unable to find a match
Error: /Stage[main]/Python::Install/Package[python]/ensure: change from 'purged' to 'present' failed: Execution of '/bin/dnf -d 0 -e 1 -y install python' retu
rned 1: Error: Unable to find a match
What behaviour did you expect instead
Python 2.7 is now EOL and so CentOS 8 are pushing a lot of Python 3. Because of the long lifespan of a CentOS release, they've only got versioned Python (python2 and python3) and python as a package doesn't exist.
"system" should be Python 3 on CentOS 8 (and other distros that have similar behaviour)
This would also solve the problem of installing Python as v3 (rather than system) and then having to specify v3 for all virtualenvs as well.
- Dominant language
- Ruby
- Stars
- 196
- Forks
- 372
- Avg merge
- 1d 18m
- Merged PRs (30d)
- 4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from voxpupuli/puppet-python
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
voxpupuli/puppet-python#743 · 1 comment ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 35/100
voxpupuli/puppet-python#721 · 1 reaction ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
voxpupuli/puppet-python#712 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
voxpupuli/puppet-python#711 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 52/100
voxpupuli/puppet-python#673 · 1 comment ·
All issues in voxpupuli/puppet-python
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
バグ
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
voxpupuli/puppet-epel#186 · 1 comment ·
-
external_created_at is no longer used for the message timestamp since the new message UI (v4.4.0) OpenBug Frontend
Difficulty 2/5 1-3 hours Newbie friendliness 78/100