Django VS Masonite

https://github.com/django/django/blob/3.2.16/django/contrib/postgres/apps.py#L61 https://github.com/django/django/blob/3.2.16/django/contrib/postgres/signals.py

Last commit, two days ago. I don't know where you looked at: https://github.com/django/django/

Many of the available jobs for Python that I could find were either for Django based projects or Machine Learning stuff I didn't like too much. So using Masonite would only be for green field type projects.

Django only uses it for the admin, and removed as a dependency for many files, but they don't seem to plan to drop its support entirely, not for the Django 4.x versions anyway (it looks like they updated it last week only https://code.djangoproject.com/ticket/33961), and my guess would be that the same problem will arise : the base django-admin will eventually drop it but many third party widgets will still rely on it.

Django is an WebFramework, Meinheld is an WSGI Server framework.

https://github.com/django/django

https://github.com/mopemope/meinheld

So django meinheld is basically saying that i used Django served by meinheld in that benchmark.

Python(v3.10), Django(v4.1.2) and Channels(v4.0.0) at the Backend;

projects that use setuptools : requests, django, flask, boto3... projects that use poetry : ward, ... (if you have some with more than 500 stars, share them in comments) projects that use pipenv : ... (if you have some with more than 500 stars, share them in comments)

7. Django

Masonite is a wonderful Python framework, much similar to Laravel I found in 2018. I even chatted with Joseph about it in the old Slack channels, before the community moved to Discord.

Masonite Framework: https://github.com/MasoniteFramework/masonite