Re: [Python-ideas] Python Reviewed

Hi Kyle, I don't see the harm caused from having a do-while construct. Not the most used construct but it is sometimes useful and not having it means you need to either have a first time through marker or a break at the end of a "while True:" loop. I would say that None should also be non-boolean. Otherwise you are saying that things which might be None would be True if not None. Re: SQLAlchemy, this does not resolve the issues satisfactorily to me. Re: half-loop. The idea that you have the same code before entry and at the end of the loop is really ugly and raises the potential for errors. I can remember doing something similarly ugly with this for looping through a cursor but I can't recall why I couldn't just do a .fetchall() and then loop through the results. Maybe I ultimately changed it to do precisely that. Perhaps you have too big a data set to load into memory all at once though and can't do it that way. Anyway, the SQL processing is all too difficult in Python and Java and nearly all modern languages. Re: Conditional expression. You could have: "<result> = if <condition> then <true-value> else <false value". Reading the actual syntax I find requires more concentration than it should. However, this means another keyword*. * General comment: I posted this because Googling didn't give me a satisfactory answer to why Python is the way that it is. I think I see it now. Guido hates keywords. I don't find this particularly logical but it is what it is and it also isn't going to change. That seems also to explain the else keyword at the end of the while loop. Anyway, I think this discussion has reached its natural conclusion here.

On 01/09/2017 09:18 PM, Simon Lovell wrote: [snip] This is not the place for this conversation. Please take it to Python List. -- ~Ethan~

I just want to point ONE thing out: On Jan 9, 2017 11:18 PM, "Simon Lovell" <simon58500@bigpond.com> wrote: * General comment: I posted this because Googling didn't give me a satisfactory answer to why Python is the way that it is. I think I see it now. Guido hates keywords. I don't find this particularly logical but it is what it is and it also isn't going to change. That seems also to explain the else keyword at the end of the while loop. No, it's because every new keyword that you add has the potential to break code that uses that as a variable name. Python is used by thousands of places across the globe right now. It would be suicidal to break half of that because someone felt the need for a new keyword. I feel like there are two things you're missing: 1. The stark majority of the "review" you made is taking about stuff that simply isn't going to change. Again, too much code to break. 2. The entirety of the "review" is your opinion. You may love the `end` keyword and enjoy using it (for some reason), but that doesn't mean it's *objectively* better. It just means it's better for you. Python is the way it is because that's the way it is, and we like it that way. _______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/ -- Ryan (ライアン) Yoko Shimomura > ryo (supercell/EGOIST) > Hiroyuki Sawano >> everyone else http://kirbyfan64.github.io/

On 01/09/2017 09:18 PM, Simon Lovell wrote: [snip] This is not the place for this conversation. Please take it to Python List. -- ~Ethan~

I just want to point ONE thing out: On Jan 9, 2017 11:18 PM, "Simon Lovell" <simon58500@bigpond.com> wrote: * General comment: I posted this because Googling didn't give me a satisfactory answer to why Python is the way that it is. I think I see it now. Guido hates keywords. I don't find this particularly logical but it is what it is and it also isn't going to change. That seems also to explain the else keyword at the end of the while loop. No, it's because every new keyword that you add has the potential to break code that uses that as a variable name. Python is used by thousands of places across the globe right now. It would be suicidal to break half of that because someone felt the need for a new keyword. I feel like there are two things you're missing: 1. The stark majority of the "review" you made is taking about stuff that simply isn't going to change. Again, too much code to break. 2. The entirety of the "review" is your opinion. You may love the `end` keyword and enjoy using it (for some reason), but that doesn't mean it's *objectively* better. It just means it's better for you. Python is the way it is because that's the way it is, and we like it that way. _______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/ -- Ryan (ライアン) Yoko Shimomura > ryo (supercell/EGOIST) > Hiroyuki Sawano >> everyone else http://kirbyfan64.github.io/
participants (4)
-
Ethan Furman
-
Rob Cliffe
-
Ryan Gonzalez
-
Simon Lovell