The Python community is heavily pushing to get Python 2 out of normal use,
so the only reason I can imagine of trying to maintain Python 2
compatibility is if people have written scripts atop GHC's test suites. I
sort of doubt that's common.
ᐧ
On Wed, Nov 30, 2016 at 2:46 PM, Ben Gamari
Hello everyone,
Note that yesterday I flipped the switch in the build system to use the Python 3 interpreter by default when invoking the testsuite driver. The motivation for this is the fact that Python 2.7 is quite buggy on Windows, which resulted in spurious testsuite failures (see #12554).
The question remains, however, of how much we care to preserve compatibility with Python 2. From what little I've seen so far I think it would be easier for everyone involved if we just let Python 2 pass into the sunset. Afterall, Python 3 is no less available than 2 at this point. Thoughts?
Cheers,
- Ben
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs