** Changed in: pylint (Ubuntu)
Status: Confirmed => Invalid
** Changed in: pylint
Importance: Unknown => Undecided
** Changed in: pylint
Status: Unknown => New
** Changed in: pylint
Remote watch: www.logilab.org/ #19641 => None
** Changed in: pylint
Importance: Undecided =>
** Tags added: 15.10 python
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/456870
Title:
pylint spews Exception RuntimeError: maximum recursion depth exceeded
while calling a Python object
To mana
Is this still a bug that needs fixing?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/456870
Title:
pylint spews Exception RuntimeError: maximum recursion depth exceeded
while calling a Python obje
** Changed in: pylint (Ubuntu)
Status: New => Confirmed
** Changed in: pylint
Importance: Undecided => Unknown
** Changed in: pylint
Status: New => Unknown
** Changed in: pylint
Remote watch: None => www.logilab.org/ #19641
** Bug watch added: www.logilab.org/ #19641
http:/
Yes. But I just checked the error message and it's not exactly the same
:
File
"/usr/local/lib/python2.6/dist-packages/logilab_astng-0.19.3-py2.6.egg/logilab/astng/_nodes.py",
line 117, in root
return self.parent.root()
File
"/usr/local/lib/python2.6/dist-packages/logilab_astng-0.19.3-p
huum, I've no time to check this. I'll reopen the ticket if this is
confirmed.
does panda3d use some C-compiled extensions?
--
pylint spews Exception RuntimeError: maximum recursion depth exceeded while
calling a Python object
https://bugs.launchpad.net/bugs/456870
You received this bug notific
Unfortunately it's not solving the issue with Panda3D :/ I still have the
maximum recursion depth
For more info, see the second comment made by sthenault in this topic :
http://www.logilab.org/ticket/19641
--
pylint spews Exception RuntimeError: maximum recursion depth exceeded while
calling a
I've checked in that patch to upstream repository, thank you guys
--
pylint spews Exception RuntimeError: maximum recursion depth exceeded while
calling a Python object
https://bugs.launchpad.net/bugs/456870
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
> Thanks EKR.
You're welcome. Tracking down this bug was fun.
> Myself, I think the code really does intend to use a different
variable __proxied but the call to hasattr() causes recursion. I just
changed it as follows:
def _set_proxied(const):
return _CONST_PROXY[const.value.__class__]
Th
Thanks EKR. We've been getting the same thing with 2.6.4 on linux on all our
code.
I tried your change, but got an exception elsewhere whose traceback ended at
for infered in callee.infer_call_result(self, callcontext):
File "/usr/local/lib/python2.6/site-packages/logilab/astng/infutil
The following hack seems to repair the damage. Change:
def _set_proxied(const):
if not hasattr(const, '__proxied'):
const.__proxied = _CONST_PROXY[const.value.__class__]
return const.__proxied
To:
def _set_proxied(const):
const._proxied = _CONST_PROXY[const.value.__class__]
The failing code appears to be _set_proxied in inference.py.
def _set_proxied(const):
if not hasattr(const, '__proxied'):
const.__proxied = _CONST_PROXY[const.value.__class__]
return const.__proxied
nodes.Const._proxied = property(_set_proxied)
The call to hasattr can call Proxy
I can now demonstrate exactly where the unbound recursion happens.
The following is a debugger that warns me when the stack gets too big. It is a
subclass of pdb, but it overrides two methods in bdb.py. Here it is::
class debugger(pdb.Pdb):
def __init__(self,completekey='tab',stdin=None
** Summary changed:
- pylint spews Exception RuntimeError: maximum recursion depth exceeded while
calling a Python object, when parsing email.message.Message.get()
+ pylint spews Exception RuntimeError: maximum recursion depth exceeded while
calling a Python object
--
pylint spews Exception Ru
Here's the bug report i was referring to:
http://www.logilab.org/ticket/19641
--
pylint spews Exception RuntimeError: maximum recursion depth exceeded while
calling a Python object, when parsing email.message.Message.get()
https://bugs.launchpad.net/bugs/456870
You received this bug notificatio
I tried to add my findings to that bug report, but despite having logged
in at logilab, their bug report page keeps presenting me with the
"register or log in message". How frustrating. If anyone from the
pylint/astng projects is reading, could you please add to that bug
report the slightly diffe
More information here:
http://lists.logilab.org/pipermail/python-
projects/2009-December/002124.html
--
pylint spews Exception RuntimeError: maximum recursion depth exceeded while
calling a Python object, when parsing email.message.Message.get()
https://bugs.launchpad.net/bugs/456870
You receiv
I installed pylint 0.19 (from ubuntu lucid packages) and it is still
spewing repeated copies of that error message. It no longer does it
with the test program I included in my first comment, but it does with
plenty of others. I'm attaching a different program that triggers the
misbehavior.
** At
I get this on all my files on Windows as well:
pylint 0.19.0,
astng 0.19.3, common 0.46.0
Python 2.6.4 (r264:75708, Oct 26 2009, 08:23:19) [MSC v.1500 32 bit (Intel)]
I do not believe pylint is working as well as it should. It is missing
serious errors, for example, undefined methods.
--
pylin
I'm getting this error in Gentoo with these versions:
pylint-0.19.0
astng-0.19.3
python-2.6.4
Pylint still seems to work fine, but this error is a little annoying.
--
pylint spews Exception RuntimeError: maximum recursion depth exceeded while
calling a Python object, when parsing email.message
If the simplest solution is to upgrade, can we upgrade the version in
the repositories?
--
pylint spews Exception RuntimeError: maximum recursion depth exceeded while
calling a Python object, when parsing email.message.Message.get()
https://bugs.launchpad.net/bugs/456870
You received this bug no
I am getting this problem with all files of my Leo sources on Ubuntu
9.10 Karmic
pylint 0.18.0, (latest available package)
astng 0.19.0, common 0.39.0
Python 2.6.4 (r264:75706, Dec 7 2009, 18:45:15)
[GCC 4.4.1]
For example, from Leo's bzr repository: (the top-level directory):
pylint leo/core/
Hi,
I cannot reproduce this bug with an up-to-date version of pylint and
astng. Simplest way to fix it is to upgrade.
Btw, easiest way of communicating with pylint maintainers is to
subscribe to the mailing list (http://lists.logilab.org/mailman/listinfo
/python-projects) and send a mail to pytho
I tried to submit a bug report on logilab.org, but I don't see a way to do so.
http://www.logilab.org/857
--
pylint spews Exception RuntimeError: maximum recursion depth exceeded while
calling a Python object, when parsing email.message.Message.get()
https://bugs.launchpad.net/bugs/456870
You re
24 matches
Mail list logo
