Re:PEP 492 – Coroutines with async and await syntax
by justifier on Saturday April 18, 2015 @04:55PM
(#9400985)
disclaimer.. i understand the strengths of 2.x, but i use and prefer 3
my standing question in the debate has always been what is the big deal with having built a robust 2to3 preprocessor?
i figure if you make a change to the spec migrating existing code to the new syntax should be a pretty straight forward ifttt, something that should be a necessary addition to the change, a la tests
knowing full well 'pretty straight forward' is the bane of all software endeavors could anyone explain to me what is going on within the scope of 2to3 preprocessors?
and why such preprocessors seem an impossible boon very few, except a handful of seeming independants, endeavor
my standing question in the debate has always been what is the big deal with having built a robust 2to3 preprocessor?
i figure if you make a change to the spec migrating existing code to the new syntax should be a pretty straight forward ifttt, something that should be a necessary addition to the change, a la tests
knowing full well 'pretty straight forward' is the bane of all software endeavors could anyone explain to me what is going on within the scope of 2to3 preprocessors?
and why such preprocessors seem an impossible boon very few, except a handful of seeming independants, endeavor