Talk:Cheryl's birthday: Difference between revisions
→'improve' tag on Python entry: Delegate 'idiomatic' issues to the tooling. All this code has been through AutoPep8 and Linter-flake8.
m (→Improve tag on Python entry: sp.) |
(→'improve' tag on Python entry: Delegate 'idiomatic' issues to the tooling. All this code has been through AutoPep8 and Linter-flake8.) |
||
Line 60:
Python is what it is. RC isn't the place to change it. One could try to write Haskell in Python, but that would not make it idiomatic Python. Yet? :-)
:[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 15:19, 26 October 2018 (UTC)
:: The way to handle the 'idiomatic' issue is with tooling – all of the code I have published here is checked with AutoPep8 and Linter-flake8
:: I am not trying to change anything – you are the one attempting to censor the code of others.
:: The 'Pythonic/imperative' coding style which you like was a particular optimisation for (1.) Easily accessible Python (imperative coding creates more run-time complexity and costs more debugging time, but it has a lower entry level, requiring a grasp only of sequence branching and iteration.) 2. Some private aesthetics (and one formal misapprehension) of Guido, for which he failed to establish sufficient consensus to get his own way, and which eventually contributed more to problems than to solutions, making his BDFL role unsustainable, and bringing it to an end. Python is now much larger than the initial 'easy-coding-for-all' personal project, and while the simple 'Pythonic' verities are still a useful source of consistency some contexts, they are deliberately dysfunctional in others. Functional composition has a higher entry barrier – it requires more concepts – but it yields more reliability, reduced debugging time, and greater code reuse. It is the absolutely the right way to write good Python for in some contexts, and for some users, and there is no value whatsoever in trying to shoe-horn into the residual shackles and deficiencies which Guido sought to put in the way of composing pure functions, against the grain and better judgement of the Python community as a whole. [[User:Hout|Hout]] ([[User talk:Hout|talk]]) 15:56, 26 October 2018 (UTC)
| |||