Paul Ganssle @pganssle@qoto.org

One day I hope ML technology advances to the point that I can describe a shirt and find out if someone is selling something like it.

It's relatively easy to make a drop-in replacement for these, but also we're deprecating them because they're conceptually the wrong thing to do, so it's best to migrate to using aware datetimes if possible: https://blog.ganssle.io/articles/2019/11/utcnow.html

`datetime.utcnow` and `datetime.utcfromtimestamp` will be deprecated in #python 3.12: https://github.com/python/cpython/issues/103857

If you maintain a package, now is probably a good time to grep your source code for `utcnow` and `utcfromtimestamp` to get out ahead of the deprecation warnings. 📅🕐

`$ sudo dd if=/dev/zero of=/dev/mapper/to_be_wiped status=progress`
`59001459200 bytes (59 GB, 55 GiB) copied, 904 s, 65.3 MB/s`

65 MB/s, nice, nice. At this rate it's only going to take.... 3 days to wipe this 16TB drive.

```
Step 5/7 : RUN python3 -m pip install .
```
```
---> Running in 31b96e802fdb
/usr/bin/python3: No module named pip
```

Hmm.. So #fedora also ships a crippled thing that is not #python when you `dnf install python3`.

I was hoping that that was a reasonable alternative to Debian/Ubuntu ☹

Bugs like `dt.replace(year=dt.year + 1)`, code that works with ordinal day-of-year, etc.

Psst. Next year is a leap year. Depending on your deployment story, now (or 3 months ago😅) might be a good time to start looking into logic that won't handle leap years correctly.

#matrix isn't *great*, but it's a darn sight better than this.

"Oh I need to communicate with someone on Discord quickly, guess I'll launch it. Oh, there's an update available, so Discord *prevents me from opening their appliaction*."

Reason #215 to avoid #discord.

Note: This is one of the *exceedingly rare* occasions where I like something like this.

For the most part I find content about datetimes, DST and programming in general to be boring and uninteresting.