expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2024-11-27 01:32:03 +00:00
Code Issues Packages Projects Releases Wiki Activity

update to more recent Django versions - online edit of handbook/troggle/trogdjangup.html

Browse Source
This commit is contained in:
Expo on server 2024-11-22 18:30:22 +00:00
parent 6b97365d21
commit d885981037
1 changed files with 49 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

65
handbook/troggle/trogdjangup.html
View File

@ -5,11 +5,12 @@
<title>Handbook Troggle and Django</title>
<link rel="stylesheet" type="text/css" href="/css/main2.css" />
</head>
<body><style>body { background: #fff url(/images/style/bg-system.png) repeat-x 0 0 }</style>
<body>
<style>body { background: #fff url(/images/style/bg-system.png) repeat-x 0 0 }</style>
<h2 id="tophead">CUCC Expedition Handbook</h2>
<h1>Upgrading Django for Troggle</h1>
<h4>Why this is difficult</h4>
<p>When django upgrades to a new version things break 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.
<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>Now read <a href="trogdjango.html">Django and Troggle</a> if you haven't already.
@ -25,22 +26,53 @@
<th>End of security fixes</th>
</tr>
<tr>
<td>4.2 LTS</td>
<td>April 2023</td>
<td>December 2023</td>
<td>April 2026</td>
<td>6.1</td>
<td>August 2026</td>
<td>April 2027</td>
<td>December 2027</td>
</tr>
<tr>
<td>6.0</td>
<td>December 2025</td>
<td>August 2026</td>
<td>April 2027</td>
</tr>
<tr>
<td>5.2 LTS</td>
<td>April 2025</td>
<td>December 2025</td>
<td>April 2028</td>
</tr>
<tr>
<td>5.1</td>
<td>5.1.3</td>
<td>April 2025</td>
<td>December 2025</td>
</tr>
<tr>
<td>5.0</td>
<td>5.0.9</td>
<td>August 7, 2024</td>
<td>April 2025</td>
</tr>
<tr>
<td>4.2 LTS</td>
<td>4.2.16</td>
<td>December 4, 2023</td>
<td>April 2026</td>
</tr>
<tr>
<td>4.1</td>
<td>August 2022</td>
<td>April 2023</td>
<td>December 2023</td>
<td>4.1.13</td>
<td>April 5, 2023</td>
<td>December 1, 2023</td>
</tr>
<tr>
<td>4.0</td>
<td>December 2021</td>
<td>August 2023</td>
<td>April 2023</td>
<td>4.0.10</td>
<td>August 3, 2022</td>
<td>April 1, 2023</td>
</tr>
<tr>
<td>3.2 LTS</td>
@ -70,7 +102,7 @@
</table>
</div>
<h4>Major, minor and releases</h4>
<p>Django release 3.2.10 is major-version 3, minor-version 2, and patch-release 10. 3.2 is the "feature release" and patch releases within each
<p>Django release 4.2.16 is major-version 4, minor-version 2, and patch-release 16. 4.2 is the "feature release" and patch releases within each
feature release are not meant to break anything. They are just to fix bugs.
<p>Things <em>will break</em> between <a href="https://docs.djangoproject.com/en/dev/internals/release-process/">feature releases</a> which come
out every 8 months. We plan on upgrading troggle on the server whenever we upgrade the server operating system, which we do only every 2-3 years
@ -98,6 +130,8 @@ troggle test suite. See <a href="troglaptop.html">how to set up a troggle softwa
sqlite database browser software very helpful and that you will need to know git.
<h3 id="djangotricks">Important Tricks</h3>
[I. November 2024 we are planning on moving from pip to uv for managing python vitrual environments.]
<p>There are six critical tricks that make everything much, much easier:
<ol>
<li>Use <a href="https://docs.python.org/3/library/venv.html">pip venv</a> or virtualenv to set up a virtual python environment within which you can easily and quickly change the specific releases of python, django, django's dependencies and django plugins.
@ -234,6 +268,5 @@ Return to: <a href="trogdjango.html">Django and Troggle</a><br />
Return to: <a href="trogintro.html">Troggle intro</a><br />
Troggle index:
<a href="trogindex.html">Index of all troggle documents</a><br />
<hr />
</body>
<hr /></body>
</html>