"First thing to do is check robots.txt and see if this is allowed."
Probably not a subtle dig at the people DDoSing like 90% of the internet to scrape training data right now, but it should be
"Artichoke sky" new band name. #pyconus
That was an excellent talk by @pganssle with some good takeaways:
* You can use whatever tech stack you want
* Projects are a great way to learn
* You can use programming to answer questions for yourself
* Your projects don't have to pay
* It's OK to make something just for you
* It's also great to tell other people about your work
The slides include links and references to all of the projects:
https://pganssle-talks.github.io/2025-pycon-us-programming-for-yourself/
hey friends if you are at #PyConUS we semi desperately need volunteers so it would be super cool of you to step up https://us.pycon.org/2025/volunteer/volunteering/
Also, I apologize in advance, I had much more limited time than normal to prepare this talk this year and I haven't had a chance yet to go through and add good alt text to all the images. If that's something that is valuable to you, check back in ~1 week.
If you are at #PyConUS and you might be interested in my talk, "Programming for Yourself", it is today at 14:45 in Room 301-305
The slides are available on github here: https://pganssle-talks.github.io/2025-pycon-us-programming-for-yourself
@hugovk @adamchainz Does `pull_request` still fire on a draft PR? I guess the maintainer still gets notified about a draft PR, which maybe defeats the purpose, but it seems like a fairly small fraction of people are running CI on their own forks. I basically never do that, I just make a draft PR early.
I guess this at least partially explains why ever PR I've ever gotten from you has been flawless and basically ready to merge from the get-go, though.
Thanks for the help everyone who was looking for this. Just heard back from the Uber driver and apparently they found it!
If anyone at #PyConUS finds this fitness tracker, please let me know. It fell out of the band today around noon, possibly near the registration desk.
I'm facilitating another #PyConUS open space:
Still on Python 2?
Sun. May 18th
11am-noon
room TBD
An opportunity for software #maintainers who are still supporting #Python 2.x to talk with people who are still using Python 2.x. What do users need before we can migrate? What do maintainers need to know or get before we can fully deprecate 2.x support? What funding might be necessary to make these happen? A supportive and nonjudgmental discussion.
Update: go get it! https://discuss.python.org/t/python-3-14-0-beta-1-is-here/91117
Another kind of bug revealed by including tests in your coverage:
with pytest.raises(ValueError):
process_data("bad data 1")
process_data("bad data 2") # never executed!
https://nedbatchelder.com/blog/202008/you_should_include_your_tests_in_coverage.html
@hynek Lol, I think I may have had my first anxiety dream about this last night!
Though to be fair, I also have booked absolutely nothing with regards to PyCon, so, uh, that's a fair get, subconscious.
Anyone out there using #AR / #VR headsets for productivity on #Linux? I would love to be able to ditch my portable second monitor in favor of some glasses with virtual monitors in them, even if the experience isn't suitable for replacing my main daily driver.
Also very interested to hear about portable new input methods that could potentially replace a keyboard.
Programmer working at Google. Python core developer and general FOSS contributor. I also post some parenting content.