djapps
djapps allows you to load your django apps by their app names rather than by the module path. This is particularly useful if you don’t know where modules will be installed or if you plan to allow overriding of your apps (eg a user replaces your foo.bar app with myfoo.bar).
Usage
If you have a django app called bar in a package called foo (such that you would add foo.bar to your INSTALLED_APPS) then you can get hold of bar without knowing its full module path:
import djapps.bar
djapps hooks into python’s regular import mechanism so all the normal ways to import things will work:
from djapps.bar import models from djapps.bar.models import MyModel as ThisIsMyModel
Your app names in a django project should all be unqiue, djapps won’t work if they are not (but django won’t like that either).
Installation
Use your favorite install method, for example:
$ pip install djapps
You do not need to add djapps to your INSTALLED_APPS, just start using it.
Release files for djapps 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| djapps-0.1.1.tar.gz | 3.0 kB | Details |
Release files / djapps-0.1.1.tar.gz
| Download URL | djapps-0.1.1.tar.gz |
|---|---|
| Size | 3.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fa7c90f592734cc0d9de99f38176177f0020d37b2bd3448ef2bd2f03f9ee5f85
|
|
BLAKE2b-256 checksum How to use checksums |
b04590265d5647987bed1083f518949fcca42012e6cf589043fb96805850dc2b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |