This ticket might be a part of what you're looking for:
https://code.djangoproject.com/ticket/11834
It proposes to dim the django parts of the stacktrace, so the code
which most likely caused the error stands out better, which is
certainly something I'd love to see.
There's some similar ideas
Hi,
I'm writing docs for a patch (#8348), and wondering how to indicate
that that feature is only available in the development version. This
used to be:
**New in Django development version**
but now I think it should be:
.. versionadded:: dev
however a grep can't find either of the above
Very helpful information from Karen and Russell, thanks. I have
written it up for the Contributing section of the FAQ:
http://code.djangoproject.com/ticket/10110
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
2009/1/7 Malcolm Tredinnick :
>
> I'm also thinking that requiring evidence of people walking across hot
> coals in order to use an application is probably a good pre-requisite
> for inclusion in django.contrib.
>
+1
The gmail ads are conveniently offering me 'Firewalk
I'm +1 on this. An exception should only appear on the console if
something serious is broken.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to
'warnings' sounds like a subset of 'logging'.
In a similar thread (about template tags and filters failing
silently) two years ago Simon Willison (who started this thread) said:
"We really need an official Django logging framework so stuff like
this can be logged"
this to publish our staging site to our
live site. It makes loadata act like a 'syncdata' command.
I hope this is useful to more than just me, and very much welcome
feedback on it.
Best regards,
Graham King
--~--~-~--~~~---~--~~
You received this message because you
Adrian Holovaty wrote:
> On 1/22/07, Istvan Albert <[EMAIL PROTECTED]> wrote:
>> There is an easy way to turn on multi-threading for the default server,
>> see the diff below:
>
> Graham and/or anybody else who wants multi-threading in the
> development server, can you try this patch and see
I have also run up against the 1 connection limit on the dev server.
Particularly I was trying to get the server to make a connection to
itself to cache the output HTML of a template, so as to serve it as a
static file.
+1 for anything that makes the dev server multi-threaded. I'm
Adrian Holovaty wrote:
> On 12/7/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>> Yes, something along the lines of the wizard control in ASP.NET.
>> Ideally, nothing is committed to the db unless all the pages in the
>> wizard are validated. Whether this is done by capturing the
>>
Dear django-devs,
If you have thousands of entries in a multiple select box in the
Django admin interface, the Javascript in SelectBox.js which makes the
nice gui widget, runs too slowly, and the browser will complain.
We have re-written SelectBox.js (attached or at
comechao,
What would be the advantage over mod_python in Apache ?
Graham.
comechao wrote:
> Why not create a server like mongrel for Django?
>
>
> >
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Ville Säävuori wrote:
>> I miss the "Week In Review" blog posts from Adrian but surely he's not
>> writting those to have more time for coding :)
>
> Yeah, me too! It's very nice to read something "digested" about ongoing
> deveploment (from an insider) because following all trac changes and
>
Dear django-developers,
At the moment django.core.mail does not set a Message-ID header in the
mails it sends. SpamAssassin spots this and says INVALID_MSGID and /or
MSGID_NO_HOST. I think the Message-ID is also used for message
threading, and matters when you have clustered mail
NE == 'mysql':
value = value.replace(microsecond=0)
it works fine.
Am I missing something ?
Thanks in advance,
Graham King.
15 matches
Mail list logo