tauthon

roject you like, but you still need to stick follow trademark law. You can't just release Linux 2.7 because you disagree with breaking changes in 3.0 either, but you're free to take the Linux code and release Twonux if you really care.

even use the language myself. I'm just observing.) It's a real shame Tauthon didn't get more traction and support. https://github.com/naftaliharris/tauthon If it had got enough support and continued, maybe the Python maintainers would have learned something, but I've not seen any sign that they have. This is nothing new. For comparison, Perl 6 went so badly that Perl 5 now looks likely to continue as Perl 7: https://www.perl.com/article/announcing-perl-7/ And PHP 6 didn't really happen -- AFAICT as a total outsider, Unicode support proved too hard and it was never released; the community backported the important bits to PHP 5, and then a new PHP 7, more modest in scope, developed from PHP 5. The Python world could have done the same, and Tauthon was an effort in that direction. It's too late now. I suspect that, just as Perl has lost a massive amount of interest and use, partly from the nearly-two-decade-long effort to release Perl 5, Python has done the same -- sabotaged its own community with this high-handed "your leaders know best" approach.

> that be acceptable? When you're in a community or a space, actions that are unintentionally hostile towards that community or space, can be seen as intentionally hostile by the members, and if you only hear about it second-hand, or you spend a lot of time around the group, that belief can be reinforced through the discussions and gripes the group has about it(1). (0): https://github.com/naftaliharris/tauthon/issues/47 (1): That's not to say there aren't bona fide intentionally hostile actions that happen, but rather that's how actions that aren't intended to be hostile can be remembered and percieved as such.