Strange error in IDLE

Samuel Schulenburg samschul at pacbell.net
Fri May 17 13:01:29 EDT 2002


shagshag13 at yahoo.fr (Shagshag) wrote in message news:<409a56e2.0205170241.5e5bba2e at posting.google.com>...
> Well i do that :
> 
> ----
> 
> Python 2.2.1 (#34, Apr  9 2002, 19:34:33) [MSC 32 bit (Intel)] on win32
> Type "copyright", "credits" or "license" for more information.
> IDLE 0.8 -- press F1 for help
> >>> def get_openingTag(node):
>     """
>     """
>     global SPECIALS_CHARS
>     #if node.nodeType == node.ELEMENT_NODE:
>     tmp = node.toxml()
>     tmp = remove_chars(tmp, SPECIALS_CHARS)
>     opening_tag = tmp[:tmp.index('>')] + '>'
>     return opening_tag
> 
> ----
> 
> then press return type "get_openingTag("
> 
> and then it do that before i go further :
> 
> ----
> 
> >>> Exception in Tkinter callback
> Traceback (most recent call last):
>   File "D:\Python22\lib\lib-tk\Tkinter.py", line 1292, in __call__
>     return apply(self.func, args)
>   File "D:\PYTHON22\Tools\idle\CallTips.py", line 51, in paren_open_event
>     arg_text = get_arg_text(self.get_object_at_cursor())
>   File "D:\PYTHON22\Tools\idle\CallTips.py", line 148, in get_arg_text
>     while doc[:1] in " \t\n":
> TypeError: 'in <string>' requires character as left operand
> 
> ----
> 
> think there is a bug, no ???

The callTips routine is correctly reporting that you have not inserted
a string within the Documentation string. I do not understand why you
would want to create a null string for documentation.

Sam Schulenburg



More information about the Python-list mailing list