msg151985 - (view) |
Author: Boštjan Mejak (Retro) |
Date: 2012-01-25 23:58 |
When you have time, incorporate this patch. Thanks.
|
msg152110 - (view) |
Author: Sandro Tosi (sandro.tosi) * |
Date: 2012-01-27 18:43 |
There are a lot more occurrences of 'floating point' in our doc: are you going to fix them too?
|
msg152262 - (view) |
Author: Boštjan Mejak (Retro) |
Date: 2012-01-29 21:34 |
If "floating point" in a sentence is in a role of an adjective, then it must be written as "floating-point" (with a hyphen), otherwise not.
Example: "The number 3.5 is a floating-point number."
Please consult some English orthography book and start writing correct English.
|
msg152287 - (view) |
Author: Sandro Tosi (sandro.tosi) * |
Date: 2012-01-29 23:32 |
Wow.. do you really expect any positive outcome from you reply style?
I'll pretend I didn't read your reply and let me rephrase my question like this: there are several occurrences of 'floating point' in python doc, are you going to fix all the ones that are wrong?
|
msg152318 - (view) |
Author: Boštjan Mejak (Retro) |
Date: 2012-01-30 14:08 |
I know that there are a lot of non-hyphenated occurences of "floating point" in Python docs, so I just want to raise awareness about those occurences. Can you fix all occurences of "floating point" (when in a role of an adjective) to "floating-point" throughout Python docs?
As a matter of fact, everything that is an adjective is hyphenated if there are 2 words that form the adjective.
Example: "This is built in." versus "This is a built-in method."
|
msg152319 - (view) |
Author: Sandro Tosi (sandro.tosi) * |
Date: 2012-01-30 14:15 |
On Mon, Jan 30, 2012 at 15:08, Boštjan Mejak <report@bugs.python.org> wrote:
> Can you fix all occurences of "floating point" (when in a role of an adjective) to "floating-point" throughout Python docs?
What I was asking is if *you* (since you care about the topic) would
provide a patch fixing all that needs fixing. At that point there will
be people interesting reviewing your patch, instead of people been
told what to do.
Regards,
Sandro
|
msg152321 - (view) |
Author: Stefan Krah (skrah) * |
Date: 2012-01-30 14:24 |
Congratulations: You (again) have found a fundamental error in TAOCP.
Example (Third Edition, page 233):
"The following definitions seem to be appropriate for base b, excess q,
floating point numbers ..."
|
msg152324 - (view) |
Author: Boštjan Mejak (Retro) |
Date: 2012-01-30 15:14 |
For the time being I don't find any other "floating point" occurences in Python docs. I found one and made a patch for it. Please apply the patch. Thanks.
|
msg152347 - (view) |
Author: Georg Brandl (georg.brandl) * |
Date: 2012-01-30 21:09 |
Wow, does that mean he can cash in a Knuth check?
|
msg152382 - (view) |
Author: Boštjan Mejak (Retro) |
Date: 2012-01-31 13:03 |
What's the purpose of this tracker if the author of an issue report has to beg for something to be fixed, despite the fact that (s)he even made a patch ?????
|
msg152407 - (view) |
Author: Stefan Krah (skrah) * |
Date: 2012-01-31 21:28 |
Georg Brandl <report@bugs.python.org> wrote:
> Wow, does that mean he can cash in a Knuth check?
Two already: One for the insight that "i-th" is the only true spelling,
and now this one.
|
msg152431 - (view) |
Author: Boštjan Mejak (Retro) |
Date: 2012-02-01 14:42 |
Message has been classified as spam.
|
msg152432 - (view) |
Author: Sandro Tosi (sandro.tosi) * |
Date: 2012-02-01 14:45 |
On Wed, Feb 1, 2012 at 15:42, Boštjan Mejak <report@bugs.python.org> wrote:
> Seriously, how old are you two clowns?
I think it's enough: FTR I'm +1 on removing Retro tracker account,
effective immediately (if any admin is around).
|
msg152434 - (view) |
Author: Boštjan Mejak (Retro) |
Date: 2012-02-01 14:59 |
Message has been classified as spam.
|
msg152437 - (view) |
Author: Antoine Pitrou (pitrou) * |
Date: 2012-02-01 15:21 |
Retro, your contributions are not welcome anymore.
|
msg152454 - (view) |
Author: Raymond Hettinger (rhettinger) * |
Date: 2012-02-02 05:40 |
Boštjan, please stop wasting everyone's time.
|
|
Date |
User |
Action |
Args |
2022-04-11 14:57:26 | admin | set | github: 58076 |
2012-02-02 05:40:17 | rhettinger | set | nosy:
+ rhettinger messages:
+ msg152454
|
2012-02-01 19:37:28 | georg.brandl | set | status: open -> closed resolution: not a bug |
2012-02-01 15:21:58 | pitrou | set | nosy:
+ pitrou messages:
+ msg152437
|
2012-02-01 14:59:57 | Retro | set | messages:
+ msg152434 |
2012-02-01 14:45:14 | sandro.tosi | set | messages:
+ msg152432 |
2012-02-01 14:42:16 | Retro | set | messages:
+ msg152431 |
2012-01-31 21:28:44 | skrah | set | messages:
+ msg152407 |
2012-01-31 13:03:31 | Retro | set | messages:
+ msg152382 |
2012-01-30 21:09:17 | georg.brandl | set | nosy:
+ georg.brandl messages:
+ msg152347
|
2012-01-30 15:14:25 | Retro | set | messages:
+ msg152324 |
2012-01-30 14:24:09 | skrah | set | nosy:
+ skrah messages:
+ msg152321
|
2012-01-30 14:15:07 | sandro.tosi | set | messages:
+ msg152319 |
2012-01-30 14:08:08 | Retro | set | messages:
+ msg152318 |
2012-01-29 23:32:23 | sandro.tosi | set | messages:
+ msg152287 |
2012-01-29 21:34:37 | Retro | set | messages:
+ msg152262 |
2012-01-27 19:34:16 | mark.dickinson | set | nosy:
+ mark.dickinson
|
2012-01-27 18:43:28 | sandro.tosi | set | nosy:
+ sandro.tosi messages:
+ msg152110
|
2012-01-25 23:58:10 | Retro | create | |