nanodjango VS gptme

nanodjango – Full Django in a single file - views, models, API, with async support.

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

gptme – Your agent in your terminal, equipped with local tools: writes code, uses the terminal, browses the web, vision

I'm building a little code+chat CLI called gptme, that aims to leverage the capabilities of local LLMs to mimic the functionalities offered by OpenAI's "Advanced Data Analysis" (formerly known as "Code Interpreter"). It is similar in spirit to the more popular open-interpreter, which some of you might have heard of.