Comments on: Getting Started with Django and Python – First Impressions http://blog.perplexedlabs.com/2009/02/08/getting-started-with-django-and-python-first-impressions/ web development war stories from the frontlines to the backend Fri, 12 Mar 2010 21:11:02 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: matticakes http://blog.perplexedlabs.com/2009/02/08/getting-started-with-django-and-python-first-impressions/comment-page-1/#comment-2730 matticakes Mon, 17 Aug 2009 21:04:01 +0000 http://www.perplexedlabs.com/?p=155#comment-2730 Joe,<br><br>Thanks for your comment.<br><br>views.py can go in your project root (if you have project specific views) and it can go in any apps directory (where __init__.py is) that you have in your installed apps setting.<br><br>Check your apache error_log to see why Django is crashing when you have Debug = false. Joe,

Thanks for your comment.

views.py can go in your project root (if you have project specific views) and it can go in any apps directory (where __init__.py is) that you have in your installed apps setting.

Check your apache error_log to see why Django is crashing when you have Debug = false.

]]> By: Joe Devon http://blog.perplexedlabs.com/2009/02/08/getting-started-with-django-and-python-first-impressions/comment-page-1/#comment-2729 Joe Devon Mon, 17 Aug 2009 20:52:29 +0000 http://www.perplexedlabs.com/?p=155#comment-2729 Your posts have been helpful. Still trying to figure out what directory to put that views.py in? I tried to edit it under pages, but that didn't do anything.<br><br>Also, nothing works if Debug is False, which is annoying because it's kind of a security hole. But how do you debug what's wrong when turning it on makes it work. Your posts have been helpful. Still trying to figure out what directory to put that views.py in? I tried to edit it under pages, but that didn't do anything.

Also, nothing works if Debug is False, which is annoying because it's kind of a security hole. But how do you debug what's wrong when turning it on makes it work.

]]> By: matticakes http://blog.perplexedlabs.com/2009/02/08/getting-started-with-django-and-python-first-impressions/comment-page-1/#comment-2679 matticakes Mon, 17 Aug 2009 17:04:01 +0000 http://www.perplexedlabs.com/?p=155#comment-2679 Joe,<br><br>Thanks for your comment.<br><br>views.py can go in your project root (if you have project specific views) and it can go in any apps directory (where __init__.py is) that you have in your installed apps setting.<br><br>Check your apache error_log to see why Django is crashing when you have Debug = false. Joe,

Thanks for your comment.

views.py can go in your project root (if you have project specific views) and it can go in any apps directory (where __init__.py is) that you have in your installed apps setting.

Check your apache error_log to see why Django is crashing when you have Debug = false.

]]> By: Joe Devon http://blog.perplexedlabs.com/2009/02/08/getting-started-with-django-and-python-first-impressions/comment-page-1/#comment-2678 Joe Devon Mon, 17 Aug 2009 16:52:29 +0000 http://www.perplexedlabs.com/?p=155#comment-2678 Your posts have been helpful. Still trying to figure out what directory to put that views.py in? I tried to edit it under pages, but that didn't do anything.<br><br>Also, nothing works if Debug is False, which is annoying because it's kind of a security hole. But how do you debug what's wrong when turning it on makes it work. Your posts have been helpful. Still trying to figure out what directory to put that views.py in? I tried to edit it under pages, but that didn't do anything.

