Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Change defaults to be consistent with original defaults and REPL perf… #10999
Happy to hear feedback on why whatever is currently going on is better but seems like generally it is best to not dramatically change the defaults. . is one of the most important operations in python (IPython) from a human perspective so everyone is quite sensitive about this stuff.
Case-insensitivity break tab-completion in the case when there is one case-sensitive choice but several case-insensitive choices. Would be interesting to consider second to be case insensitive or something like that. Then you don't break that UX on the first tab completion.
Thanks, merging. We may want to refine this further (e.g. falling back to case-insensitive search when we find no matches), but it sounds like this will be an improvement for most users.
That's always a dangerous thing to say. If there are people who don't like this change, they won't be complaining yet.