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.
Than
P.S.
>
> Effectively 2.2 is as far as you need to go for the time being because it is
> an LTS release. Might make a convenient initial goal. Should be pain-free.
>
Unfortunately that’s not an option.
--
You received this message because you are subscribed to the Google Groups
"Django users"
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, s
On 31/12/2020 2:16 pm, Benny M wrote:
Hi all,
I have a project that’s doing a rather sizable jump from 1.11.29 to 3.1.
I’m aware of the internal gotchas (enforced on_delete, settings syntax, etc) -
but I was curious if anyone knows of a package compatibility list exists?
Something like caniuse
Hi all,
I have a project that’s doing a rather sizable jump from 1.11.29 to 3.1.
I’m aware of the internal gotchas (enforced on_delete, settings syntax, etc) -
but I was curious if anyone knows of a package compatibility list exists?
Something like caniuse but for django-focused packages. Right
5 matches
Mail list logo