IDLE - autocompletion logic optimization

[taleinat]

BPO	2062
Nosy	@kbkaiser, @taleinat
Files	IDLE_AutoComplete_complete_string_optimization.080211.patch: second version IDLE_AutoComplete_complete_string_optimization.080214.patch: thrid version, after fixing a bug and doing some testing

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = 'https://github.com/kbkaiser'
closed_at = <Date 2008-04-27.21:38:34.681>
created_at = <Date 2008-02-10.23:36:53.022>
labels = ['expert-IDLE', 'type-bug']
title = 'IDLE - autocompletion logic optimization'
updated_at = <Date 2008-04-27.21:38:34.645>
user = 'https://github.com/taleinat'

bugs.python.org fields:

activity = <Date 2008-04-27.21:38:34.645>
actor = 'kbk'
assignee = 'kbk'
closed = True
closed_date = <Date 2008-04-27.21:38:34.681>
closer = 'kbk'
components = ['IDLE']
creation = <Date 2008-02-10.23:36:53.022>
creator = 'taleinat'
dependencies = []
files = ['9403', '9426']
hgrepos = []
issue_num = 2062
keywords = ['patch']
message_count = 8.0
messages = ['62265', '62266', '62269', '62286', '62296', '62297', '62371', '65904']
nosy_count = 2.0
nosy_names = ['kbk', 'taleinat']
pr_nums = []
priority = 'normal'
resolution = 'accepted'
stage = None
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue2062'
versions = ['Python 2.6']

[taleinat]

Improve the code in AutoCompleteWindow._complete_string to be more
efficient.

(this is to be followed up by a more extensive patch, which builds on
this change to support case-insensitive completion)

[taleinat]

Found two more instances in the code where a similar improvement can be
made. This (second) version of the patch is more consistent, please use
it instead of the initial version.

[kbkaiser]

I would greatly appreciate it if you would slow down and test your
patches and use them for an extended period of time (preferably with
some other people trying them) before submitting them. It's quite
aggravating to start working on one, and even have it checked in, only
to have to start over again. It doubles the work and makes me
unwilling to address your patches. How much time have you given the
second version?

[taleinat]

Well, I admit, I haven't tested this enough. Specifically, there is a
bug in this patch (both versions); please delete it.

I accept your criticism of my latest patches, they truly are of inferior
quality. I deeply apologize for having taken up more of your time than I
should have.

Allow me to explain my situation:

I work with a highly modified version of IDLE to which I have added many
features, and which is also used daily by ~10 friends and colleagues.
Many of these patches are my attempt to contribute the more mature and
successful changes/features back to CPython. However, the completion
code differs greatly from the CPython version, making porting changes a
large effort, requiring me to re-implement many things, as well as go
once more through the process of testing and debugging.

This is really a great deal of work and I have been eager to contribute
some of the better features. While I have tried to be methodical,
thorough and test everything, I seem to still have been too hasty. I
must tell you that I spent many hours preparing the last few patches,
but I realize that doing half a job is worse than not doing it at all.

In the future I will test every change much more thoroughly before
posting it as a patch.

[kbkaiser]

I agree that testing GUI apps is problematic, especially if you are
working with an intermediate version which isn't being used heavily.
Besides code review, you essentially have to run at least a subset of an
user-conducted acceptance test which tries to explore the corner cases
and generally monkey test the app. It seems the best way beyond that is
to use the new version of IDLE to develop code for awhile; that usually
exposes at least the superficial problems. I don't have an issues with
correcting minor bugs, but I expect the corrective patch to be small.
We have one going on CallTips which has become problematic for several
reasons, and I'll comment on it at msg59009.

Unless a person wants to fork, he has to make a deliberate effort to
stay close to the main line of development. That can mean forgoing
things that would be 'nice to have' or non-essential refactorings. It's
a problem with distributed VCS that divergence is encouraged. I think
you see the problem!

Are the differences in your autocomplete code significant functional
differences, or can we bring our versions into alignment at some point?
Please take into account the comments I'm going to make at msg59009
regarding 2.6/3.0 compatibility.

I really do appreciate your interest in IDLE and the work you are doing
to make it better. I think you understand my interest in keeping it
minimal and intuitive. It doesn't have to be like all the rest and
continually accrete features which are of limited use to the target
audience, especially at the cost of reliability and performance.

[kbkaiser]

That should be 'bpo-1350'!

[taleinat]

After fixing the aforementioned bug and testing as thoroughly as I can,
here is a revised patch.

[kbkaiser]

r62548