django-async-orm VS Django

I'm not sure if its official. Would love some more guidance/clarity/docs/funding from the django foundation on what it looks like to migrate legacy code to the new ways.

The rednaks repo works great for just giving the new async stuff a go. If everything else is also using async.

I did some experimentation with this. And its a pain trying to migrate a production application that uses gevent and psycogreen2.

The documentation on the code migration path is pretty sparse.

The main hiccup that I ran into was psycogreen2 not being supported.

https://stackoverflow.com/questions/67735453/django-async-or...

https://github.com/rednaks/django-async-orm/discussions/9

Plays well with others : And get this, HTMX buddies up with your go-to tech. Rocking with Django or vibing with Flask? HTMX slips right in, boosting your game without a total remodel.

Django: Django, with its "batteries-included" philosophy, provided a comprehensive suite for web development. Yet, it was primarily synchronous in nature, relying on worker processes or threads.

I built a custom blog using Django the other day, and made some detailed notes on how I did it since it's been a while since the last time.

https://til.simonwillison.net/django/building-a-blog-in-djan...

Atom support was easy, thanks to Django's built-in syndication Library (a feature for over 18 years at this point https://github.com/django/django/blame/1.0/django/contrib/sy...)

Can you explain a bit more about the Django ORM being very thin and easy to read? It does seem like the Django ORM is thin (from an architecture perspective), but it doesn't seem to be small, it seems to be pretty big. Maybe I'm not understanding it though, so here's what I see:

The "ORM" part of Django seems to be everything in `django.db.models.Model`, which seems to require you to declare your Models as subclasses of the aforementioned class. Looking into that code though, it seems like the implementation supporting all this is around ~20,000 lines of Python: https://github.com/django/django/tree/main/django/db/models

That doesn't strike me as a super lightweight. For comparison, all of Flask (a Python WSGI web app framework, but mostly a 10+ year old project to compare to, and excluding tests) is ~4,000 lines of Python.

Is there a small subsection of the code in `django/db/models/` that is all that's necessary to use the ORM part? Or maybe I'm missing something about the "core" of the ORM?

Several frameworks for developing web APIs have been developed, such as Django and Flask, but the underlying speed problem has always been present. As a result, another Python framework, FastAPI, has been developed to combat this issue.

Compared to frameworks like django, which I personally love, setting up a web-socket server in node is incredibly simple, thanks to the web-socket package

Django Project Official Website - The official website of the Django web framework provides comprehensive documentation, tutorials, and resources for getting started with Django.

The first part of the name PySeKT comes from Python, a programming language known for its clean syntax and excellent readability. Python's comfort of coding and the wealth of libraries available for nearly every programming task makes it a cherished choice for developers worldwide. In our stack, Python, particularly with Django [with DRF], powers our backend, providing the robustness and secure handling of APIs.

Crash course on python, django project section explains it nicely. Also you could go on https://www.djangoproject.com/ for more aspect of django and how they function.

Django is a high-level Python web framework that enables rapid development of secure and maintainable websites. It has over 71.5k stars on Github and is used by companies such as Instagram and Mozilla. Flask is a micro web framework that is lightweight and easy to use. It has over 63.3k stars (2023) on Github and is used by companies such as Airbnb and Netflix.