I run an outdated version of Django. #django #fail #hypstatic

Yikes haven't done a deploy since January 6. I've definitely been ignoring all of the USNs about Linux kernel vulnerabilities. #fail Django 2.2 release is what got me to get to upgrading #django #win

#django is a joy to use. Making my new blog app was so easy. Each view is only two lines of code! #win

Jumped to latest #django 2.0.x and then to latest 2.1.x today. No deprecation warnings, smooth sailing. As a plus, I turned on PYTHONWARNINGS for my app in systemd #win

hyperbola is ready for #django 2.1. https://github.com/hyperbola/hyperbola/commit/d92a79f. That was easy #win

I am surprised that #django autolinked the .tires domain. We live in the future.

hyperbola is now running #django 2.0. Added automigrate to hyperbola-app systemd unit, eliminating one of the last things I ever needed a bastion host for #win

I skipped #django 1.11.4 and 1.11.5. Finally did an upgrade today to 1.11.6 #win. My dep upgrades for python, js, and ansible deps are too coarse grained. Pulled in ansible changes which blocked the deployment #fail

related, using pip-tools to manage and pin python dependencies has removed uncertainty from my deploy process. Upgrade packages only when I intend to #win #django 1.11.3 upgrade went super smoothly in part due to this

Upgraded to #django 1.11 ... woo LTS

Tested a #django release candidate (1.11RC1) for the first time. Site continues to work. No deprecation warnings. #win

#django feature request and #patch accepted https://code.djangoproject.com/ticket/27541

Yay refactoring! #python #django #win

Now have proper retina image support on lifestream and contact page. Generating @2x and @3x images. The flexibility of django-imagekit helped. This is a well-designed library. #django #ux

This new #django admin UI is BEAUTIFUL!

Finally got around to getting my #django 1.9 upgrade branch over the line. Didn't have django-pipeline pinned and 1.6 introduced a breaking change to settings. All done now.

python -Wall is a neat trick. Cleaned up a bunch of #django deprecation warnings

I feel like my #django site is futureproofed for at least the next two minor version upgrades now. Just converted a ton of render_to_response snippets to the new render hotness. Even feels faster.

Despite being stable, #django deprecates frequently. What they deprecate tends to have been the recommended way of doing it circa 1.4 ... feels like they are slowly rewriting everything.

Fixed a long outstanding bug in how the sidebar on the lifestream calculated monthly post counts #win Tickled by the upgrade to #django 1.8 which caused them to all display as 1. #fail

Finally upgraded to #django 1.8. Only an 8 commit adventure

Finally subscribed to django-announce. I was running a super old version of 1.7 ... oops #django

#bug fixed https://github.com/hyperbola/hyperbola/commit/01b34d with minor staging break caused by django-pipeline renaming their templatetags #django

Now I have #utf8 support in #MySQL. I thought I did https://hyperbo.la/lifestream/174/ but that was a #fail. Bitten by the difference between utf8 and utf8mb4. Alas, #Django 500's; no emoji for me

The admin site is slightly modernized in #django 1.7 ... looks nice #win

hyperbola, now with #django 1.7 ... I love how easy it has gotten to deploy this site.

PyCharm is neat. #python #django I found the code analysis to be useful.

#django sure as hell doesn't make it easy to get at the database backend ... but the fact that I can is still awesome. Enabled post count badges on lifestream.

next project: convert #hyperbola to UTC, server, #django, and #mysql

Needed: #mobile optimized #django admin skin. Posting from my iPhone is less than ideal

wow link tags and auto RSS/Atom feed discovery ... welcome to the internet Ryan ... #fail ... I feel like #django is missing a template tag here.

#django 1.6 upgrade was a breeze. Just a single deprecation warning. #win ... took the opportunity to refactor some old code too :)

Upgraded #django from 1.4 alpha to 1.5.x stable tonight. It only took a couple hours. Mostly dealt with deprecated APIs and new template tag syntax

I don't ♥ manually managing character sets #fail Why doesn't #django ensure the #mysql db has #utf8 as its character set?

Woo! my #django #patch got accepted. https://code.djangoproject.com/changeset/16609

Got a #django bug accepted: https://code.djangoproject.com/ticket/16573

first post on the new server. It runs. I'm trying to make this #django thing leaner and less hacky. Still have a ways to go. Boy do I need to set up a dev env.

I avoid adding punctuation after my #hashtags because there's a #bug in my regex that parses them. #thingsishouldfix #django

After working with #rails for a bit now, I kinda like the #magic. DB interations seem so much more natural than they do in #django

Thinking about migrating this site to EC2. Probably gonna stick with #django. http://dev.hyperbo.la will probably die; github does it way better. Moving all media assets to s3: maybe. ssl: probably not

one day I'll set up a #django dev environment again. Until then, we'll do it live!

this site: now with 5 times fewer 500 errors #django #fail

for some reason every part of the #django admin worked except the root page. had to turn on debug mode to see I was improperly configured #fail

lol. edited the site live again while working on a new app. 500 errors abound. #django #fail

lesson learned: never edit a site live. #fail #django

This is why I like django's pluggable apps. I can get distracted and not finish a project, but the site still works. #django #distractions

lots of code refactoring going on right now. One drawback of the ease and speed of #django is that it allows you not to think.