Re: render_to_response fails with TemplateSyntaxError: too many values to unpack

On Wed, Aug 19, 2009 at 8:30 AM, Janne Peltola wrote: > > Template rendering fails when both form data and a tuple are passed to > render_to_response. > > Python: 2.6.2; Django: 1.1; Environment: Windows + built-in dev server > > I use the standard

Re: How much memory does a django instance need was Does Hostmonster support Django?

> did all this - I am still getting around 35 MB per instance. And it > is not the fault of webfaction. The same site on my local machine > gives the same figure. This on the latest svn in both cases. The last > time I looked at these figures, it was around 12-15mb an instance. > Any

Re: url tag difficulties

> No. This one's a case or pilot error. If you want to use this form, you > must write it as: > > url(r'^$', 'index', name="blog-index") > > url() is a function call, so you can pass it named arguments. The (...) > form (without a leading "url") is a Python tuple and you can't use >

Re: url tag difficulties

> hello, > > I am learning a lot from the B-List blog > Here is an entry, which could be interesting for > you:http://www.b-list.org/weblog/2007/nov/06/urlconf/ > (specially the named URL patterns) Thanks Bernd, I'd seen that before, and decided I wouldn't mess with it if I couldn't get the

url tag difficulties

I really hope this isn't embarrassingly obvious but... My {% url %} tags aren't producing anything -- no error and no url. My current setup is so bare-bones I can't imagine what's gone wrong. Here are the basics: ROOT_URLCONF = Project.urls In Project.urls: (r'^$', 'app1.views.index'),

Re: webhostingbuzz, anyone tried

I'm also on webfaction, and like it. The most basic plan is pretty skimpy on server RAM (simply enabling debug on my site put it over the limit, and I was the only one accessing it), but you'll be fine if you take a bit of care with the setup. Django works straight out of the box, and their

Re: Anyone running mod_python for Python 2.5 on Mac OS X?

Whoops, sorry, ignore that last... On Nov 1, 10:16 am, [EMAIL PROTECTED] wrote: > Ulf, did you ever figure this out? I don't use pgsql/psycopg, but I've > had the same issues with mod_python and competing framework/MacPort > installations of Python. And I didn't even know there was a >

Re: the old django-in-a-subdirectory problem

> for what its worth, here is part of the httpd.conf file (smedia is > where the uploaded media is put, if you want to serve it from the > main apache, you *must* put it in ./webapps/ directory): One last question then I'll let this drop: Kenneth you mention putting things directly into your

Re: the old django-in-a-subdirectory problem

Thanks, Kenneth and Karen... > Wrong order, you won't need the 500.html (nearly as much) once all the bugs > are worked out, many of which you will find while getting the front page to > work! :) Ha! Understood. > So, I think you can fix it by including the trailing slash in all your links >

Re: the old django-in-a-subdirectory problem

http://taojian.webfactional.com/django/InnerWorks/ works fine from here, try once more? > I get back a 500 status code (and you really need to create a 500.html > template, btw). I'm saving all that for after I've got the front page working properly :)

Re: the old django-in-a-subdirectory problem

> You haven't really provided enough details for me, at least, to know > what you're doing here. Thanks very much for taking the time to look at this, the whole thing has been very frustrating... Part of the problem may come from the fact I'm hosting this on WebFaction, and in their control

Re: the old django-in-a-subdirectory problem

On Oct 31, 6:20 am, Graham Dumpleton <[EMAIL PROTECTED]> wrote: > On Oct 31, 1:15 am, [EMAIL PROTECTED] wrote: > If you use mod_wsgi, it contains instructions for how to mount > application on a sub url rather than at root. To make it all work > requires doing a workaround in the WSGI wrapper

the old django-in-a-subdirectory problem

This issue has come up for many people in many places, but most of the threads seem old, and none of the solutions proposed has helped. I have a django installation in a subdirectory of a site, like so: www.mysite.com/django. At first I noticed a problem with the admin login, like other people

Re: static images with built-in django server

Me too, I can't get this to work and it's driving me crazy. My main problem seems to be that Django is looking inside the Django site package within my Python framework for the media (when I try to load an image directly, for instance, it tells me "Page not found: /Library/