Weeknotes 2022-11-07
,Short work week. Gave me time to indulge in heavy yak shaving. At first, I tried to just make django-cast (the develop branch) work for newer Django and Wagtail versions. Then I realized I had to fix wagtail-srcset first and replaced poetry with flit while I'm at it. Then I got lost fixing some stuff in kptncook before I remembered that I have to also update django-indieweb and django-fileresponse to be able to finally fix django-cast and make it deployable on my staging system using the latest and greatest Django and Wagtail versions. Oh and then I fixed some bootstrap stuff in the commands.py of my Django startproject template. Maybe I'll manage to merge the develop branch of django-cast back into main soon after develop started to diverge back in 2019 iirc because I wanted to use Wagtail as a CMS. Looking forward to meet some hairy yaks on the way.
Articles
- Get a Mastodon instance running #290 | This yak is looking especially attractive atm
- Static-Dynamic Content With In-Memory SQLite | Hmm, cool - but I need to shave my postgres 15 yak first, sorry
- Becoming fasterthanlime full-time
Twitter
- No twitter this week, just yaks
Weeknotes
- Week in Review 2022-10-31 | Luis
- Weeklog for Week 43: October 24 to October 30 | Johannes
Software
- htmx v1.8.4 release
- Django 4.1.3 release | Support for Python 3.11 + some bugfixes
- django-upgrade Mega Release 1.11.0
- Component patterns A collection of cross browser UI components for use in accelerating or inspiring your own design systems.
Podcasts
- Was sollte Ihrer Meinung nach den Kapitalismus ablösen? (Das philosophische Radio)
- A Different Story Of Inflation With John Cochrane (Capitalisn't) | Doh - bonds and cash aren't the same?
- Probabilistic thinking with James “JD” Long (Data Science Salon) | Very familiar vibes here - I also wonder why people get away that often with publishing just an accuracy number which is meanlingless in most contexts. On the other hand, I don't buy the economic arguments in favor of the cloud: You just have to pay for what you use. You also have to pay for being able to use the cloud efficiently, you pay for stuff you forgot to turn off and last but not least you pay for not having competent IT people and living with grossly inefficient cloud solutions.
- HorseRecords - Andy Ide (Django Chat) | Hmm, maybe need to take a closer look at django-unicorn
- Episode 130: Fostering an Internal Python Community & Managing the 3.11 Release (The Real Python Podcast) | "Sometimes you have to break a few eggs to make an omelette.. and some dishes, and the restaurant" 😃