Re: Problems running testsuite on Windows with Python 3

Earlier, in the thread "schedule for 1.14.0 release"...

On Wed, Apr 22, 2020 at 8:15 AM Johan Corveleyn <jcorvel_at_gmail.com> wrote:
> In fact, there is very little pressure on getting this in 1.14.0 GA,
> because (1) it only affects testsuite-runners on Windows, of which
> there are extremely few :-), and (2) the workaround is simple (just
> use Py 2.7 for running the testsuite on Windows). Not worth taking
> risks for IMHO.
>
> The only actual "damage" is perhaps marketing. Now we can't claim
> "Full Py3 support" in big letters, we need to add a footnote pointing
> to a known issues section in the release notes or something ...

I'd like to add something along these lines to the Release Notes,
under "Known Issues in the Release."

Please check for accuracy:

(I haven't tested this myself -- haven't reached this point yet in my
Windows setup!)

[[[

When using Python 3.6 or higher on Windows, the test suite fails to
run because of changes in Python's implementation of console I/O.

Several workarounds are available:

Either:

* Use Python 2.7, or Python 3.5 or below, or

* Run the test suite with the --log-to-stdout command line argument,
  or

* Set the PYTHONLEGACYWINDOWSSTDIO environment variable before running
  the test suite, or

* Apply r1876707 and r[insert number here] and run the test suite.

This problem is (expected to be) fixed in 1.14.1.

]]]

Where "insert number here" would be Yasuhito's latest patch.

Nathan
Received on 2020-04-22 15:19:08 CEST