On Fri, Mar 19, 2010 at 10:16 PM, sebastien requiem <[email protected]> wrote: [...] > >> 2) No Gems. Why not have a central repository that tracks middleware >> and its versioning? >> Seems like a crap-shoot to use middleware if you don't know if its >> being utilized, updated, or buggy. >> > > I guess that looking at pypi.python.org should give you a hint.
Also take a look to virtualenv + pip >> 3) This may be purely out of my ignorance: I don't care to have all my >> models in my app in one file. Can't I just split them up in a [snip] > with django, you can have your models in any files you want. > As long as I can tell models.py is only a naming convention. > you can have a class_a.py and a class_b.py which contain the > respective classes. Yes. You can put your models within a package models in your app directory. BUT the __init__.py must import your defined models. e.g. # models/__init__.py from .abc import ModelA, ModelB from .xyz import ModelX If your models aren't in models.py or models/__init__.py django will not load your app's models If you are curious you can check the methods: get_apps, get_models, register_models, etc in the source django/db/models/loading.py Regards, Rolando -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
