[issue41266] IDLE call hints and completions confused by ints and floats

2022-01-31 Thread Terry J. Reedy
Terry J. Reedy added the comment: There are 1000s of open python issues and perhaps 200 for IDLE. I consider this one to be lower priority that enough others to fill my IDLE time. -- stage: -> test needed versions: +Python 3.11 -Python 3.10, Python 3.8, Python 3.9

[issue41266] IDLE call hints and completions confused by ints and floats

2022-01-31 Thread wyz23x2
wyz23x2 added the comment: Ping, this issue is 571 days old. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue41266] IDLE call hints and completions confused by ints and floats

2021-09-22 Thread Terry J. Reedy
Terry J. Reedy added the comment: What is your point? Code without explanation is useless. -- ___ Python tracker ___ ___

[issue41266] IDLE call hints and completions confused by ints and floats

2021-09-21 Thread wyz23x2
wyz23x2 added the comment: Ping. >>> from datetime import datetime as d >>> d(2021, 9, 22)-d(2020, 7, 10) datetime.timedelta(days=439) -- ___ Python tracker ___

[issue41266] IDLE call hints and completions confused by ints and floats

2020-07-11 Thread Terry J. Reedy
Terry J. Reedy added the comment: Neither '1 .bit_length()' (space required) nor '1.3.hex()', both legal syntax, get either proper completions or call hints. Neither does the erroneous syntax '1.bit_length'. This suggests that the backwards parsing from the final '.' could be improved.