How to take on a large Django project
1–10 of 21 posts
Re: How to take on a large Django project
#2I still find the project/app distinction in Django pretty confusing. I wish there were just the app standalone, and some way to join apps together if you really need to.
Re: How to take on a large Django project
#3I still find the project/app distinction in Django pretty confusing. I wish there were just the app standalone, and some way to join apps together if you really need to.
Think of it like this: The project is your final product, comprised of separate functions from each app. The Project is really the glue holding your apps together.
Re: How to take on a large Django project
#4I still find the project/app distinction in Django pretty confusing. I wish there were just the app standalone, and some way to join apps together if you really need to.
Think of it like this: The project is your final product, comprised of separate functions from each app. The Project is really the glue holding your apps together.
[deleted]
Re: How to take on a large Django project
#5I still find the project/app distinction in Django pretty confusing. I wish there were just the app standalone, and some way to join apps together if you really need to.
I just put everything in an app called 'core'. That seems to be pretty normal.
Anything non-core obviously goes in a separate app, and usually if the project grows large enough there will be parts where it makes sense to break it apart.
Re: How to take on a large Django project
#6I still find the project/app distinction in Django pretty confusing. I wish there were just the app standalone, and some way to join apps together if you really need to.
I just put everything in an app called 'core'. That seems to be pretty normal. Anything non-core obviously goes in a separate app, and usually if the project grows large enough there will be parts where it makes sense to break it apart.
I like this idea. Can you give us an example of something that wouldn't go in core?
Re: How to take on a large Django project
#7On the same subject, I just finished uploading video of a talk given to the Django Boston Meetup Group on Wednesday night -- "Staying Sane While Taking Over An Existing Django Codebase" by Matt Makai:
Re: How to take on a large Django project
#8On the same subject, I just finished uploading video of a talk given to the Django Boston Meetup Group on Wednesday night -- "Staying Sane While Taking Over An Existing Django Codebase" by Matt Makai: http://www.youtube.com/watch?v=psCVC9BdgsA
nice! i'll check it out later
Re: How to take on a large Django project
#9Earlier quoted context omitted.
I just put everything in an app called 'core'. That seems to be pretty normal. Anything non-core obviously goes in a separate app, and usually if the project grows large enough there will be parts where it makes sense to break it apart.
I like this idea. Can you give us an example of something that wouldn't go in core?
anything reusable that you can package as an external utility (and would upload to pypi if it weren't for IP restrictions).
Re: How to take on a large Django project
#10> Pssst! Hackers, sign up here!
just tried to register at gun.io. it doesn't want my email from github auth, then asks for email on their site anyway, but the form doesn't work.