#359 gil--;

Topics covered in this episode:

• PyCon 2024 is up?
• Ruff formatter is production ready
• gil--;
• Why is the Django Admin “Ugly”?
• Extras
• Joke

Watch on YouTube

About the show

Sponsored by Scout APM

Connect with the hosts

• Michael: @mkennedy@fosstodon.org
• Brian: @brianokken@fosstodon.org
• Show: @pythonbytes@fosstodon.org

Join us on YouTube at pythonbytes.fm/live to be part of the audience. Usually Tuesdays at 11am PT. Older video versions available there too.

Michael #1: PyCon 2024 is up?

• May 15 - May 23, 2024 - Pittsburgh, Pennsylvania
• Conference breakdown:
  • Tutorials: May 15 - 16, 2024
  • Main Conference and Online: May 17 - 19, 2024
  • Job Fair: May 19, 2024
  • Sprints: May 20 - May 23, 2024
• Tickets aren’t on sale yet
• Unfortunately, I’m not going (see health and safety guidelines)
• Attendance numbers over time on Wikipedia

Brian #2: Ruff formatter is production ready

• We reported the alpha release in September
• It’s fast, 30x faster than Black
• Provides >99.9% compatibility with Black, with a list of known deviations
• More configurable
• Bundled with ruff, ruff format
• Still in Beta, but considered production-ready
• Integration extensions for VSCode and PyCharm

Michael #3: gil--;

• The Python Steering Council has now formally accepted PEP 703 ("Making the Global Interpreter Lock Optional in CPython")
• The global interpreter lock will remain the default for CPython builds and python.org downloads.
• A new build configuration flag, --disable-gil will be added to the configure script that will build CPython with support for running without the global interpreter lock.
• "In short, the SC accepts PEP 703, but with clear provisio:
  • that the rollout be gradual and break as little as possible,
  • that we can roll back any changes that turn out to be too disruptive – which includes potentially rolling back all of PEP 703 entirely if necessary (however unlikely or undesirable we expect that to be)."
• Removing the global interpreter lock requires substantial changes to CPython internals, but relatively few changes to the public Python and C APIs.
• The implementation changes can be grouped into the following four categories:
  • Reference counting
  • Memory management
  • Container thread-safety
  • Locking and atomic APIs

Brian #4: Why is the Django Admin “Ugly”?

• Vince Salvino
• Some great quotes from the article:
  • "The Django admin is not ugly, rather, no effort was made to make it a beautiful end-user tool.” - Ken Whitesell
  • “The admin’s recommended use is limited to an organization’s internal management tool. It’s not intended for building your entire front end around.” - Django docs
  • “The Django admin was built for Phil.” - Jacob Kaplan-Moss
  • “Even in the 0.9x days we used to have a image that said “Admin: it’s not your app”.” - Curtis Maloney
• As Curtis put it, “encouraging people to build their own management interface, and treat admin as a DB admin tool, has saved a lot of people pain... the effort to customise it grows far faster than the payoffs.”

Extras

Brian:

• Local Conferences: Big Potential

Michael:

• Data Science Jumpstart with 10 Projects course is out!
• PSF is X-ed out (or are they?)
• GPT4All is pretty excellent
• Fosstodon invites from us (expires Nov 7 2023)

Joke: Searching YouTube for bug fixes