On 23/11/10 20:48, Markus Barth wrote:
> I am using quite a lot of asynchronous calls for updating a page. The
> problem is that this way you never see a traceback. In turbogears the
> development server prints all tracebacks to the terminal. Is there any
> way to get a similar behaviour with
On 11/23/2010 09:48 PM, Markus Barth wrote:
I am using quite a lot of asynchronous calls for updating a page. The
problem is that this way you never see a traceback. In turbogears the
development server prints all tracebacks to the terminal. Is there any
way to get a similar behaviour with
On 23 nov, 23:33, Markus Barth wrote:
> On 23 nov, 23:19, Javier Guerra Giraldez wrote:
>
> > On Tue, Nov 23, 2010 at 3:48 PM, Markus Barth
>
> > wrote:
> > > I am using quite a lot of asynchronous calls for
On 23 nov, 23:19, Javier Guerra Giraldez wrote:
> On Tue, Nov 23, 2010 at 3:48 PM, Markus Barth
>
> wrote:
> > I am using quite a lot of asynchronous calls for updating a page. The
> > problem is that this way you never see a traceback. In
I have just found a post from beginning of last year pointing out that
this feature got "lost" during the transition from 0.9 to 1.0. I have
digged a bit through the code but must admit that fixing this
definitely should be done by someone who is familiar with django
internals.
Tracebacks are one
On Tue, Nov 23, 2010 at 3:48 PM, Markus Barth
wrote:
> I am using quite a lot of asynchronous calls for updating a page. The
> problem is that this way you never see a traceback. In turbogears the
> development server prints all tracebacks to the terminal. Is there
I am using quite a lot of asynchronous calls for updating a page. The
problem is that this way you never see a traceback. In turbogears the
development server prints all tracebacks to the terminal. Is there any
way to get a similar behaviour with django?
--
You received this message because you
7 matches
Mail list logo