It's not unreasonable to expect to be finished with software.
>For better or for worse, this is simply how software works.
This is false. The author has already fallen into this trap by using a programming language which is also subject to this, however.
>Things have to be updated. Unless you want to eschew security updates (which is not smart), there is never such a thing as a fully "finished" product.
There is such a thing as finished software, but I can understand why something such as a WWW framework wouldn't be. The WWW is ugly and misguided and inspires disgusting systems to accomodate it.
>Software maintenance is part of the job responsibilities.
When you have a project with no real design goals, apparently, I agree. Otherwise, you can remark on how a program achieves its goals and so is finished. That doesn't stop minor improvements or reworkings, but those would be entirely unnecessary.
>This post is particularly targeted at Django, but I feel that it applies to almost every web framework or piece of software
I agree, because, again, the WWW is a disgusting tangle of systems that encourages similarly disgusting systems.
One language I enjoy is Common Lisp. The standard hasn't changed in decades and there are many implementations. I can finish a library and then never need to touch it again. Python can't compare.