| Blog Info | James Bennett |
|---|---|
| Blog website | Link |
May 5, 2020 » James Bennett » [Archived Version]
On April 20th, 2020, a release manager named Benjamin Peterson smashed the “publish” button on Python 2.7.18. The Python 2 release series reached the end of its upstream support from the Python core team at the start of the year. I don’t know for certain, but I assumed the timing of the actual final package was meant to occur during PyCon (which, until a global pandemic struck, was scheduled for mid-April), possibly so there … Read full entry
Read MoreMay 5, 2020 » James Bennett » [Archived Version]
On April 20th, 2020, a release manager named Benjamin Peterson smashed the “publish” button on Python 2.7.18. The Python 2 release series reached the end of its upstream support from the Python core team at the start of the year. I don’t know for certain, but I assumed the timing of the actual final package was meant to occur during PyCon (which, until a global pandemic struck, was scheduled for mid-April), possibly so there … Read full entry
Read MoreMarch 23, 2020 » James Bennett » [Archived Version]
Well, that provoked some discussion. While there were plenty of people who agreed with the general idea of that post, there were also quite a few objections. And most of those seem to fall into two main categories: people who want some type of additional layer (and may or may not call it a “service”) as a way of managing cross-cutting complexity, and people who want it as an isolating abstraction for testing. There’s also a third … Read full entry
Read MoreMarch 23, 2020 » James Bennett » [Archived Version]
Well, that provoked some discussion. While there were plenty of people who agreed with the general idea of that post, there were also quite a few objections. And most of those seem to fall into two main categories: people who want some type of additional layer (and may or may not call it a “service”) as a way of managing cross-cutting complexity, and people who want it as an isolating abstraction for testing. There’s also a third … Read full entry
Read MoreMarch 16, 2020 » James Bennett » [Archived Version]
This post now has a followup. Recently I’ve seen posts and questions pop up in a few places about a sort of “enterprise” Django style guide that’s been getting attention. There are a number of things I disagree with in that guide, but the big one, and the one people have mostly been asking about, is the recommendation to add a “service layer” to Django applications. The short version of my opinion on this … Read full entry
Read MoreMarch 16, 2020 » James Bennett » [Archived Version]
This post now has a followup. Recently I’ve seen posts and questions pop up in a few places about a sort of “enterprise” Django style guide that’s been getting attention. There are a number of things I disagree with in that guide, but the big one, and the one people have mostly been asking about, is the recommendation to add a “service layer” to Django applications. The short version of my opinion on this … Read full entry
Read MoreFeb. 3, 2020 » James Bennett » [Archived Version]
Once upon a time I wrote a bit about testing, specifically how I was organizing and testing my open-source Django apps. It’s been a while since that post, though, and the calendar has even flipped over to a new penultimate digit in the year number, so it’s worth revisiting to go over what’s changed in how I do things and what’s stayed the same. And since I do maintain a couple things that aren’t … Read full entry
Read MoreFeb. 3, 2020 » James Bennett » [Archived Version]
Once upon a time I wrote a bit about testing, specifically how I was organizing and testing my open-source Django apps. It’s been a while since that post, though, and the calendar has even flipped over to a new penultimate digit in the year number, so it’s worth revisiting to go over what’s changed in how I do things and what’s stayed the same. And since I do maintain a couple things that aren’t … Read full entry
Read MoreJan. 20, 2020 » James Bennett » [Archived Version]
The other day on a Slack I hang out in, someone posted an amusing line of Python code: port = "{port}:{port}".format(port=port) If it’s not clear after the inevitable Swedish-chef-muppet impression has run through your mind, this string-formatting operation will replace the contents of port with a string containing two copies of whatever was in port, separated by a colon. So if port was "foo", now it will … Read full entry
Read MoreJan. 20, 2020 » James Bennett » [Archived Version]
The other day on a Slack I hang out in, someone posted an amusing line of Python code: port = "{port}:{port}".format(port=port) If it’s not clear after the inevitable Swedish-chef-muppet impression has run through your mind, this string-formatting operation will replace the contents of port with a string containing two copies of whatever was in port, separated by a colon. So if port was "foo", now it will … Read full entry
Read More