Christopher Barker writes:
On Sat, Nov 13, 2021 at 12:01 AM Stephen J. Turnbull
What I think would make a difference is a six-like tool for making "easy changes" like substituting aliases and maybe marking other stuff that requires human brains to make the right changes.
I think a “2to3” like or “futurize” like tool is a better idea, but yes.
That's what I meant, thanks for the correction.
The real challenge with the 2-3 transition was that many of us needed to keep the same code base running on both 2 and 3. But do we need to support running the same code on 3.5 to 3.10?
Need? No. Want to not raise a big middle finger to our users? Yes. Speaking for GNU Mailman (and I think I can do that in this case without getting lynched by the rest of our crew). I wouldn't mind if the tool gently suggests, ''' hey, folks, you can't really support both 3.5 AND 3.10 without a lot of "if hasattr(foo, 'frob')", so maybe you can drop support for 3.5? ''', though.
I’m confused — did you mean “sometimes cause dangerous behavior”? That’s pretty rare isn’t it?
FVO of "often" == "yeah, I've heard enough stories that I worry about it", I mean "often". We're talking about risk assessments, and I work with Internet-facing code, where there are no risks, just certain disasters at an uncertain but near-future date. ;-) Steve