If anyone else finds themselves attending #PyConUS Pittsburgh Airport due to weather delays, I'll be hosting a last minute open space at Penn Brewery in the "A" arm of the terminal.
I think that there will be a post-#PyConUS survey going out at some point where you can register feedback for the conference organizers. I would humbly submit that as part of that feedback you should suggest that PyCon should invite @grimalkina to give a keynote next year; our community needs to hear what she has to say.
#PyConUS always reminds me that sleep is for the weak. It also reminds me that I am the weak.
Anyone know what dates #PyConUS 2026 is? I'm feeling sad I missed the 2025 sprints 😢
At my PT appointment in the waiting room and I hear "We are Family" playing from the adjacent exercise room, now with the new lyrics in my head 💜 🐍 #PyConUS
"Have you ever started a Python process, realized that you made a mistake, immediately hit Ctrl+C to interrupt it and then waited a surprisingly long time to get the command line back?
This delay is caused by a bug in the compiled #Python extension.
:thread:"
thread at https://bsky.app/profile/millionconcepts.com/post/3lpmgmqah3s2c about @zwol 's work, readable to non-users of Bluesky, includes #PyConUS #PyConUS2025 shout-out.
I think the best part of #PyConUS might have been helping @kjaymiller with some issues in `render-engine` during the sprints. If you come to PyCon US and have never done the sprints I highly recommend staying for at least 1 day of them.
Did someone leave a Dell power brick at the #pyopensci table in room 318 at the #PyConUS sprints? Can I get it back to you somehow?
I've been focusing on django-simple-deploy this week, but there have been ongoing interesting discussions about py-bugger as well.
It started as a simple tool to help teach and learn debugging. But someone else said their org has a codebase that ingests the output of other people's Python projects. They want to run py-bugger on their input .py projects, to feed into their tests. It's not mutation testing, it's about reliably generating specific errors as part of the test process.
I was hoping to keep a running thread about what we're accomplishing in the django-simple-deploy sprints. But we're at an interesting inflection point in the project where there aren't a bunch of PRs to merge, even though really significant things are happening.
Here's a brief thread about what has been happening.