This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients taleinat, terry.reedy
Date 2014-06-14.21:41:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The current behavior is documented, if not exactly 'chosen' as the best possible. "return the indices of the opening bracket and the closing bracket (or the end of line, whichever comes first". 

As you note, the automatic matching when pausing afte typing a closer only needs to search back, and that should not be affected. When I type ^0, I am willing to wait the extra 1/20? of a second to get a proper highlight.

To see if anything might depend on the truncated search, I grepped

Searching 'get_surrounding_brackets' in C:\Programs\Python34\Lib\idlelib\*.py ... 66:         sur_paren = hp.get_surrounding_brackets('(') 105:     def get_surrounding_brackets(self, openers='([{', mustclose=False): 93:         indices = HyperParser(self.editwin, "insert").get_surrounding_brackets() 109:         indices = hp.get_surrounding_brackets(_openers[closer], True)

So we have to make sure that calltips are not disabled or burdened. (The 'testing' you said is needed.)

I don't understand the call because the goal is to find the expression preceding '('. There usually is no matching ')' after '(' just typed.  I just know that unless unless evalfuncs is True, calltips are not fetched when the function expression contains a function call. 'f(' gives a calltip for f, but 'f()(' does not call f to give a calltip for f().
Date User Action Args
2014-06-14 21:41:57terry.reedysetrecipients: + terry.reedy, taleinat
2014-06-14 21:41:57terry.reedysetmessageid: <>
2014-06-14 21:41:57terry.reedylinkissue21756 messages
2014-06-14 21:41:56terry.reedycreate