Description of problem: Looking at https://docs.python.org/3/whatsnew/3.4.html I see that inseparable part of python34 (PEP 453). /usr/bin/python3 command should be available (PEP 394) We should really have COMPLETE python3 distribution packaged not some of its selected parts. setuptools is suggested to be available. Could we get it as well, please? Version-Release number of selected component (if applicable): python34-3.4.3-2.el7.x86_64
Thank you for the report, you are correct, /usr/bin/python3 should be available in this case. It's not there because the following part of spec identifies the build as non-main-python, which does not provide /usr/bin/python3 (see 'Python3 in EPEL' docs for more information on what main python means). %if "%python3_pkgversion" == "%pyshortver" %global main_python3 1 %else %global main_python3 0 %endif It does so because %python3_pkgversion is not yet available in the minimal buildroot, for which I first need to modify packaging guidelines and pass them through FPC. It's been on my To Do list for a long while, unfortunately I just didn't have time to do it, yet. > setuptools is suggested to be available. Could we get it as well, please? setuptools and pip will definitely be available, when all is done.
(In reply to Matej Stuchlik from comment #1) > /usr/bin/python3 (see 'Python3 in EPEL' docs for more information on what > main python means). There is that awesome thing called URL ... you may put it here so we all know what document you are talking about. Is it https://fedoraproject.org/wiki/User:Bkabrda/EPEL7_Python3 ? BTW, in that document I am still confused about this item: # Usage of "/usr/bin/python3" is discouraged in favour of using /usr/bin/python3.X explicitly. ??? Is there some explanation of this strange idea? (most of the world uses "/usr/bin/env python3", I would say). > It does so because %python3_pkgversion is not yet available in the minimal > buildroot, for which I first need to modify packaging guidelines and pass > them through FPC. It's been on my To Do list for a long while, unfortunately > I just didn't have time to do it, yet. Does it mean, that we are just missing a package python3-main or something which would hold this symlink and depend on python34? > > setuptools is suggested to be available. Could we get it as well, please? > > setuptools and pip will definitely be available, when all is done. Thanks.
Just to record here that I believe the minimal python should have at least: python-devel python-docutils python-jinja2 python-markupsafe (probably useful for the web developers) python-nose (too many people use it) python-pygments ??? python-setuptools python-sphinx python-sqlalchemy python-virtualenv
Seems like nothing is going on here, so I have just set manually main_python3 variable to 1 and rebuild locally. However, the test suite fails with test_precision_c_limits (test.test_format.FormatTest) ... test test_format failed Any idea, what's going on?
(In reply to Matěj Cepl from comment #4) > Seems like nothing is going on here, so I have just set manually > main_python3 variable to 1 and rebuild locally. However, the test suite > fails with > > > test_precision_c_limits (test.test_format.FormatTest) ... test test_format > failed weird, the whole thing builds correctly in Koji http://koji.fedoraproject.org/koji/taskinfo?taskID=11638633
Looking through some of the python34 bug reports here and I'm wondering what is left in this report? As of python34-3.4.5-3.el7.x86_64 there is a /usr/bin/python3 as required in the initial report so maybe we can just close this issue?
(In reply to Felix Schwarz from comment #7) > Looking through some of the python34 bug reports here and I'm wondering what > is left in this report? As of python34-3.4.5-3.el7.x86_64 there is a > /usr/bin/python3 as required in the initial report so maybe we can just > close this issue? I agree, closing it.