Building EOL Python versions, and locating/building dependencies for non-EOL versions, in a convenient way
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 45.1k
- Forks
- 3.3k
- Avg merge
- 19h 54m
- Merged PRs (30d)
- 21
Description
I have successfully used pyenv to install python 3.7 on this system, where it is running great. I tried to install python 3.4.7 and I got these errors
Installing Python-3.4.7...
Traceback (most recent call last):
File "", line 1, in
File "/home/safulop/.pyenv/versions/3.4.7/lib/python3.4/curses/init.py", line 13, in
from _curses import *
ImportError: No module named '_curses'
WARNING: The Python curses extension was not compiled. Missing the ncurses lib?
Traceback (most recent call last):
File "", line 1, in
File "/home/safulop/.pyenv/versions/3.4.7/lib/python3.4/ssl.py", line 97, in
import _ssl # if we can't import it, let the error propagate
ImportError: No module named '_ssl'
ERROR: The Python ssl extension was not compiled. Missing the OpenSSL lib?
Clearly the ncurses devel package is actually installed so, I am at a loss to figure this out.
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.
Research direction
Start by reproducing the pyenv install of Python 3.4.7 and inspect the build output around the missing curses and ssl extensions. No source file or test is identified in the issue; done means EOL and non-EOL Python builds can locate or build their required dependencies conveniently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, shell
- Domain
- build-system, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100