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 martin.panter
Recipients Claudiu.Popa, donlorenzo, martin.panter, r.david.murray, rbcollins
Date 2016-05-13.12:11:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1463141461.3.0.685222076551.issue22141@psf.upfronthosting.co.za>
In-reply-to
Content
Maybe there are two special cases colliding here:

1. complete("A.foo", 0) returns "A.foo(". But the opening bracket is in readline.get_completer_delims(), which means the completer has suggested not only a “word” but also a delimiter.

2. Perhaps Lorenz has taken "A.foo(" directly and passed it back to the completer. But as Robert said, if Readline were used, it would see the bracket as a delimiter, and only pass an empty string as the text.

The question is how should the completer behave when it gets (invalid) input that would not be possible from default Readline usage?

Lorenz: why are you passing "A.foo(" to the completer, when it only parses attribute names, and not other Python syntax such as brackets?
History
Date User Action Args
2016-05-13 12:11:01martin.pantersetrecipients: + martin.panter, rbcollins, donlorenzo, r.david.murray, Claudiu.Popa
2016-05-13 12:11:01martin.pantersetmessageid: <1463141461.3.0.685222076551.issue22141@psf.upfronthosting.co.za>
2016-05-13 12:11:01martin.panterlinkissue22141 messages
2016-05-13 12:11:01martin.pantercreate