[issue34112] 3.7.0 build error with --enable-optimizations

2018-07-15 Thread Jayanth Koushik
Jayanth Koushik added the comment: Updating gcc to 8.1.0 fixed the problem. -- resolution: -> works for me stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue34112] 3.7.0 build error with --enable-optimizations

2018-07-14 Thread Jayanth Koushik
Jayanth Koushik added the comment: Hi. Do you mean turning of `--enable-optimizations` or reducing GCC optimization level (O3 etc)? -- ___ Python tracker <https://bugs.python.org/issue34

[issue34112] 3.7.0 build error with --enable-optimizations

2018-07-14 Thread Jayanth Koushik
New submission from Jayanth Koushik : I'm trying to build 3.7.0 locally (not as superuser) on a server. I am able to successfully build without `--enable-optimizations` enabled, but the build fails with it enabled. I have dependencies installed in custom locations as well, and this is my

[issue22243] Documentation on try statement incorrectly implies target of except clause can be any assignable expression

2014-08-23 Thread Jayanth Koushik
Jayanth Koushik added the comment: Oh ok. That makes sense. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22243 ___ ___ Python-bugs-list

[issue22243] Documentation on try statement incorrectly implies target of except clause can be any assignable expression

2014-08-22 Thread Jayanth Koushik
Jayanth Koushik added the comment: The whole page on compound statements seems to be rife with inconsistencies. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22243

[issue22243] Documentation on try statement incorrectly implies target of except clause can be any assignable expression

2014-08-22 Thread Jayanth Koushik
Jayanth Koushik added the comment: The page on compound statements defines compound statements as: compound_stmt ::= if_stmt | while_stmt | for_stmt | try_stmt | with_stmt | funcdef

[issue22243] Documentation on try statement incorrectly implies target of except clause can be any assignable expression

2014-08-21 Thread Jayanth Koushik
Jayanth Koushik added the comment: Yes. Seems to be a documentation error. The full grammar specification [1] uses 'NAME' instead of 'target'. [1]: https://docs.python.org/3/reference/grammar.html -- nosy: +jayanthkoushik type: - enhancement

[issue21510] fma documentation should provide better example.

2014-05-15 Thread Jayanth Koushik
Jayanth Koushik added the comment: @Mark: I agree. And perhaps it is also worth mentioning (on an unrelated note), that the decimal fma is not based on the internal cmath fma (it could not be) and unlike the cmath fma, it is no faster than an unfused multiply-add

[issue21510] fma documentation should provide better example.

2014-05-14 Thread Jayanth Koushik
New submission from Jayanth Koushik: The documentation for decimal.fma provides an example which fails to illustrate the most important feature of the function i.e. single rounding. In fact: Decimal(2).fma(3, 5) == Decimal(2)*3 + 5 An example such as this would make it much more clear

[issue21380] timezone support in strftime methods broken

2014-04-30 Thread Jayanth Koushik
Jayanth Koushik added the comment: This is not an issue with strftime. By default, datetime and time objects are 'navie' and they do not contain timezone info. Nor does the datetime module provide any tzinfo classes of its own. You would need to write a class derived from tzinfo and specify

[issue21232] Use of '1' instead of 'True' as 'splitlines' argument in difflib documentation

2014-04-15 Thread Jayanth Koushik
Changes by Jayanth Koushik jnkous...@gmail.com: -- assignee: docs@python components: Documentation nosy: docs@python, jayanthkoushik priority: normal severity: normal status: open title: Use of '1' instead of 'True' as 'splitlines' argument in difflib documentation type: enhancement

[issue21232] Use of '1' instead of 'True' as 'splitlines' argument in difflib documentation

2014-04-15 Thread Jayanth Koushik
New submission from Jayanth Koushik: In the difflib documentation, multiple uses of 'splitlines' use '1' as the 'keepends' argument. In Python 2.x, 1 is not guaranteed to be True and while this is guaranteed in 3.x, it would be much clearer to specify the argument as 'True