#346 [Hack-half]: Modern Python packaging hackfest
Closed: Talk Scheduled by riecatnor. Opened by pviktori.

== What is your proposal?

The Python maintenance team is prepared to help you update existing Python RPM packages or package new ones.

With the new Python packaging guidelines and macros, we aim to automate Python packaging more, and help packagers stay closer to upstreams. But you need to make some changes to start benefitting.
Just bring your spec file or idea and feel free to hack with us. We'll be there for you for half a day, you can join or leave at your convenience.

We're also happy to discuss the guidelines or macros, and answer any questions.

== Technical

This is a Hackfest that lasts a half-day.
The session can only be live, but we'd like to pre-record a short (5-10min) introduction, which attendees could watch whenever they join.

== What do you want to accomplish?

We want packagers to get more comfortable with the new tools and use them more widely.

== Who'll be there?

  • Packagers of Python packages
  • As hosts, the Python Maintenance team from Red Hat:
    • Petr Viktorin (pviktori)
    • Miro Hrončok (churchyard)
    • Tomáš Orsava (torsava)
    • Tomáš Hrnčiar (thrnciar)
    • and possibly others

== Who are you?

Name: Petr Viktorin
FAS ID: pviktori
IRC Nick: encukou
Timezone: Europe
Availability for August 5-8th: ONLY Thursday/Friday (5-6th); 9:00-16:00 UTC


I like this idea. Is there a way for maintainers to know if their packages could benefit from this? Or is it assumed that if you maintain a Python package and you don't know that you're using the latest tools, you probably need it

if you maintain a Python package and you don't know that you're using the latest tools, you probably need it.

Pretty much the gist of it.

More complex answer:

If your package uses any of the deprecated macros listed in https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/#_deprecated_macros than you can update to the new macros. If you attend the hackfest, you have a good chance of leaving with a working updated spec file.

If your package does not use such macros, but instead uses cmake/autotools/etc. to build the Python bits, you might not yet be able to update to the new macros, but we welcome you anyway on the hackfest, so we can collect your packages for later analysis and brainstorm some ideas with you. If you attend the hackfest, you have a good chance to influence the future so it benefits your package, but you are not that likely to leave with a working updated spec file.

Hi @pviktori - Thank you for your submission!

Your session has been accepted for Nest with Fedora. Please review the following Wiki link and advise ASAP if there are any conflicts. The schedule will be locked by Friday July 30th. https://fedoraproject.org/wiki/Nest_with_Fedora_2021_Schedule

Please register for Nest with Fedora on Hopin at the following link. I will need to add you all as speakers for the session in the Hopin admin dashboard.
https://hopin.com/events/nest-with-fedora-2021

If you have further questions or need assistance, feel free to email mnordin@redhat.com or drop those inquiries on this ticket. Thanks!

Hey @riecatnor. Awesome news. Looking at the proposed schedule, the Hackfest lasts 2 hours. Is it possible to make it longer? Our assumption for "half a day" was more like 4 hours than 2.

I see the event starts at 12:00 UTC on Friday. Can we start at that hour? I understand that people might want to see the keynote or attend the social thing, but since this is "show up or leave at any time" kind of hackfest, I believe it is not that important not to conflict with other sessions. WDYT?

@churchyard works for me! I have updated the schedule accordingly

Thank you!

@churchyard, @torsava, @thrnciar: could you all register on hopin, so you can get added as speakers?
https://hopin.com/events/nest-with-fedora-2021

Already done on my part.

Metadata Update from @riecatnor:
- Issue close_status updated to: Talk Scheduled
- Issue status updated to: Closed (was: Open)

Metadata