Hi Ahmed,
I made some inline comments
On Sat, 31 Mar 2018, 10:44 Haroon Ahmed, wrote:
> Hi,
>
> I am using python 3.4 already!
> Yes my project is big, it is almost completed now but the requirement is
> to upgrade it to latest suitable release and that release should not
Hi,
See https://www.djangoproject.com/weblog/2015/jun/25/roadmap/ how Django
releases and fixes are applied.
la 31. maaliskuuta 2018 klo 12.45 Haroon Ahmed
kirjoitti:
> Hi,
>
> I am using python 3.4 already!
> Yes my project is big, it is almost completed now but the
Hi,
I am using python 3.4 already!
Yes my project is big, it is almost completed now but the requirement is to
upgrade it to latest suitable release and that release should not be
insecure.
when i started this project, it was not written on Django 1.9.8 official
document that its an insecure
Hi,
In most cases, if possible I would upgrade latest release. Main issue with
1.11 to 2.0 upgrade is Python 2 support. 1.11 is the last version to
support Python 2.7 and starting from Django 2.0 Python 3 is required.
Of course, if your project is a big that takes long time to upgrade,
sticking
Hi,
Thanks for the information!
Should i upgrade to Django 2 for my project? As Django 2 is not Long Time
Supported.
Django 1.11 is the latest release that is Long Time Supported yet!
Should I go for Django 1.11 at the moment rather then Django 2.0? What
will be your suggestion for me?
What
Hi,
Standard procedure to update Django is to upgrade gradually all versions
from source version to target.
There is no single document to describe changes needed between versions
that are apart more than one release.
Only changelog you can find is at every release which contains changes from
Hi,
Currently my application is developed with Django 1.9.8 and I want to
upgrade it to 2.0.3 because
Django 1.9.8 is an insecure version of django as mention on it official
documentation.
https://docs.djangoproject.com/en/1.9/internals/release-process/#backwards-compatibility-policy
This
7 matches
Mail list logo