On 16 février 02:07, Edward K. Ream wrote:
> QQQ
> I haven't seen any updates on the "maximum recursion depth exceeded" bug
> recently. Any word on whether the developers have reproduced it or when it
> might be fixed?
>
> It's still broken in pylint 0.19.0 and logilab-astng 0.19.3 with python
>
On 16 février 02:07, Edward K. Ream wrote:
Hi,
> QQQ
> I haven't seen any updates on the "maximum recursion depth exceeded" bug
> recently. Any word on whether the developers have reproduced it or when it
> might be fixed?
>
> It's still broken in pylint 0.19.0 and logilab-astng 0.19.3 with pyt
QQQ
I haven't seen any updates on the "maximum recursion depth exceeded" bug
recently. Any word on whether the developers have reproduced it or when it
might be fixed?
It's still broken in pylint 0.19.0 and logilab-astng 0.19.3 with python
2.6.4.
http://www.logilab.org/ticket/19641
https://bugs
I haven't seen any updates on the "maximum recursion depth exceeded" bug
recently. Any word on whether the developers have reproduced it or when it
might be fixed?
It's still broken in pylint 0.19.0 and logilab-astng 0.19.3 with python
2.6.4.
http://www.logilab.org/ticket/19641
https://bugs.lau
On 16 décembre 08:45, Barry Warsaw wrote:
> On Dec 15, 2009, at 09:03 PM, Daniel Harding wrote:
>
> >This past June problems were reported with seeing messages like the
> >following on stderr when running pylint:
> >
> > Exception RuntimeError: 'maximum recursion depth exceeded while
> >
On Dec 15, 2009, at 09:03 PM, Daniel Harding wrote:
>This past June problems were reported with seeing messages like the
>following on stderr when running pylint:
>
> Exception RuntimeError: 'maximum recursion depth exceeded while
> calling a Python object' in
> ignored
>
>At the tim
This past June problems were reported with seeing messages like the
following on stderr when running pylint:
Exception RuntimeError: 'maximum recursion depth exceeded while
calling a Python object' in
ignored
At the time it was attributed to a bug in Python 2.6.2. However, after
