Drop python 3.6 - 3.7 and django 2.

[baseplate-admin]

Is your feature request related to a problem? Please describe.
I'm always frustrated when i see EOL dependencies are in pyproject.toml

Describe the solution you'd like

1. Drop every EOL or soon to be EOL python version. ( 3.6 - 3.7 )
2. Bump django dependency to 3.2 as django 2 is unsupported at this point.

Reasoning :

1. We can directly support modern django features ( eg : sync_and_async_middlewares )
2. We can get access to Async ORM ( which is unsupported in django 2.0 )
3. ...
   I think its a good time to address this as django-ninja is moving to a v1 release

[baseplate-admin]

@vitalik ,

What's your take on this ?

[skokado]

+1

[vitalik]

personally I do not see reason to drop django 2 - there are just few compatibility wrappers (the async views are already used heavily alot by the projects I'm keeping eye on)

python 3.6 will be dropped with pydantic2

python 3.7 most likely will stay (basically what pydatic supports will be supported by django ninja) - I see in statas some persentage is still using 3.7