installation of 3.10 and 3.11 failed on LINUX in the script "compileall.py"
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
I often installed python but now (for some unknown reason) it failed on LINUX. The problem is the lib/python3.11/compileall.py with 6 sub-fork never end. I stop after 1h30 execution time, I try 3.10 and 3.11.
comment out the block
# -PYTHONPATH=$(DESTDIR)$(LIBDEST) $(RUNSHARED) \
# $(PYTHON_FOR_BUILD) -Wi $(DESTDIR)$(LIBDEST)/compileall.py \
# -j0 -d $(LIBDEST) -f \
# -x 'bad_coding|badsyntax|site-packages|lib2to3/tests/data' \
# $(DESTDIR)$(LIBDEST)
# -PYTHONPATH=$(DESTDIR)$(LIBDEST) $(RUNSHARED) \
# $(PYTHON_FOR_BUILD) -Wi -O $(DESTDIR)$(LIBDEST)/compileall.py \
# -j0 -d $(LIBDEST) -f \
# -x 'bad_coding|badsyntax|site-packages|lib2to3/tests/data' \
# $(DESTDIR)$(LIBDEST)
# -PYTHONPATH=$(DESTDIR)$(LIBDEST) $(RUNSHARED) \
# $(PYTHON_FOR_BUILD) -Wi -OO $(DESTDIR)$(LIBDEST)/compileall.py \
# -j0 -d $(LIBDEST) -f \
# -x 'bad_coding|badsyntax|site-packages|lib2to3/tests/data' \
# $(DESTDIR)$(LIBDEST)
# -PYTHONPATH=$(DESTDIR)$(LIBDEST) $(RUNSHARED) \
# $(PYTHON_FOR_BUILD) -Wi $(DESTDIR)$(LIBDEST)/compileall.py \
# -j0 -d $(LIBDEST)/site-packages -f \
# -x badsyntax $(DESTDIR)$(LIBDEST)/site-packages
# -PYTHONPATH=$(DESTDIR)$(LIBDEST) $(RUNSHARED) \
# $(PYTHON_FOR_BUILD) -Wi -O $(DESTDIR)$(LIBDEST)/compileall.py \
# -j0 -d $(LIBDEST)/site-packages -f \
# -x badsyntax $(DESTDIR)$(LIBDEST)/site-packages
# -PYTHONPATH=$(DESTDIR)$(LIBDEST) $(RUNSHARED) \
# $(PYTHON_FOR_BUILD) -Wi -OO $(DESTDIR)$(LIBDEST)/compileall.py \
# -j0 -d $(LIBDEST)/site-packages -f \
# -x badsyntax $(DESTDIR)$(LIBDEST)/site-packages
helps to install, but the python seems to be broken with startup error on missing parts like.
exec: [1] ;.../bin/python3.11
Could not find platform dependent libraries <exec_prefix>
Python 3.11.1 (main, Jan 25 2023, 23:48:02) [GCC 11.3.1 20221024 [revision bd0c76a2329e7fe6d6612c2259647bbb67f5866a]] on linux
Type "help", "copyright", "credits" or "license" for more information.
Traceback (most recent call last):
File "/etc/pythonstart", line 7, in <module>
import readline
ModuleNotFoundError: No module named 'readline'
>>>
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 with lib/python3.11/compileall.py and the build-script block that invokes it with -j0 during Linux installation. Reproduce the reported 3.10 or 3.11 build and investigate why the six subprocesses do not finish. Done means the installation completes without commenting out the block and the resulting interpreter can import readline without the reported missing-library startup error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100