On 29. 04. 20 16:27, Tomas Orsava wrote:
Hello everyone.
I’m working on a change to rename pythonXY packages to pythonX.Y, e.g. python39
to python3.9.
*Motivation:*
When you install an additional Python interpreter, the command that runs it
contains a dot (e.g. /usr/bin/python3.9) but the
On 07. 05. 20 23:35, Felix Schwarz wrote:
What is the Fedora policy regarding Python 2 packages in F33?
If there was a Fesco exception for some package last year can we assume that
we can/should keep the package also in F33? I did not find anything about the
assumed scope of these Fesco
What is the Fedora policy regarding Python 2 packages in F33?
If there was a Fesco exception for some package last year can we assume that
we can/should keep the package also in F33? I did not find anything about the
assumed scope of these Fesco exceptions.
Specifically this is about bug
On 2020-05-06 11:24, Lumir Balhar wrote:
I've took a look and the new guidelines look good to me.
The only thing I am afraid of is that there is a lot of magic behind new
macros. Previously, macros were a way how to use standard Python
commands like "python3 setup.py build" without memorizing
On 2020-05-06 13:44, Miro Hrončok wrote:
In this change:
https://fedoraproject.org/wiki/Changes/Make_ambiguous_python_shebangs_error
We have advised the following:
pathfix.py -pni "%{__python3} %{py3_shbang_opts}"
To fix the shebangs.
-p preserves timestamps
-n prevents creating
