Paul Ganssle @pganssle@qoto.org

Of course, there are legitimate reasons for this sort of dependency injection-style parameterization, but adding support for arbitrary interfaces broadens your "supported configuration surface" so much that usually it doesn't pass the YAGNI test — unless you need it for tests.

That's obviously a pithy twitter-sized take, but I think most of the time when you have some highly parameterized class / function, you aren't doing it because you actually want to support an interface where someone supplies their own provider of some core language functionality.

You do it because it makes your testing easier, and you can nominally it allows you to test using only the public interface.

That sort of thing is a necessity in languages without monkey patching, but it seems like it's a considerably worse code smell than patching in tests.

Listening to Anna-Lena Popkes on @TalkPython@twitter.com and I realized something I've never consciously understood: mocking is bad because it is tightly coupled to implementation details, but dependency injection solves this problem by promoting those details to be part of the public API.

In the book "Brooklyn", @builtbrooklyn@twitter.com says early aviator Calbraith Rodgers was "blogging all the way" on a cross-country flight.

I am kinda startled to find that I can't think of a non-anachronistic verb to describe what he was doing: sending regular dispatches for publication.

Citation: https://www.google.com/books/edition/Brooklyn/JHbTDwAAQBAJ?hl=en&gbpv=1&bsq=blogging

Another election year where I can find basically no information about any of the judges running for office.

You would think that they would have some sort of at least rudimentary campaign information, such that you could know like... their positions on issues and their track record as judges?

Talk is done!

The video is available here if you missed it (with an archive of the chat): https://youtu.be/S4TjOnkFLtI

Slides (with speaker notes) are here: https://pganssle-talks.github.io/pytexas-2020-upstream-bugs/#/

The slides are probably not especially mobile-friendly.

#python

The beginning of my @PyTexas@twitter.com talk: "Here are a bunch of hacky strategies that you should do everything to avoid using."

Every "real-life examples" section of the talk: "Here are a bunch of my projects that use these horrible hacks!" 😅 🤦‍♂️

My PyTexas talk, "What to Do When the Bug is in Someone Else's Code" will be streaming in 15 minutes!

I'll be in the Youtube chat answering questions and "not really a question, more of a comment"s!

Link to stream:

https://www.youtube.com/watch?v=S4TjOnkFLtI&list=PL0MRiRrXAvRgAFCdfHUcw8PNPqS7ux_BK&index=20

#python

One advantage of virtual conferences: if PyTexas had been in person, me running out of the room halfway through @moshezadka@twitter.com's talk screaming "That's a red-breasted nuthatch!" while scrambling for my camera would have been really inappropriate in person.

Fun fact: If you scatter peanuts around your yard and porch in an attempt to attract birds, it will also attract other animals.

Tonight we got a visit from a possum and a skunk at the same time!

As promised a few days ago, we now have a 2020.4 release of the first-party tzdata package on PyPI:

https://pypi.org/project/tzdata/

This includes changes to Palestine's DST rules that take effect THIS SATURDAY, so a good time to upgrade this (and your system package) is now!

#python

And for the "try before you buy" types among you, my slides are already available!

https://pganssle-talks.github.io/pytexas-2020-upstream-bugs/#/

The @PyTexas@twitter.com talk schedule is up!

If you're interested in my talk, "What to do When the Bug is in Someone Else's Code", it'll be airing from 14:00-14:30 CDT on Sunday, October 25:

https://www.pytexas.org/schedule/#:~:text=Speaker%3A%20Paul%20Ganssle

To be honest, I feel like I may have shot myself in the foot by trying to get the word out about this the last few years. It's so widely misunderstood that I may have been able to make the case for a backwards-incompatible change based on "we'd be fixing more code than we break".

This is starting to come up a lot more as people switch from pytz to zoneinfo, so a reminder about datetime arithmetic semantics; addition is NOT referring to elapsed time:
https://blog.ganssle.io/articles/2018/02/aware-datetime-arithmetic.html

(Relevant SO question: https://stackoverflow.com/q/64440016/467366 )

#python

This was all within ~10 minutes of one another.