Re: python 3.x

On Thu, Sep 2, 2010 at 9:03 AM, Russell Keith-Magee wrote: ... > Effectively, this means that official support for Django under Python > 3 is still a couple of years away. Fortunately, there is plenty to do preparing for this glorious day -- many commonly-used libraries

Re: python 3.x

On Thu, Sep 2, 2010 at 9:34 PM, stefanoC wrote: > bumping an already old question, is django going to run on python > 3.x ? > > I found a few discussions talking about this, eg.   and >

python 3.x

bumping an already old question, is django going to run on python 3.x ? I found a few discussions talking about this, eg. and http://groups.google.com/group/django-developers/browse_thread/thread/f8c747a26aa5d8ed/0749bfa67b47c802 and

Re: Inline template rendering in admin shouldn't silence errors

On Thu, Sep 2, 2010 at 8:47 PM, burc...@gmail.com wrote: > On Thu, Sep 2, 2010 at 6:27 PM, Russell Keith-Magee > wrote: >> On Thu, Sep 2, 2010 at 5:04 PM, burc...@gmail.com wrote: >>> Russell, >>> >>> Sorry, we didn't understand

Re: Inline template rendering in admin shouldn't silence errors

On Thu, Sep 2, 2010 at 6:27 PM, Russell Keith-Magee wrote: > On Thu, Sep 2, 2010 at 5:04 PM, burc...@gmail.com wrote: >> Russell, >> >> Sorry, we didn't understand each other, >> >> You're talking about additional problems for templates with variable

Re: contrib/admin/validation.py

On Thu, Sep 2, 2010 at 7:43 PM, George Karpenkov wrote: > Would you accept the patch that would simply allow functions as well > as iterables? Possibly, yes. Specifically, I'd be happy with any proposal that put ModelAdmin into alignment with other parts of Django, like

Re: Inline template rendering in admin shouldn't silence errors

On Thu, Sep 2, 2010 at 7:40 PM, George Karpenkov wrote: > Dear Russ, > > I still don't quite get why "runtime template errors are > unacceptable". My understanding is that if user has DEBUG=True, and > TEMPLATE_DEBUG=True, then clearly (at least to me) the user does want

Re: Actions in popups

On Thu, Sep 2, 2010 at 7:08 PM, Simon Meers wrote: > Users regularly get confused when you present them with a raw_id popup > window which shows action checkboxes beside the list of items they are > selecting from -- they try to click the checkboxes, and wonder why the > window

Re: contrib/admin/validation.py

Would you accept the patch that would simply allow functions as well as iterables? On Sep 1, 10:35 pm, Russell Keith-Magee wrote: > On Wed, Sep 1, 2010 at 6:41 PM, Gregor Müllegger wrote: > > I ran into the same problem as George before. And it

Re: Inline template rendering in admin shouldn't silence errors

Dear Russ, I still don't quite get why "runtime template errors are unacceptable". My understanding is that if user has DEBUG=True, and TEMPLATE_DEBUG=True, then clearly (at least to me) the user does want to see all of the errors. DEBUG flags should be off in the production environment, right?

Re: Inline template rendering in admin shouldn't silence errors

On Thu, Sep 2, 2010 at 5:04 PM, burc...@gmail.com wrote: > Russell, > > Sorry, we didn't understand each other, > > You're talking about additional problems for templates with variable names. > > However main point that George made was that he wanted template > rendering to

Actions in popups

Users regularly get confused when you present them with a raw_id popup window which shows action checkboxes beside the list of items they are selecting from -- they try to click the checkboxes, and wonder why the window isn't closing. IMHO it really doesn't make much sense to be performing actions

Re: CSRF Middleware/SSL/Firefox 3.6.8 bug

On Fri, Aug 27, 2010 at 7:53 PM, Luke Plant wrote: > > Finally, the only time we need Referer headers sent is for same origin > requests (POST requests to be exact).  Sending the Referer header in > this case is virtually never a privacy concern, since the site will >

Tahoe-LAFS, Django, RAIC

Dear Tahoe-LAFS hackers, Django developers, Anders Pearson, and Jakob Pagter: I guess it is a sign that your Free Software project is succeeding when you have more users than you know that you have. Today I was reading this article about Zope vs. Django persistence strategies:

Re: Inline template rendering in admin shouldn't silence errors

Russell, Sorry, we didn't understand each other, You're talking about additional problems for templates with variable names. However main point that George made was that he wanted template rendering to break when including templates fails, no matter if that was in the parse time or rendering

Re: proposal: abstract file upload/download handling

How often should I ping, so my patch won't be forgotten? :) On Thu, Aug 19, 2010 at 9:38 AM, Jannis Leidel wrote: > Am 19.08.2010 um 01:50 schrieb Waldemar Kornewald: > >> No comments means it's still not good enough and I'll never get it >> into an acceptable shape? :) > >

Re: Inline template rendering in admin shouldn't silence errors

On Thu, Sep 2, 2010 at 2:30 PM, burc...@gmail.com wrote: > Hi Russell, > > I'd define >> {% for templ in template_list %} >>    {% include templ %} >> {% endfor %} > as a special case, for which special command or pattern should exist. > > Should it be > {% for templ in

Re: Inline template rendering in admin shouldn't silence errors

Hi Russell, I'd define > {% for templ in template_list %} >    {% include templ %} > {% endfor %} as a special case, for which special command or pattern should exist. Should it be {% for templ in template_list %} {% try-include template %} {% endfor %} or the opposite to be called {%

Re: Inline template rendering in admin shouldn't silence errors

On Thu, Sep 2, 2010 at 1:42 PM, burc...@gmail.com wrote: > Hi George, > > I believe this is a bug since any other errors in admin (not related > to inlines) don't pass silently. > > Silencing errors should always be documented, especially if error is > silenced when DEBUG is