Am 27.03.2020 um 21:52 schrieb Yaakov Selkowitz:
On Fri, 2020-03-27 at 18:52 +0100, Marco Atzeri wrote:
Am 26.03.2020 um 08:19 schrieb Yaakov Selkowitz:
On Thu, 2020-03-26 at 06:54 +0100, Marco Atzeri via Cygwin-apps wrote:
Am 20.03.2020 um 04:47 schrieb Yaakov Selkowitz:
I would suggest the following:
* python2-2.7.z continues to provide all '2' symlinks.
* python38 be updated to 3.8.2, and 3.8 be designated the next default
'python3' version (with the '3' symlinks continued to be kept
separate), and adjust python-wheel.cygclass accordingly.
* Similarly, a separate package (in Fedora it's called 'python-
unversioned-command') provide unversioned symlinks, pointing to 2.7 for
now (for compatibility).
* Anything currently dependent on 'python' or 'python2' should either
be dropped if no longer needed, switched to 3 is possible, otherwise
rebuilt.
* Drop 2.7 from the "default" version set in python-wheel.cygclass, and
only build those modules that are actually needed by other things by
specifying "all".
* Once that's done, look at what's still depending on /usr/bin/python
('python-unversioned-command'), and based on that decide when that can
be changed to point to python3.
HTH,
--
Yaakov
The plan looks fine. Thanks for it
unfortunately I see unexpected segfault on the testsuite
0:00:03 load avg: 1.65 [ 24/404] test_argparse -- test_applesingle skipped
0:00:11 load avg: 1.58 [ 25/404] test_array
0:00:12 load avg: 1.58 [ 26/404] test_ascii_formatd
make: *** [Makefile:878: test] Segmentation fault (core dumped)
for both 2.7.17 and your original 2.7.16.
as I saw other segfault on other programs recently
I assume that one of compiler/binutils/cygwin has some problem.
3.8.2 seems to stall later in the test, so it is another issue.
In my experience, particularly on Cygwin, the first and most common
cause of testsuite errors are in the tests themselves. While
eventually fixing these would certainly be welcome, I wouldn't block
progress thereon. How does the saying go, "don't let perfection be the
enemy of the good"?
--
Yaakov
usually I follow the same rules, but a bit of investigation
will be needed just to be sure.
Do you know a simple way to go on with the test or skip one ?
particular useful for 3.8.2
6:14:06 load avg: 0.31 running: test_subprocess (6 hour 13 min),
test_asyncio (6 hour 11 min), test_asyncore (6 hour 10 min), test_ssl (6
hour 13 min)
6:14:36 load avg: 0.30 running: test_subprocess (6 hour 13 min),
test_asyncio (6 hour 12 min), test_asyncore (6 hour 11 min), test_ssl (6
hour 14 min)
6:15:06 load avg: 0.41 running: test_subprocess (6 hour 14 min),
test_asyncio (6 hour 12 min), test_asyncore (6 hour 11 min), test_ssl (6
hour 14 min)
