[issue16438] Numeric operator predecence confusing

2014-07-06 Thread Mark Lawrence
Mark Lawrence added the comment: I find the numeric operator predecence simply wrong, not confusing, so +1 from me for applying the attached patch from ktt3ja. It's as simple as possible but no simpler :) -- nosy: +BreamoreBoy versions: +Python 3.5 -Python 3.2, Python 3.3

[issue16438] Numeric operator predecence confusing

2012-11-27 Thread Ezio Melotti
Ezio Melotti added the comment: I'm still unable to figure out how to do it You could look at Doc/library/unittest.rst, there are some tables that span multiple lines. If you want a newline in the output too I think you have to add a blank line in the cell. --

[issue16438] Numeric operator predecence confusing

2012-11-27 Thread Kiet Tran
Kiet Tran added the comment: That document actually doesn't have any table that spans multiple lines. Here's the html page: http://docs.python.org/dev/library/unittest.html Actually, I already know how to make a table span multiple lines from this stackoverflow page:

[issue16438] Numeric operator predecence confusing

2012-11-22 Thread Kiet Tran
Kiet Tran added the comment: Good idea. -- keywords: +patch Added file: http://bugs.python.org/file28075/16438.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16438 ___

[issue16438] Numeric operator predecence confusing

2012-11-21 Thread Kiet Tran
Kiet Tran added the comment: I was trying to fix this, but I ran into a couple questions. 1) Once I put, say, x + y and x - y into the same table cell, what would a good format be? My preferred format is to have them on separate lines in the cell, but after a lot of googling on the syntax of

[issue16438] Numeric operator predecence confusing

2012-11-21 Thread Yongzhi Pan
Yongzhi Pan added the comment: One possible solution: We do not list priorities of the operations, instead link to the precedence table in the language reference. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16438

[issue16438] Numeric operator predecence confusing

2012-11-08 Thread Yongzhi Pan
New submission from Yongzhi Pan: http://docs.python.org/3/library/stdtypes.html#numeric-types-int-float-complex All numeric types (except complex) support the following operations, sorted by ascending priority. It list '-' after '+', '/' after '*'. That is to mean '-' has higher precedence

[issue16438] Numeric operator predecence confusing

2012-11-08 Thread Jesús Cea Avión
Jesús Cea Avión added the comment: Precedence ordered per row. Same row, same precedence. I don't see any problem. It is natural math precedence. Closed as invalid. -- nosy: +jcea resolution: - invalid ___ Python tracker rep...@bugs.python.org

[issue16438] Numeric operator predecence confusing

2012-11-08 Thread Mark Dickinson
Changes by Mark Dickinson dicki...@gmail.com: -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16438 ___ ___

[issue16438] Numeric operator predecence confusing

2012-11-08 Thread Yongzhi Pan
Yongzhi Pan added the comment: I mean the text at the first link need fix. '+' and '-' are not on the same row. And the doc says: sorted by ascending priority, that means they have ascending priority. The table in the reference is just right. --

[issue16438] Numeric operator predecence confusing

2012-11-08 Thread Jesús Cea Avión
Jesús Cea Avión added the comment: You are right, Yongzhi Pan. Reopening. Not sure how to solve it. Delegating to docs@python. -- resolution: invalid - status: closed - open ___ Python tracker rep...@bugs.python.org

[issue16438] Numeric operator predecence confusing

2012-11-08 Thread Meador Inge
Changes by Meador Inge mead...@gmail.com: -- nosy: +meador.inge ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16438 ___ ___ Python-bugs-list

[issue16438] Numeric operator predecence confusing

2012-11-08 Thread Ezio Melotti
Changes by Ezio Melotti ezio.melo...@gmail.com: -- keywords: +easy nosy: +ezio.melotti stage: - needs patch type: - enhancement ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16438 ___