#6275 closed (wontfix)
An "official" place to put applications
Reported by: | Marinho Brandão | Owned by: | nobody |
---|---|---|---|
Component: | Contrib apps | Version: | dev |
Severity: | Keywords: | apps, django.contrib | |
Cc: | robillard.etienne@… | Triage Stage: | Unreviewed |
Has patch: | no | Needs documentation: | yes |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Some developers use the project path to put applications in, some others put in a 'apps' folder or something like this.
Would be nice once place to import from applications from, like the following example:
from django.apps import myapp
To turn this possible, I think will be necessary exists a way to 'register' the application with a simple name (or change INSTALLED_APPS to 2-tuples-style).
Change History (9)
comment:1 by , 17 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:2 by , 17 years ago
Resolution: | invalid |
---|---|
Status: | closed → reopened |
I disagree.
I know the best practices but I wish this idea be availed better because we can gain cohesion and flexibility. An "application registration" would turn possible an applications repository, turning them more plugable than are today.
comment:3 by , 17 years ago
Cc: | added |
---|---|
Component: | Uncategorized → Contrib apps |
Keywords: | apps django.contrib added |
Needs documentation: | set |
I agree with the idea of picking a standard namespace for user-contributed django apps. Having such a scheme
documented more extensively in django could leads to things like marinho mentioned.
comment:4 by , 17 years ago
Resolution: | → invalid |
---|---|
Status: | reopened → closed |
This is out of scope for Django; aside from certain minimum necessities like the existence of a models
module inside an application, Django does not and will not attempt to dictate where you put your code.
follow-up: 8 comment:5 by , 17 years ago
Resolution: | invalid |
---|---|
Status: | closed → reopened |
Sorry but I don't agree. If we want users to distribute third-party applications on top of django, then why not explaining how
to distribute them using setuptools ?
I dont think this has nothing to do with dictature (really).
It's only being nice to users (developers) wanting to adopt a common standard for sharing contributed apps.
Person who say it cannot be done should not interrupt person doing it. --Chinese Proverb
comment:6 by , 17 years ago
I agree to Erob and I think a common namespace or something kind of solution would be possible to developer put the applications WHEREVER wants. Today, the developer must put all of apps in once place, or create symlinks (Windows doesn't supports) or include miriads of paths to PYTHONPATH.
comment:7 by , 17 years ago
Resolution: | → wontfix |
---|---|
Status: | reopened → closed |
Hello there,
I don't understand what this is proposing, as it is currently written. For that reason, I'm marking this as "wontfix." If you want to provide a fuller explanation of your idea, please open a new ticket rather than reopening this one.
comment:8 by , 17 years ago
Replying to erob:
Sorry but I don't agree. If we want users to distribute third-party applications on top of django, then why not explaining how
to distribute them using setuptools ?
Isn't it the job of setuptools to document how to use setuptools?
comment:9 by , 17 years ago
Adrian, ok (and I thank for your interest).
I wrote the following task: #6300
This is out of scope for Django. You can accomplish this however you like with the use of
PYTHONPATH
and/or
sys.path
. Ask on django-users on some of the best practices others are doing to accomplish something similar.