Also, nothing works if Debug is False, which is annoying because it's kind of a security hole. But how do you debug what's wrong when turning it on makes it work.

]]> By: Adventures in Django and Python – Part III | Perplexed Labs http://blog.perplexedlabs.com/2009/02/08/getting-started-with-django-and-python-first-impressions/comment-page-1/#comment-2658 Adventures in Django and Python – Part III | Perplexed Labs Thu, 13 Aug 2009 14:11:05 +0000 http://www.perplexedlabs.com/?p=155#comment-2658 [...] my previous two posts on Django and Python - Part I and Part [...] [...] my previous two posts on Django and Python – Part I and Part [...]

]]> By: Django and Python First Impressions - Part II | Perplexed Labs http://blog.perplexedlabs.com/2009/02/08/getting-started-with-django-and-python-first-impressions/comment-page-1/#comment-1139 Django and Python First Impressions - Part II | Perplexed Labs Fri, 20 Mar 2009 17:37:45 +0000 http://www.perplexedlabs.com/?p=155#comment-1139 [...] spent more time with Django the past couple days. Read my installation guide and my first impressions to get caught up. I wanted to address a couple issues I came across as I was exposed to certain [...] [...] spent more time with Django the past couple days. Read my installation guide and my first impressions to get caught up. I wanted to address a couple issues I came across as I was exposed to certain [...]

]]> By: Emily Ingram » links for 2009-02-10 http://blog.perplexedlabs.com/2009/02/08/getting-started-with-django-and-python-first-impressions/comment-page-1/#comment-683 Emily Ingram » links for 2009-02-10 Tue, 10 Feb 2009 15:18:17 +0000 http://www.perplexedlabs.com/?p=155#comment-683 [...] Getting Started with Django and Python - First Impressions | Perplexed Labs (tags: django tips programming) [...] [...] Getting Started with Django and Python – First Impressions | Perplexed Labs (tags: django tips programming) [...]

]]> By: Luke Plant http://blog.perplexedlabs.com/2009/02/08/getting-started-with-django-and-python-first-impressions/comment-page-1/#comment-679 Luke Plant Mon, 09 Feb 2009 23:11:05 +0000 http://www.perplexedlabs.com/?p=155#comment-679 Doing "svn up" in a Django trunk checkout won't get you Django 1.0.2 -- you want a checkout of "branches/releases/1.0.X" for that. Django trunk is for development. That means that it is (momentarily) identical to Django 1.0.0, 1.1.0, 1.2.0 as they come into existence. But 1.0.2 etc contains bug fixes backported from trunk. Doing “svn up” in a Django trunk checkout won’t get you Django 1.0.2 — you want a checkout of “branches/releases/1.0.X” for that.

Django trunk is for development. That means that it is (momentarily) identical to Django 1.0.0, 1.1.0, 1.2.0 as they come into existence. But 1.0.2 etc contains bug fixes backported from trunk.

]]> By: Matt http://blog.perplexedlabs.com/2009/02/08/getting-started-with-django-and-python-first-impressions/comment-page-1/#comment-678 Matt Mon, 09 Feb 2009 14:31:11 +0000 http://www.perplexedlabs.com/?p=155#comment-678 Thank you for pointing that out, crossed out that portion. I was editing files directly on my server, must not have realized that they existed already. Thank you for pointing that out, crossed out that portion. I was editing files directly on my server, must not have realized that they existed already.

]]> By: Carl Meyer http://blog.perplexedlabs.com/2009/02/08/getting-started-with-django-and-python-first-impressions/comment-page-1/#comment-677 Carl Meyer Mon, 09 Feb 2009 13:32:50 +0000 http://www.perplexedlabs.com/?p=155#comment-677 Good article. I'm confused about "it was somewhat surprising to me that certain files were created automatically for you with the manage.py startapp command while others weren't (such as models.py)." manage.py startapp _does_ create both models.py (the only file an app must have) and views.py. In a trunk version of Django I believe it now also creates tests.py. You're correct about the reason for needing INSTALLED_APPS. Not only might you want to include Django contrib apps, Django is also designed to encourage you to write your own reusable apps. You can just put those in a global location on your Python path and reuse them in as many projects as you want, without copying them into each one. Django apps are _kind of_ like Rails plugins, but they include their own models, which I don't believe plugins are able to do? Been awhile, so I'm not sure on that. Good article. I’m confused about “it was somewhat surprising to me that certain files were created automatically for you with the manage.py startapp command while others weren’t (such as models.py).” manage.py startapp _does_ create both models.py (the only file an app must have) and views.py. In a trunk version of Django I believe it now also creates tests.py.

You’re correct about the reason for needing INSTALLED_APPS. Not only might you want to include Django contrib apps, Django is also designed to encourage you to write your own reusable apps. You can just put those in a global location on your Python path and reuse them in as many projects as you want, without copying them into each one.

Django apps are _kind of_ like Rails plugins, but they include their own models, which I don’t believe plugins are able to do? Been awhile, so I’m not sure on that.

]]>