| | 1 | = Guidelines for writing, distributing and using Django applications = |
| | 2 | |
| | 3 | |
| | 4 | |
| | 5 | See |
| | 6 | |
| | 7 | |
| | 8 | = Guidelines for reusable application authors = |
| | 9 | |
| | 10 | |
| | 11 | |
| | 12 | * '''namespace''': apps should live in `django.apps`, i.e. if your app is named `frobnicate`, your code should be in `django.apps.frobnicate` |
| | 13 | |
| | 14 | * FIXME alternative: require use of namespace packages, see http://peak.telecommunity.com/DevCenter/setuptools#namespace-packages , review how Zope does it |
| | 15 | |
| | 16 | * FIXME '''Django version''': somehow the Django version used has to be conveyed (`django1.0-comments`?), again Zope app versioning should help |
| | 17 | |
| | 18 | * '''publishing''': apps should be packaged with `setuptools` and published in the [http://pypi.python.org/pypi Python Package Index], under trove category `Framework :: Django` |
| | 19 | |
| | 20 | * '''dependencies''': ordinary `setuptools` dependency handling |
| | 21 | |
| | 22 | |
| | 23 | |
| | 24 | = Package index = |
| | 25 | |
| | 26 | |
| | 27 | |
| | 28 | Additionally to the PyPi index, a separate indexing service with ratings, groupings and whatnot would be useful. [http://djangoplugables.com Django Pluggables] is a nice start. |