On 17 May 2013 14:17, "Neal Becker" wrote:
>
> Nathaniel Smith wrote:
>
> > On 16 May 2013 19:48, "Jonathan Helmus" wrote:
> >>
> >> On 05/16/2013 01:42 PM, Neal Becker wrote:
> >> > Is there a way to get a traceback instead of just printing the
> >> > line that triggered the error?
> >> >
> >> >
Neal Becker wrote:
> Nathaniel Smith wrote:
>
>> On 16 May 2013 19:48, "Jonathan Helmus" wrote:
>>>
>>> On 05/16/2013 01:42 PM, Neal Becker wrote:
>>> > Is there a way to get a traceback instead of just printing the
>>> > line that triggered the error?
>>> >
>>> > ___
Nathaniel Smith wrote:
> On 16 May 2013 19:48, "Jonathan Helmus" wrote:
>>
>> On 05/16/2013 01:42 PM, Neal Becker wrote:
>> > Is there a way to get a traceback instead of just printing the
>> > line that triggered the error?
>> >
>> > ___
>> > NumPy-Dis
On 16 May 2013 19:48, "Jonathan Helmus" wrote:
>
> On 05/16/2013 01:42 PM, Neal Becker wrote:
> > Is there a way to get a traceback instead of just printing the
> > line that triggered the error?
> >
> > ___
> > NumPy-Discussion mailing list
> > NumPy-Di
On 05/16/2013 01:42 PM, Neal Becker wrote:
> Is there a way to get a traceback instead of just printing the
> line that triggered the error?
>
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> http://mail.scipy.org/mailman/listinfo/nump
Is there a way to get a traceback instead of just printing the
line that triggered the error?
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion