Wow, impressive list of enhancements, that's really great! I didn't
realized that so many things were done only in 2020!
Fedora is and remains my favorite OS to develop on Python!
Victor
On Thu, Jan 21, 2021 at 4:38 PM Miro Hrončok wrote:
>
> Inspired by a similar report from the Copr team, I’v
I'm not sure I understand your question. This proposal is about
python36 packages, not the existing python34 packages or hypothetical
python38 packages. In any case, packages shouldn't be requiring
python* directly. They automatically get a requirement on
`python(abi) = X.Y` that serves this pur
Agreed. And if a maintainer decides to stick with the python36 name,
they MUST provide the equivalent python3 name. I've captured those
for what I'll add to the guidelines.
On Thu, Jan 21, 2021 at 4:30 AM Miro Hrončok wrote:
>
> On 21. 01. 21 7:19, Carl George wrote:
> > I propose that we stand
Inspired by a similar report from the Copr team, I’ve decided to look back at
2020 from the perspective of Python in Fedora (and little bit in
RHEL/CentOS+EPEL as well). Here are the things we have done in Fedora (and EL)
in 2020.
https://communityblog.fedoraproject.org/fedora-loves-python-202
On 21. 01. 21 7:19, Carl George wrote:
I propose that we standardize
on the python3 prefix to match RHEL7 packages and document in EPEL
guidelines that maintainers SHOULD use the python3 prefix.
I'm fine with that, is we also say they MUST use %python_provide (or that the
packages MUST provide
