2 ms·
The fork comment is not meant to be a realistic suggestion, it just points out that there is work needed to maintain compatibility. The thing is, you can't both
by pyrale 6y ago
The fork comment is not meant to be a realistic suggestion, it just points out that there is work needed to maintain compatibility. The thing is, you can't both complain about the time it takes to migrate your project _and_ expect maintainers to spend an incommensurate amount of time maintaining suff for you, free of charge.
I understand that some people and companies are now caught between a rock and a hard place right now. But honestly, that rock has been coming for 12 years now, and the alternative is to put other people in that situation.
- Chris2048 6y agoSure, but the assumption is py3 devs do the work in order to dismiss the idea and suggest people are entitled. py3 devs don't need to do the work, they just need to hand it off. > The thing is, you can't both.. Yes you can, if "maintaining" is handing it off, as opposed to the straw man of forcing py3 devs to do it. Why do the gatekeepers only allow for themselves to do the work? > that rock has been coming for 12 years notice is not consent. > the alternative is to put other people in that situation 12 years is enough time to hand off to people who are happy to maintain py2. But there was no choice given.