Slashdot Mirror
DjangoCon 2016 To Be Held In Philadelphia In July (defna.org)
New submitter FlipperPA writes: It has just been announced that the 2016 vintage of DjangoCon US will be held in Philadelphia at The Wharton School of the University of Pennsylvania from July 17th through 22nd. DjangoCon US is a 6-day international community conference for the community by the community, held each year in North America, about the Django web framework. From its humble beginnings in a newsroom in Lawrence, KS, Django now powers some of the better known web sites on the planet, including The Washington Post, Mozilla, Instagram, Disqus, and Pinterest. Considered by many to be the "batteries included" web framework for Python, Django continues to attract new developers across the globe.
This conference is gonna be off the chain! Unchained, as it were.
Django's upgrade/deprecation policies are pretty well documented, but if a project is going to be unmaintained for a long time, and you're trying to, say, upgrade a Django 1.6 app to 1.9, you're going to be in for some pain, as in three versions a feature will go from supported, to quiet-deprecation to noisy-deprecation to absent. If a project is not going to be maintained to track the "latest" Django, it should target one of the LTS releases - 1.8 currently - which will have support till 2018.
That will give you security and data-loss-bug updates, but won't give you new features. If you wan't those, then you need to track the current version. If you really are stepping through 3 or more versions (or fewer, if it was already using a deprecated feature) then the best bet is to go through the deprecation documents and convert things over... or just re-write. Sometimes that IS simpler. And, of course, target a LTS if that's appropriate.