20140513-DjangoCon-App-loading

Recommendations

Info

Consistency• <strong>App</strong>s must have unique labels — backwards-incompatible.• Models must be imported with the same Python path —backwards-incompatible.• Models must be defined in an installed application orprovide their app_label explicitly — deprecation path.• Models mustn’t be imported before their application —deprecation path.36
Order of INSTALLED_APPSIf several applications provide the same resource,the earliest application in INSTALLED_APPS wins.• Management commands — backwards-incompatible.• Static files• Templates• Template tags and filters libraries• Translations37
Page 1: The Story of App-LoadingAymeric Aug
Page 7 and 8: Timeline• Feb ’07 — Joseph Ko
Page 9 and 10: Final implementation# myproject/app
Page 11 and 12: Initialization sequence$ django-adm
Page 13 and 14: Here’s a model# monsters/models.p
Page 15 and 16: Let’s find out# monsters/models.p
Page 17 and 18: In a development server$ django-adm
Page 19 and 20: Enter django.db.models.loading.AppC
Page 21 and 22: Hardest bug$ git log --reverse | eg
Page 23 and 24: Interesting behavior# monsters/mode
Page 25 and 26: Not even an accident# django/db/mod
Page 27 and 28: What’s new in Django 1.7?“I hop
Page 29 and 30: App-loading reloaded - non-goals4.
Page 31 and 32: Apps without models!!$ find . -empt
Page 33 and 34: Start-up hook# rock_n_roll/apps.py!
Page 35: App registry population• Populati
Page 39 and 40: App registry APIfrom django.apps im
Page 41 and 42: RuntimeError: App registry isn't re
Page 43 and 44: Dynamic models and other app loadin
Page 45 and 46: Django 1.6 project template# projec
Page 47 and 48: too complicated; didn’t listenhtt

20140513-DjangoCon-App-loading

Create successful ePaper yourself

Delete template?

Save as template?