Message256527
I am using Python 2.7.5. The segment of code from inspect that I previously extracted came from line 332 although you may also find it by "finding" _searchbases.
This is really an issue with Forthon:
http://hifweb.lbl.gov/Forthon/
Specifically the Forthon class, which I think is older than current standards. If you guys want this Forthon class to flag an error (I can work around that too), than the proposed fix I sent can be rejected, and this ticket can be closed. I just wanted to bring this case to you attention just in case.
Thanks again,
Brandon
Quoting "R. David Murray" <report@bugs.python.org>:
>
> R. David Murray added the comment:
>
> Which version of python are you running? I can't match that
> traceback up to the code in the current 2.7 inspect module.
>
> That said, the same issue probably exists in the current code. A 2.7
> class is expected to have either an __mro__ or a __bases__ attribute,
> and if it has neither inspect probably *should* throw an error, since
> it can't know what to do with the class. The error could be clearer,
> though.
>
> But, let's see what others think.
>
> ----------
> nosy: +r.david.murray
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue25884>
> _______________________________________
> |
|
Date |
User |
Action |
Args |
2015-12-16 17:03:24 | billyziege | set | recipients:
+ billyziege, r.david.murray |
2015-12-16 17:03:24 | billyziege | link | issue25884 messages |
2015-12-16 17:03:24 | billyziege | create | |
|