> List Archives:
> https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
I like this plan overall. The only part I would adjust is the
guidelines h
probably premature, but is anyone opposed to me marking the package as
deprecated so that new packages can't (build)require it?
https://docs.fedoraproject.org/en-US/packaging-guidelines/deprecating-packages/
--
Carl George
___
python-devel mailing
erves this purpose.
On Thu, Jan 21, 2021 at 4:57 AM Andrew C Aitchison
wrote:
>
>
> On Thu, 21 Jan 2021, Carl George wrote:
>
> > RHEL7 ships Python 3.6 packages using the python3 prefix. Currently
> > EPEL7 contains Python 3.6 packages using both the python3 and pyt
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'll present this proposal and the
feedback to the EPEL Steering Committee.
--
Carl George
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code
Red Hat added python3 to RHEL 7.7, but at least for now has declined to turn on
the python3 subpackage in the libselinux spec file.
https://bugzilla.redhat.com/show_bug.cgi?id=1719978
I have attempted to to extract the python3 subpackage into it's own spec file.
It seems to work as best I can
Howdy! My name is Carl. I'm a Linux Engineer at Rackspace. Part of my job is
running the IUS project [0]. I also maintain numerous packages in Fedora and
EPEL, both for work and personal reasons.
I'd like to join the Python SIG. I'm primarily interested in EPEL
python34/python36 packages.
