OK, I'm moving. I'll do the whole magic redirect thing later on, but just in case, I'm going to be over here:
See you on the other side! 🤞
Remote
Carlton Gibson 🇪🇺
@carlton@fosstodon.org
mastodon 4.7.3Veteran software engineer and open source juggler 🤹 Last optimist in town.
Former Django Fellow, Security Team and 6.x Steering Council member. I work mainly on and with the #Django web framework. I'm having fun these days mixing that with #htmx and #AlpineJS.
Other than that, it’s parenting, cooking, and philosophy. He/him
127 Followers
286 Following
38 Posts
Joined October 29, 2022
Website:
GitHub:
Skipping the Django conference season this autumn is still the right call for me but the FOMO is hitting hard now. 😅@djangodenmark@fosstodon.org's Django Day TOMORROW, @djangocon@fosstodon.org in a week or so, and then @djangoconafrica@fosstodon.org next month
Online tickets it is going to have to be 📺🍿💬
Massively happy to see this post for the next @djangonaut@indieweb.social program on the @django@fosstodon.org blog 🚀
https://www.djangoproject.com/weblog/2023/oct/19/djangonaut-space-now-accepting-applications/ #Django
Replying to
@felixxm @sarahboyce @adamchainz Sorry 😞 I do too really. It’s just this phenomenon of the numbering confusing the non-initiated.
When you retire, you can start hot potatoes too! 😜
Reading the chaos.social rules. **Finally** understand the difference between public and quiet/unlisted posts.
https://meta.chaos.social/rules#:~:text=Clarification,-:%20You%20post%20to
Replying to
@djangochat @nessita @wsvincent It’s just an idea to stimulate your thought, rather than an actual suggestion, but… Why CalVer?
Well, we don’t really do Major versions, 5.0 could just have well have been 4.3, and Django release schedule IS timebased…
That I ❤️ CalVer is entirely incidental 😜
Replying to
@webology @valberg @nessita @sarahboyce @djangochat @wsvincent “How will we decide?” - we’ll take positive comments on a fedi thread (muting negative ones) 😜
Replying to
@sarahboyce @djangochat @nessita @wsvincent BRILLIANT! 🤩
I’ve got a Not-Really-Secret-Rant™ in the back-pocket, which is “⚠️ Don’t use the LTS!”
I’ve half-floated it at various times over the years. Turns out folks are quite (en-us) attached to it. 😳
Clients will service their cars, but not update their Django applications it seems 😜
(Don’t @ me! 🥰)
Replying to
@adamchainz @sarahboyce @djangochat @nessita @wsvincent I DO think having the LTS is good as an insurance though… say a disruptive change did occur, it gives the ecosystem room to breathe, and heal that. So keeping it on 👍
(That I don’t use it is because such changes have been managed by the API stability, depreciation, and backport policies successfully in recent years, and that is projectable forwards.)
Replying to
@_chrismay thanks, yes, it would be lovely. It’s been a monster 12 months though, and at some point something has to give.
You will have a great time though, and we can meet next year 😉
Replying to
@samuelcolvin@fosstodon.org @webology@mastodon.social @hynek@mastodon.social Very wise! I’m not going back there 😜
Replying to
@paulox Absolutely! It was great. I’ll be in Vigo for @djangoconeurope for sure. (Just needed a pause this time round, given life.)
Replying to
@EmmaDelescolle@mastodon.social that’s awesome 🤩 I shall enjoy browsing 👀
A great showcase for what you can do with django-classy-doc. #Django
Replying to
@sarahboyce @djangochat @nessita @wsvincent I'm just gonna park my 👍 here. We can come and pick it up when we've got a few more to put with it 😜
Replying to
Replying to
@kevinrenskers Yeah, or we could just decide that the existing system is fine, and continue with it. The point of the post was just to ask folks to ponder it, on the back on the discussion on the podcast.
(Most likely is that changing isn’t worth the disruption, but we’ll see.)
Replying to
@kevinrenskers yep, that’s another option. The change from 1.11 to 2.0 made sense from this point of view, because that was dropping Python 2, which was kind of big. Since then though we could have just ticked along really…
The LTS is popular. It gives folks a stable supported version for essentially 3.5 years.
Replying to
@marcelotryle@fosstodon.org So I get Executing :1> result=None created at /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/asyncio/tasks.py:636> took 0.254 seconds running that, with a test file.
Replying to
@marcelotryle@fosstodon.org Sure. It tells you the function you blocked the event loop in. But not the exact line no.
Replying to
@marcelotryle@fosstodon.org Q: what are you looking for that isn't asyncio debug mode? 🤔
https://docs.python.org/3.11/library/asyncio-dev.html#asyncio-debug-mode
Replying to
@marcelotryle@fosstodon.org so can that log entry be raised to a warning? I suspect so, although I didn't look into it. My thought was that asyncio already ≈does what you're asking (or so it looked)
Replying to
@marcelotryle@fosstodon.org Okay, gotcha.
Do you think that’s a legitimate part of the Better Error Messages effort?
Replying to