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 Eduardo.Seabra, cdspace, rhettinger, terry.reedy
Date 2014-06-20.02:08:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1403230115.23.0.542268783726.issue21261@psf.upfronthosting.co.za>
In-reply-to
Content
String keys is what Raymond requested and what looks sensible to me. A week ago, I committed test_idle/test_hyperparser.py and an incomplete test_autocomplete.py. So we can now, for this issue, at least partly follow our standard procedure of requiring tests with patches.

I want at least a test of is_in_subscript_string(self) added to test_hyperparser. cls.code will need another line (or an existing string bracketed and the string test altered) and a new test_is_in_subscript_string added. If you are working from an installation rather that a repository, and therefore cannot write/test an addition to the new file, say so.

The change to auto-complete is trickier. I would have to look the code versus to tests to decide what to do, if anything. I might decide to improve the autocomplete htest (human test, in repository AutoComplete.py and test_idle/htest.py) rather than the unittest.

In any case, we need a signed contributor agreement to accept patches.
https://www.python.org/psf/contrib
https://www.python.org/psf/contrib/contrib-form/
History
Date User Action Args
2014-06-20 02:08:35terry.reedysetrecipients: + terry.reedy, rhettinger, Eduardo.Seabra, cdspace
2014-06-20 02:08:35terry.reedysetmessageid: <1403230115.23.0.542268783726.issue21261@psf.upfronthosting.co.za>
2014-06-20 02:08:35terry.reedylinkissue21261 messages
2014-06-20 02:08:34terry.reedycreate