>From the page Tim linked:
"If you’re upgrading through more than one feature version (e.g. A.B to
A.B+2), it’s usually easier to upgrade through each feature release
incrementally (A.B to A.B+1 to A.B+2) rather than to make all the changes
for each feature release at once. For each feature releas
I accept Tim's advice to upgrade from one major version to the next. Even
if I want to upgrade from 1.11 to 2.2, I have to upgrade first to 2.0 and
then 2.1 and only then 2.2. It makes sense.
אורי
u...@speedy.net
On Tue, Apr 2, 2019 at 4:44 PM Derek wrote:
> I agree; and the reason for Django
I agree; and the reason for Django moving to LTS releases was so that you
would be able to upgrade from one LTS to the next. Hence the OP (and
others like me I am sure) asking how that can be done - we are looking for
specific advice or instructions (and less about "general" guidelines).
On Tu
always go for 2nd last or 3rd last release of any framework or any language
it will be more stable but if you want to go with 2.2 you can because it
comes with LTS
On Friday, March 29, 2019 at 2:22:10 PM UTC+5:30, Uri Even-Chen wrote:
>
> Hi,
>
> I want to upgrade Django from 1.11 to 2.2. Do I h
always go for 2nd last or 3rd last release of any frame it will be more
stable but if you want to go 2.2 you can because it comes with LTS
On Friday, March 29, 2019 at 2:22:10 PM UTC+5:30, Uri Even-Chen wrote:
>
> Hi,
>
> I want to upgrade Django from 1.11 to 2.2. Do I have to upgrade first to
>
The advice is to go from one the major version to the next. Don't try to skip
versions.
--
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+unsubscr...
The upgrade doc has good, general advice but does not specifically address
the issue of LTS-to-LTS upgrades; I must admit I am a bit disappointed as I
thought that there would be explicit, official support for this migration
(and its one of the reasons I have stayed on the older LTS up to now).
Consider the "Upgrading Django to a newer version" guide.
https://docs.djangoproject.com/en/stable/howto/upgrade-version/
On Friday, March 29, 2019 at 4:52:10 AM UTC-4, Uri Even-Chen wrote:
>
> Hi,
>
> I want to upgrade Django from 1.11 to 2.2. Do I have to upgrade first to
> 2.0 and then to 2.1,
you can upgrade directly from 1.11 to 2.2, but some of third party packages
may not support Django 2.2
On Fri, Mar 29, 2019 at 2:22 PM אורי wrote:
> Hi,
>
> I want to upgrade Django from 1.11 to 2.2. Do I have to upgrade first to
> 2.0 and then to 2.1, or can I upgrade directly from 1.11 to
I'd suggest not worrying too much about upgrading to 2.2 right away. Since
it's going to be an LTS release, the projects your project depends on will
probably consider adding 2.2 support fairly fast.
But if you want to give it a shot anyway, I'd suggest taking a look at what
changed from 1.11 to 2
First use 'pip freeze' in your virtual env to see all the packages
installed. Then checkout their official, latest documentation to see
whether they support django2.1 or not.
Even if all them do, you might need to make a lot of changes in your code
after upgrade.
And no, you dont need to install
Hi,
I want to upgrade Django from 1.11 to 2.2. Do I have to upgrade first to
2.0 and then to 2.1, or can I upgrade directly from 1.11 to 2.2?
By the way, we use many third-party packages and I'm not sure which version
of Django they support. Maybe not all of them already support Django 2.2.
Than
12 matches
Mail list logo