On Oct 27, 2009, at 6:09 PM, Tim Chase wrote:
> >> There's quite a learning curve here. > > The learning curve doesn't have much to do with Django, but > rather development in general -- any time you take on a new > technology (or soup of technologies, in this case Python/HTML/CSS > Django's templating language, and possibly SQL) there's a hill to > climb, but this one's pretty gentle -- in fact the most gentle > learning curve of all the frameworks I've toyed with. I've not done any python before so I'm struggling with infrastructure concepts. Where do I put my code that isn't necessarily model types? Ditto for cross application model relationships (if any). I looked at pinax and the major obstacle to adoption is the virtualenv thing. I tried the setup script and it wants to install its own python stack and everything else. I just want to use the modules, I already got a python stack built (on Snow Leopard - no it hasn't been fun rebuilding every blessed open source lib I ever downloaded for binary compatibility). And then the best practices of django. I don't know any of the tools yet, but I've got a web app to build and I've judged django has more pre-built parts I need than anything else so here we go. -Todd --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
