Re: Compatibility List

On 31/12/2020 6:18 pm, Benny M wrote:
> Thanks for your response, Mike.
> I was using "changelog" and "release notes" interchangeably; sorry for the confusion.
>
> My question is more about packages that extend Django's capabilities (i.e. django_csp, django_rq, etc.) as opposed to Django itself.
>
> Thankfully Django has great release notes, so catching up there isn't a problem. However, what would be good way to audit third-party dependencies to find out which ones need to be updated to work with 3.1, or which haven't caught up?

If it was my project I would migrate it one increment at a time. I went
from 1.11 to 2.2 in one step but had to go back and review the release
notes here and there to resolve a tiny number of issues which were in
fact well flagged. It might have been easier to do the intermediate
upgrades.

Having loads of unit tests is probably the most important thing. Vital
if it is running on Python 2.7.

Adjusting from Python 2.7 in 1.11 to Python 3.x in 1.11 was also
important. I had it running on 3.6 and 2.7 before moving forward to 2.2

As for the packages, if they are currently supported I'm sure they will
be up-to-date.

YMMV

Mike

>
> Benny
>


--
Signed email is an absolute defence against phishing. This email has
been signed with my private key. If you import my public key you can
automatically decrypt my signature and be sure it came from me. Just
ask and I'll send it to you. Your email software can handle signing.


--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/8e4fe962-65ad-bb02-d4f6-88b4bd0803ea%40dewhirst.com.au.