mirror of
https://expo.survex.com/repositories/expoweb/.git/
synced 2024-11-27 09:42:02 +00:00
emph - online edit of handbook/troggle/trogdjangup.html
This commit is contained in:
parent
f608f0e9a1
commit
dd4080cb74
@ -10,7 +10,7 @@
|
|||||||
<h2 id="tophead">CUCC Expedition Handbook</h2>
|
<h2 id="tophead">CUCC Expedition Handbook</h2>
|
||||||
<h1>Upgrading Django for Troggle</h1>
|
<h1>Upgrading Django for Troggle</h1>
|
||||||
<h4>Why this used to be difficult</h4>
|
<h4>Why this used to be difficult</h4>
|
||||||
<p>Before Django 3.0, when Django was upgraded to a new version things broke across the entire django package, including things which we don't conciously use but are internal dependencies within Django. These were 'the way to do it' when troggle was first written for Django 0.7 in 2006. So upgrading troggle to a new Django version requires not just a broad beadth of knowledge across troggle, but also across the entire breadth of django itself. And the error messages are sometimes very unhelpful. This is no longer the case and the Django organisation has a very clear "non-breaking" policy between LTS releases.
|
<p>Before Django 3.0, when Django was upgraded to a new version things broke across the entire django package, including things which we don't conciously use but are internal dependencies within Django. These were 'the way to do it' when troggle was first written for Django 0.7 in 2006. So upgrading troggle to a new Django version required not just a broad beadth of knowledge across troggle, but also across the entire breadth of django itself. And the error messages are sometimes very unhelpful. This is <em>no longer the case</em> and the Django organisation has a very clear "non-breaking" policy between LTS releases.
|
||||||
<p>Now read <a href="trogdjango.html">Django and Troggle</a> if you haven't already.
|
<p>Now read <a href="trogdjango.html">Django and Troggle</a> if you haven't already.
|
||||||
|
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user