401: We must replace uWSGI with something else - Python Bytes

▬ Topics covered ▬▬▬▬▬▬▬▬▬▬▬▬

- Michael #1: “We must replace uwsgi by something else”
- Brian #2: Let’s build and optimize a Rust extension for Python
- Michael #3: Fake recruiter coding tests target devs with malicious Python packages
- Brian #4: Monthly PSF Board Office Hours

▬ Extras ▬▬▬▬▬▬▬▬▬▬▬▬

Brian:
- PyCascades CFP closes Friday, Sept 20
- uv now supports Python 3.13.0rc2

Michael:
- ** Big Python Humble Bundle with both of our products**
- Djangonaut Space Session 3 Applications Open!
- AltTab: Windows alt-tab on macOS

▬ Connect with the hosts on Mastodon ▬▬▬▬▬▬▬▬▬▬▬▬

▬ Support the Show ▬▬▬▬▬▬▬▬▬▬▬▬

[BartWillems]

Just because the logo is a green unicorn doesn’t necessitate that it is the origin of the name. Python, with its snake logo, is a very good example of that. But you still make a strong case.

[kivabirb]

I've noticed the uwsgi thing a year ago (it took its sweet time to support python 3.12). Made me start working harder on the asyncio migration.

[JohnDoe-ktiq]

We were using gunicorn with nginx in production. Just this week we replaced both of them with nginx unit.

For our application, we got significant improvements in CPU and memory usage.