djng
nanodjango
djng | nanodjango | |
---|---|---|
1 | 5 | |
133 | 695 | |
0.0% | 11.2% | |
- | 8.3 | |
over 13 years ago | 2 months ago | |
Python | Python | |
BSD 2-clause "Simplified" License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
djng
-
Building a full Django project, starting with a single file
I'm a big fan of the single-file Django ambition - it's the feature I most envy from frameworks like Flask and Starlette.
I actually had a go at this myself 15 years ago, with a project I called Djng: https://github.com/simonw/djng - more details on that here: https://simonwillison.net/2009/May/19/djng/
nanodjango
-
This Week In Python
nanodjango – Full Django in a single file - views, models, API, with async support.
- Nanodjango: Full Django in a Single File
- Nanodjango
-
Building a full Django project, starting with a single file
The app-based model is really baked into Django. As we've seen from a bunch of examples, especially recently, it's not too hard to build out a single-file project that serves a simple home page with a brief message. As soon as you want to support a full actual page, and a set of pages, you really have to figure out a well-thought-out plan for how people will expand the project.
If you're still interested in this work, I suggest checking out nanodjango, which was mentioned earlier in this thread. That project is new, but there's a plan from the outset for how people can transition from the single-file based version to a standard Django project. You might also want to check out Andrew Godwin's django-singlefile project. It's meant to support small flask-like projects, where you don't have any intention of expanding out into a standard Django project.
Both of these projects have their own code that takes what's included in the small file and tells Django how to make sense of it. That's much different than the projects that are only trying to make use of what's included in Django itself.
(I'm the author of the Django from first principles series that was submitted here, but I didn't see it on HN until this morning.)
nanodjango: https://github.com/radiac/nanodjango
django-singlefile: https://github.com/andrewgodwin/django-singlefile
What are some alternatives?
djantic - Pydantic model support for Django
Local-File-Organizer - An AI-powered file management tool that ensures privacy by organizing local texts, images. Using Llama3.2 3B and Llava v1.6 models with the Nexa SDK, it intuitively scans, restructures, and organizes files for quick, seamless access and easy retrieval.
django-singlefile
tinylangs - Real programming languages in 50 lines of code
tortoise-orm - Familiar asyncio ORM for python, built with relations in mind
httpdbg - A tool for Python developers to easily debug the HTTP(S) client requests in a Python program.
iommi - Your first pick for a django power cord
django-first-principles - A Django project, developed from a single file.
gptme - Your agent in your terminal, equipped with local tools: writes code, uses the terminal, browses the web, vision.