Re: python-flit for EPEL9?
On 23. 12. 21 23:31, Michel Alexandre Salim wrote: On Thu, Dec 23, 2021 at 04:51:36PM -0500, Neal Gompa wrote: Top posting because replying from my phone, but I think it'd be great to have in EPEL 9 because it's essential for some packages to build. The same goes for Poetry, which is now used for software made by Fedora Infrastructure these days. Do we (as in Fedora) have any preference which way, between setuptools, poetry, and flit? Not really. Asking because I'm writing a new tool and I wonder which build system to use. If there is a chance you'll ever target EPEL 8 or lesser, stick with setuptools and keep at least a small setup.py shim. I've seen Fedora infra packaging noggin with poetry and then struggling to package it for EPEL 8: https://bugzilla.redhat.com/1898395 -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: python-flit for EPEL9?
On Thu, Dec 23, 2021 at 04:51:36PM -0500, Neal Gompa wrote: > Top posting because replying from my phone, but I think it'd be great to > have in EPEL 9 because it's essential for some packages to build. The same > goes for Poetry, which is now used for software made by Fedora > Infrastructure these days. > Do we (as in Fedora) have any preference which way, between setuptools, poetry, and flit? Asking because I'm writing a new tool and I wonder which build system to use. Thanks, -- Michel Alexandre Salim profile: https://keyoxide.org/mic...@michel-slm.name signature.asc Description: PGP signature ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: python-flit for EPEL9?
On Thu, Dec 23, 2021 at 11:18:47PM +0100, Miro Hrončok wrote: > On 23. 12. 21 21:10, Michel Alexandre Salim wrote: > > I'm starting to try and grok pyproject.toml and its assorted PEPs in > > more details, and it looks like flit is one of the more straightforward > > way to build compliant wheels out there. > > So is setuptools BTW. > True. > > Should we get it into EPEL9? I filed a tracking bug: > > https://bugzilla.redhat.com/show_bug.cgi?id=2035376 > > Sure. > > > It currently does not build because of some missing dependencies - I > > listed them in the bug above - if we do want this in EPEL9 I'll file > > those bug requests and make them block this. > > I've noted some info about a bootstrap loop in a comment, reposting here for > clarity: > > Note that tomli/flit needs to be bootstrapped. If you want to void extra > commits, you can build flit 3.3.0 first, then tomli, then update flit. > Thanks for the tip! > > Also, to note, the EPEL maintainer is currently set to orphan. While I'm > > in python-sig so I can branch and build just fine as is, Miro, as the > > owner could you add me to the ACL and/or set me as the EPEL assignee? > > Done both. It was set to orphan because when I took the package I had no > intention to maintain the ancient version in EPEL 7 and 8. > Yeah, that makes sense. > > We could probably add epel-packagers-sig as collaborator on epel* > > branches too. > > Done. > And thanks Best regards, -- Michel Alexandre Salim profile: https://keyoxide.org/mic...@michel-slm.name signature.asc Description: PGP signature ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: python-flit for EPEL9?
On 23. 12. 21 21:10, Michel Alexandre Salim wrote: I'm starting to try and grok pyproject.toml and its assorted PEPs in more details, and it looks like flit is one of the more straightforward way to build compliant wheels out there. So is setuptools BTW. Should we get it into EPEL9? I filed a tracking bug: https://bugzilla.redhat.com/show_bug.cgi?id=2035376 Sure. It currently does not build because of some missing dependencies - I listed them in the bug above - if we do want this in EPEL9 I'll file those bug requests and make them block this. I've noted some info about a bootstrap loop in a comment, reposting here for clarity: Note that tomli/flit needs to be bootstrapped. If you want to void extra commits, you can build flit 3.3.0 first, then tomli, then update flit. Also, to note, the EPEL maintainer is currently set to orphan. While I'm in python-sig so I can branch and build just fine as is, Miro, as the owner could you add me to the ACL and/or set me as the EPEL assignee? Done both. It was set to orphan because when I took the package I had no intention to maintain the ancient version in EPEL 7 and 8. We could probably add epel-packagers-sig as collaborator on epel* branches too. Done. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: python-flit for EPEL9?
Top posting because replying from my phone, but I think it'd be great to have in EPEL 9 because it's essential for some packages to build. The same goes for Poetry, which is now used for software made by Fedora Infrastructure these days. On Thu, Dec 23, 2021, 3:10 PM Michel Alexandre Salim < sali...@fedoraproject.org> wrote: > I'm starting to try and grok pyproject.toml and its assorted PEPs in > more details, and it looks like flit is one of the more straightforward > way to build compliant wheels out there. > > Should we get it into EPEL9? I filed a tracking bug: > https://bugzilla.redhat.com/show_bug.cgi?id=2035376 > > looks like it's retired in CS9 so it should be fine for us to have. > > https://gitlab.com/redhat/centos-stream/rpms/python-flit/-/blob/main/dead.package > > It currently does not build because of some missing dependencies - I > listed them in the bug above - if we do want this in EPEL9 I'll file > those bug requests and make them block this. > > Also, to note, the EPEL maintainer is currently set to orphan. While I'm > in python-sig so I can branch and build just fine as is, Miro, as the > owner could you add me to the ACL and/or set me as the EPEL assignee? > > We could probably add epel-packagers-sig as collaborator on epel* > branches too. > > Best regards, > > -- > Michel Alexandre Salim > profile: https://keyoxide.org/mic...@michel-slm.name > ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Are the new guidelines mandatory for new packages?
On 23. 12. 21 21:34, Robert-André Mauchin wrote: On 12/23/21 18:41, Miro Hrončok wrote: On 23. 12. 21 18:25, Robert-André Mauchin wrote: Hello, Are the new Python guidelines mandatory or optional? Optional. From https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/ """Older guidelines are still being kept up to date, and existing packages MAY use them instead of this document.""" I meant for brand new packages, when i review them, shall i ask people to follow the new ones strictly? You might ask them nicely to consider it, but you should not demand that. They are optional for brand new packages as well. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
python-flit for EPEL9?
I'm starting to try and grok pyproject.toml and its assorted PEPs in more details, and it looks like flit is one of the more straightforward way to build compliant wheels out there. Should we get it into EPEL9? I filed a tracking bug: https://bugzilla.redhat.com/show_bug.cgi?id=2035376 looks like it's retired in CS9 so it should be fine for us to have. https://gitlab.com/redhat/centos-stream/rpms/python-flit/-/blob/main/dead.package It currently does not build because of some missing dependencies - I listed them in the bug above - if we do want this in EPEL9 I'll file those bug requests and make them block this. Also, to note, the EPEL maintainer is currently set to orphan. While I'm in python-sig so I can branch and build just fine as is, Miro, as the owner could you add me to the ACL and/or set me as the EPEL assignee? We could probably add epel-packagers-sig as collaborator on epel* branches too. Best regards, -- Michel Alexandre Salim profile: https://keyoxide.org/mic...@michel-slm.name signature.asc Description: PGP signature ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Are the new guidelines mandatory for new packages?
On 23. 12. 21 18:25, Robert-André Mauchin wrote: Hello, Are the new Python guidelines mandatory or optional? Optional. From https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/ """Older guidelines are still being kept up to date, and existing packages MAY use them instead of this document.""" -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Are the new guidelines mandatory for new packages?
Hello, Are the new Python guidelines mandatory or optional? I mean the whole: %build %pyproject_wheel %install %pyproject_install %pyproject_save_files Or can packagers still use py3_build and py3_install? Best regards, Robert-André ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
