Paul Ganssle @pganssle@qoto.org

How did they even find the time to play this much hockey?

@simon You may also want to note that this changes the semantics of your `datetime` object, which is why we didn't just make `datetime.utcnow()` an alias for `datetime.now(UTC)`. If you change it you have to change it everywhere, and make sure all the datetimes you are consuming from other libraries are also aware.

(Also in the second example you have `import python` instead of `import datetime`).

@simon @anubhav The UTC object was added in 3.2 I believe.

@anubhav @simon Generally I recommend using `datetime.timezone.utc` for the UTC object, though there's usually also a UTC object in `zoneinfo`.

I adjusted the prompt that generates example sentences for my Spanish vocabulary Anki deck so that it intermittently tries to include interesting facts in the cards, and it has worked out marvelously.

Apparently sperm whales (cachalotes) are the loudest animals in the world.

#anki #spanish

@itamarst Reading "Guns of the South"?

Is there a good library out there in Python that provides a simple abstraction over the major LLM providers, such that it's easy for me to swap out which one I'm using for a given project?

I find myself writing my own version of this because each of the LLMs have strengths and weaknesses, and sometimes for a project I want to test them all out before committing to use a specific one.

A few months back I looked at @simon's `llm`, but from what I could tell it was mostly wrapping ChatGPT or compatible APIs, and I wasn't sure how to use it for everything.

If you are learning Spanish like me, just remember that *ser* is for permanent characteristics like your job title or the location of a party, whereas *estar* is for transitory conditions like death or the location of Barcelona.

I was explaining retirement to my son today and he said, "Oh, I might not ever have to work."
"Why not?"
"I am going to ask Santa for $2M this year. Then I'll be able to retire."
"Hmm.. I have never heard of Santa giving anyone enough money to retire on, to be honest. And $2M might not be enough..."

I noticed that he and my wife made the list today and he has now upped the request to $2B. Go big or go home, I guess. 😅

Man my package has been stuck at a UPS facility in Koeln, Germany for 10 days now, apparently this is a very common theme: https://www.reddit.com/r/UPS/comments/1f969dw/more_delay_experiences_cologne_koeln_germany/

And from older threads, it seems like it has been like this for years (I dunno if it is constant or intermittent).

I wonder if this is just a dysfunctional facility or if stuff gets stuck there because everything goes there before coming to the US and the problem is getting stuff from Europe to the US in general...

@hroncok My counterpoint here:

- The current Python REPL is pretty rough, and this is a *dramatic* improvement.
- A lot of the weird behavior and bugs don't show up until you get a lot of eyes on it, which means that the first release will always look like this.
- Given that it's an interactive terminal and not part of "hands-off" deployments, the kinds of bugs you are likely to encounter are less like, "Oh this created a bunch of work for me today because our whole pipeline broke" and more like, "Oh this new REPL isn't working for me, I should disable it until it works".

I am neutral about the lack of a PEP. It's definitely a major new feature, which weighs in favor of a PEP, but also I'm not sure how well it fits with the PEP process. It's not a major language feature, it's more an overhaul of an interactive application bundled with the language. I'm not sure what choices or trade-offs needed to be made that they would want people to weigh in about, or what decisions the SC would be making.

I also think the case could be made for saying that if you were to make the individual changes one at a time, none of them would require a PEP (with the possible exception of `exit() -> exit`).