[issue8686] "This isn't defined beyond that" phrase is not friendly to non-native English speakers.

2010-10-17 Thread Georg Brandl
Georg Brandl added the comment: Removed gloss in r85610. -- nosy: +georg.brandl resolution: -> fixed status: open -> closed ___ Python tracker ___ __

[issue8686] "This isn't defined beyond that" phrase is not friendly to non-native English speakers.

2010-05-14 Thread Tim Peters
Tim Peters added the comment: Terry asks: > is it also guaranteed that quick_ratio() <= real_quick_ratio() Nope! The docs don't say that, so it's not guaranteed. It's not the _intent_ of the code that it be true, either. The only point to quick_ratio() and real_quick_ratio() is speed. ---

[issue8686] "This isn't defined beyond that" phrase is not friendly to non-native English speakers.

2010-05-14 Thread Terry J. Reedy
Terry J. Reedy added the comment: I agree with Tim. Drop the zero-info glosses. For real_quick_ratio(), "Return an upper bound on ratio() even more quickly." should be sufficient (assuming that it *is* always quicker. Just curious, The descriptions say ratio() <= quick_ratio() and ratio() <

[issue8686] "This isn't defined beyond that" phrase is not friendly to non-native English speakers.

2010-05-12 Thread Tim Peters
Tim Peters added the comment: I find this whole discussion to be hilarious ;-) "Approximate upper bound" is gibberish - "upper bound" is a crisp concept that means what it says. It's not necessarily true that an upper bound is inaccurate - it may be exactly right. So "this is not as accurat

[issue8686] "This isn't defined beyond that" phrase is not friendly to non-native English speakers.

2010-05-12 Thread Martin v . Löwis
Martin v. Löwis added the comment: I think it's important to note that this may err towards larger numbers (rather than being merely inaccurate). I also find this "an upper bound on ratio()" difficult to understand. IIUC, it is the correct value being bounded, not the result of the function u

[issue8686] "This isn't defined beyond that" phrase is not friendly to non-native English speakers.

2010-05-12 Thread A.M. Kuchling
A.M. Kuchling added the comment: How about just dropping those words entirely, and writing "Return an approximate upper bound on ratio() very quickly. This is not as accurate as ratio(), but is faster to compute." (We'd make similar changes to real_quick_ratio()'s text.) -- nosy: +

[issue8686] "This isn't defined beyond that" phrase is not friendly to non-native English speakers.

2010-05-11 Thread R. David Murray
Changes by R. David Murray : -- versions: +Python 3.1 -Python 3.3 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue8686] "This isn't defined beyond that" phrase is not friendly to non-native English speakers.

2010-05-11 Thread R. David Murray
R. David Murray added the comment: Unfortunately that wouldn't be correct English, as far as I know. How about "This isn't defined other than that..." I think that reads a bit more clearly than "beyond that" even to a native speaker, even though beyond is valid in this context. -- n

[issue8686] "This isn't defined beyond that" phrase is not friendly to non-native English speakers.

2010-05-11 Thread INADA Naoki
New submission from INADA Naoki : http://docs.python.org/library/difflib.html#difflib.SequenceMatcher.quick_ratio > This isn’t defined beyond that it is an upper bound on ratio(), and is faster > to compute. "beyond" is a bit confusing because it also means "over" and this sentence refers upper