Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
Sign upAny updates on Python 3 support status? Python 2 EOL is imminent. #12943
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
"From our side very little has changed since" okay but i'm interested in other viewpoints, this repository has 383 contributors |
This comment has been minimized.
This comment has been minimized.
|
I am asking if there's anything new to discuss. If there is, of course opening a ticket makes sense. But opening a ticket just because you didn't like that the other one is locked is puzzling to me. Only purpose I can see is to have a magnet for drive-by commentary like the previous ones, such as "project management is blind" or "upgrade or RIP". Such comments are precisely why the other two are locked. We don't lock tickets preemptively. People who want to raise a new point that has not been brought up before are capable of opening a new ticket themselves. I doubt this will happen though. |
untitaker
closed this
Apr 25, 2019
This comment has been minimized.
This comment has been minimized.
Ah okay, other projects allow (somtimes quiet lengthy) discussions in their Issues, where people can raise new points as a post to an existing Issue, rather than new Issues for each new view point. That's why i got confused. |
This comment has been minimized.
This comment has been minimized.
|
That's how we would like it to work as well, but in this situation we see a more pressing need for locking the threads that go out of hand. Our inboxes are already full as-is :) |
madnight commentedApr 25, 2019
It would be nice to allow an open community discussion about this (in my opinion very serious) issue and not close/silence it immediately with maintainer override forces. Thanks in advance!