51–60 of 115 posts
Earlier quoted context omitted.
Sorry, I mean that the volunteer maintainer of the latexmk package in Debian hasn't updated it since 2015. Arch probably has a newer version from the latexmk authors (and I think Arch does not have the same culture of individual package maintainers, in general).
The Debian LaTeX maintainer was essentially harassed out of the project by the Anti-Harassment Team.
Just rip the band-aid off. Some of the async stuff in Python 3 is awesome. A bit curious that 3.4 has been dropped, as that's the stock Python 3 shipped for CentOS 7.
> Just rip the band-aid off. Some of the async stuff in Python 3 is awesome. Will that awesome async stuff help us migrate several 100s of thousands of lines of 2.7 code?
Just rip the band-aid off. Some of the async stuff in Python 3 is awesome. A bit curious that 3.4 has been dropped, as that's the stock Python 3 shipped for CentOS 7.
> Just rip the band-aid off. Some of the async stuff in Python 3 is awesome. Will that awesome async stuff help us migrate several 100s of thousands of lines of 2.7 code?
Earlier quoted context omitted.
EDIT: My comment is grossly misunderstood and I cannot delete my comment. I did not imply python 3 causes bad code, I was trying to tell a story about how "our" python 2 code is handsome and python 3 code is ugly; sorta implying python2 is not necessarily legacy code. I have absolutely no problem with python 3 and prefer it over python 2. I do not want to start a 2 vs 3 flamewar please just ignore this comment. === M…
If your Python 2 code is clean and your Python 3 is ugly, I don't know what the hell you are doing. They are almost the same language. Are you trolling?
Earlier quoted context omitted.
> Just rip the band-aid off. Some of the async stuff in Python 3 is awesome. Will that awesome async stuff help us migrate several 100s of thousands of lines of 2.7 code?
What percentage of those lines do you estimate will need changes?
Earlier quoted context omitted.
> Just rip the band-aid off. Some of the async stuff in Python 3 is awesome. Will that awesome async stuff help us migrate several 100s of thousands of lines of 2.7 code?
What percentage of those lines do you estimate will need changes?
You'd need insane test coverage, of all possible code paths, to be 100% confident.
Earlier quoted context omitted.
The code I've written recently relies heavily on async and data classes, both of which are recent additions. I can't imagine choosing Python 2 at this point.
Same here. Dataclasses and type annotations are fantastic, not to mention f-strings.