Django 3 whether to move?

Hello, I learned that not too long ago released a new version of Django, namely 3, in General, should go for it or 2 still rules be?
And also question main feature that Django 3 asynchronous in simple words what is it?
April 4th 20 at 00:56
4 answers
April 4th 20 at 00:58
Only that this explanation right now does not fit with the fact that under the hood Django 3. More specifically, there is nothing about asynchrony. And while at least the ORM will not make pseudosynchronous (on tadpole), the meaning of the third version does not. And when there are real async approach - I'm afraid to make) - amber_Ho commented on April 4th 20 at 01:01
@amber_Ho, a feeling that there Godwyn in a mug karyachitsya on this task. He certainly surprisingly productive citizen, but is unlikely to be managed in less than a couple of years, I think. - london_Koe commented on April 4th 20 at 01:04
@london_Koe, and this is a good opportunity to tocontribute in a very required feature. Only would time to find. - amber_Ho commented on April 4th 20 at 01:07
@amber_Ho,
but this is a good opportunity to tocontribute in a very required feature.

+

Only would time to find.

+ - london_Koe commented on April 4th 20 at 01:10
as I understand, asynchronous work faster? - olen.Rolfson commented on April 4th 20 at 01:13
@olen.Rolfson, asynchronous code allows to parallelize the operation of entry/withdrawal. Normal django project runs wsgi-service as several processes, each of which can serve one request per time unit. Accordingly, even if your project eats up all operatives and server processor time, more than a hundred competitive queries it can handle will not. In an asynchronous embodiment, it is theoretically possible to process tens of thousands konkretnyh connections. - london_Koe commented on April 4th 20 at 01:16
April 4th 20 at 01:00
1) If it is more or less a commercial project, I would sit on Django 2.2.9 LTS until until LTS on Django 3, and it is according to the plans of 2021 only. And the community will not give feedback that norms can juzat.

2) the Whole idea with asynchronous Django and justification of the reasons for the transition (where probably 5-6 times howevet about money and investors, and not a request of the community), I don't like. It is likely that they lock it and make it an alpha test for applicants.

Ie, in his pet projects, please, something fighting...I would have refused so far. There are more elegant solutions to the current problems that they are trying to solve using django 3.
not a request community

What? Request from the community for a long time.
If it's more or less a commercial project, I would sit on Django 2.2.9 LTS

Every project has its details, so usually just testing the new version and look at the result. There are enough projects that are jumping on the new version, it is better to do many small steps than a few and rare, but the giant jumps. - Roberta.Macejkovic commented on April 4th 20 at 01:03
April 4th 20 at 01:02
Django conditionally asynchronous 3.0, even more no than Yes. They have a roadmap for the introduction of async and this version is only the beginning.
April 4th 20 at 01:04
can simple words what is it?


look here
sarony - the fourth line from the top (3880 ..)
asynchronous - third (2413...)

when the same number of users ( and even more on the 3rd row out)

but writing code is also a need for asynchronous

Find more questions by tags Django