Document using Django's ORM in other Python projects

[LilyAcorn]

Code of Conduct

• I agree to follow Django's Code of Conduct

Feature Description

There's a long standing desire to make the ORM easier to use outside of a regular Django project. (Script usage for example.) Django should explicitly support this use-case, and provide documentation to guide users.

Problem

While it is possible to use the Django ORM without much of Django's other machinery already, there is still some minimal configuration with settings and calling django.setup(). The necessary configuration is difficult to discover, so many users find it difficult to get started or don't think it's possible.

Request or proposal

request

Additional Details

Extracting the ORM into a separate package is proposed in #6. This proposal is for an easier step that may satisfy the majority of use-cases. It will also provide a clearer backdrop for pursuing changes to make using the ORM in external projects easier.

Implementation Suggestions

No response

[github-actions]

Thank you LilyAcorn for sharing your idea! We have a lot of them so please be patient. You can see the current queue here.

Community instructions

For commenters, please use the emoji reactions on the issue to express support, and/or concern easily. Please use the comments to ask questions or contribute knowledge about the idea. It is unhelpful to post comments of "I'd love this" or "What's the state of this?"

Reaction Guide

• 👍 This is something I would use
• 👎 This is something that would cause problems for me or Django
• 😕 I’m indifferent to this
• 🎉 This is an easy win