#Appreciation for @carlton today. I have recently opened an issue and a PR on his repos and the responses have been of kindness and thoughtfulness to my potential ramblings (especially the issue I raised then closed!)
> Custom tags may now set extra data on the Parser object that will later be made available on the Template instance. Such data may be used, for example, by the template loader, or other template clients.
Django 5.1 alpha 1 is now available. It represents the first stage in the 5.1 release cycle and is an opportunity for you to try out the changes coming in Django 5.1.
This alpha milestone marks the feature freeze. The current release schedulecalls for a beta release in about a month and a release candidate about a month from then. We'll only be able to keep this schedule if we get early and often testing from the community. Updates on the release schedule are available on the Django forum.
As with all alpha and beta packages, this is not for production use. But if you'd like to take some of the new features for a spin, or to help find and fix bugs (which should be reported to the issue tracker), you can grab a copy of the alpha package from our downloads page or on PyPI.
The PGP key ID used for this release is Natalia Bidart: 2EE82A8D9470983E.
I finally got around to upgrading my main project from Django 4.2 to Django 5.
I allocated several hours this evening for the arduous process of making sure I got everything right, and before I got started I figured I'd give django-upgrade (by @adamchainz) a try this time around.
No more than 15 minutes later my project was running on Django 5, tested good, and pushed to production.
Wait, what?!?! 😲
Super impressed with how easy django-upgrade made it ❤️
Here's a generic response for object creation with django-ninja:
class GenericCreatedSchema(Schema, Generic[EmbeddedType]):
success: bool
created_object: EmbeddedType
= use the same generic response template for ALL object creation endpoints.
But even better: I can use different response types in the same API endpoint, using HTTP status codes - depending on which fields are exposed to the user.
All of this translates to OpenAPI spec automatically 💯
Early AM, we begin to work on the Django framwork via Python. I've feared the framework for a while, but today I am going to handle it. Never let the programming lang handle me. lol.
Oy! Today, it's the 10 year anniversary for #Django PR#2692 🥳
It's definitely worth celebrating how the good forces were victorious against all the loud mouth conservatives/trolls. Since my office is full today, I might need to get both a primary cake and a replica cake for redundancy 🍰
Congrats and thanks to @fcurella and everyone else involved in this.
On May 20th, it's 10 years anniversary for #Django PR#2692 - feeling very thankful for people who were around early to start this long journey, despite all the crazy internet hate.
You were victorious, so if you know who to congratulate or want to celebrate it, you should... well it's a Monday, but it can be a good opportunity to buy a primary cake and have some replicas ready in case of a extra demand.