Changes between Version 4 and Version 5 of Python3


Ignore:
Timestamp:
04/09/2024 12:59:24 AM (6 months ago)
Author:
ken@…
Comment:

Tests for 3.11.9 now complete for me. Thanks for the fix.

Legend:

Unmodified
Added
Removed
Modified
  • Python3

    v4 v5  
    77However, if there is a new release of the same minor version (e.g. 3.12 to 3.12.1) you can just upgrade that and the existing modules should continue to work. Although current 3.10 is in 'bugfix' status, several of the previous series are still receiving security fixes (back to 3.8 in August 2023), see [https://www.python.org/downloads/source/]
    88
    9 WARNING: On two LFS-12.0 machines where I have tried to update to Python-3.11.9 the builds stalled in different ways. Putting the output in a log to avoid cluttering the screen, nothing show apart from a few lines at the start about missing dependencies (_tkinter, nis). On one machine I interrupted the build with Ctrl-C and found it had run all the 483 initial tests, with some errors, and had then spent 1hr 28. On the other, 453 tests were ok then some messages about the interrupt. For a non-pythonista the reason for the stall was not clear, but the log ended
    10 {{{
    11 2 re-run tests:
    12     test_embed test_threading
     9Although previous updates seemed to complete without problems, some people have been seeing hangs in the tests for a long time, and that hit me (ken) on two
     10machines with 3.11.9 where 3.11.8 was OK. LFS now has an added 'timeout' parameter (check the LFS development books) which works well.
    1311
    14 2 tests failed:
    15     test_embed test_threading
    1612
    17 453 tests OK.
    18 
    19 Test suite interrupted by signal SIGINT.
    20 
    21 Total duration: 2 hour 26 sec
    22 Total tests: run=40,186 failures=4 skipped=1,225
    23 Total test files: run=480/483 failed=2 skipped=23 resource_denied=3 rerun=2
    24 Result: FAILURE, INTERRUPTED then FAILURE, INTERRUPTED
    25 }}}
    26 
    27 Clearly, it would have kept on hanging if I had not killed it.
    28 
    29 This is supposed to include a vulnerability which was fixed in 3.10.14 in March.
    30