On Monday, June 18, 2018 at 2:48:58 PM UTC-5, Ian wrote: > I would also note that none of this applies to type hinting > in any case. Type hints don't require the programmer to be > able to explain anything in natural language, nor are they > prone to becoming out-of-sync. > > Because if they do, then then the type analyzer will > complain the very next time you run it. So if you're trying > to make the case for type hints being treated like > comments, this isn't it.
My point is perfectly clear to anyone who bothers to read it in its entirety. I have asked time and time again for someone to directly justify why py-dev won't offer a tool to remove the interleaved type-hint syntax from scripts. And yet, this whole thread has been a giant cascade of distractions from that one, simple, question. It is obvious to the impartial reader what is going on here. There is a systematic campaign of brow beating underway to punish those who do not blindly accept the validity of type- hints. And any wavering from the the official party line will be subject to retributions. That is not behavior of a community. A community would care for the opinions of all members. I have made my sacrifice, by agreeing that i will accept the inclusion of type-hints even though i find the whole concept the be a violation of Python's core principles. All i ask in return is that the py-devs make a sacrifice of their own, by releasing a tool to remove these type-hints error free. And then those of us who are offended by type-hints will have no reason to complain. And wouldn't that be nice? Wouldn't it be nice to actually have a sense of community again. Wouldn't it be nice to compromise instead of squabble? -- https://mail.python.org/mailman/listinfo/python-list
