Re: Preventing the leaking of sensitive information in error logs

2011-06-02 Thread Michael Manfre
On Jun 2, 3:33 pm, Luke Plant wrote: > On 02/06/11 19:45, Michael Manfre wrote: > > On Jun 1, 5:53 am, Luke Plant wrote: > >> Would it possible to make the sensitive decorator add some kind of > >> strategy object to the request, which itself is responsible for the > >> filtering, rather than a

Re: get_object_or_404 hook

2011-06-02 Thread Vinicius Mendes
You can always create your own convenience method. Atenciosamente, Vinicius Mendes Engenheiro de Computação Globo.com On Fri, Jun 3, 2011 at 12:30 AM, Justin Holmes wrote: > For every convenience method, there are always ways to make it even more > convenient. > > I think that if the needs are

Re: get_object_or_404 hook

2011-06-02 Thread Justin Holmes
For every convenience method, there are always ways to make it even more convenient. I think that if the needs are other than the very most typical use case (ie, get_object_or_404) than a try block is indicated. On Thu, Jun 2, 2011 at 10:31 PM, waylybaye wrote: > Hi guys, how about add a hook t

get_object_or_404 hook

2011-06-02 Thread waylybaye
Hi guys, how about add a hook to get_object_or_404 to render a template with the same name of model when object does not exist ? For example: user = get_object_or_404(User, pk=pk) if the user does not exist, get_object_or_404 will try to render "404/ user.html" to show the error page other than

Re: Fixing makemessages for Javascript

2011-06-02 Thread Ned Batchelder
On 5/29/2011 5:40 AM, Jannis Leidel wrote: On 15.04.2011, at 15:25, Ned Batchelder wrote: Hi Ned, As you say, Jannis has suggested that a Babel-based solution isn't that much work. But that work hasn't been done yet. I don't know how much work it is. It's going to be a larger change to th

Re: Preventing the leaking of sensitive information in error logs

2011-06-02 Thread Julien Phalip
On Jun 1, 7:53 pm, Luke Plant wrote: > Would it possible to make the sensitive decorator add some kind of > strategy object to the request, which itself is responsible for the > filtering, rather than a simple boolean flag? The GET/POST parameters appearing in the error logs come from the HttpReq

Re: Preventing the leaking of sensitive information in error logs

2011-06-02 Thread Luke Plant
On 02/06/11 19:45, Michael Manfre wrote: > > > On Jun 1, 5:53 am, Luke Plant wrote: >> Would it possible to make the sensitive decorator add some kind of >> strategy object to the request, which itself is responsible for the >> filtering, rather than a simple boolean flag? The strategy object >>

Re: Preventing the leaking of sensitive information in error logs

2011-06-02 Thread Michael Manfre
On Jun 1, 5:53 am, Luke Plant wrote: > Would it possible to make the sensitive decorator add some kind of > strategy object to the request, which itself is responsible for the > filtering, rather than a simple boolean flag? The strategy object > interface might be: > > class ExceptionReporterFil

#15294 -- Don't use hard-coded URLs in the admin

2011-06-02 Thread Ramiro Morales
Hi all, We have a first [1]patch ready for review and feedback for this [2]ticket. It is strongly based on one Florian Apolloner had posted to ticket #13588. It's about removing as many hard-coded '../../..'-prefixed URLs in Python code and templates of the admin app as possible. Some notes and