This addresses the "small caveat" issue mentioned on #7531 that
affects all python versions, by making sure that both site.py's
and sysconfig.py's copies of _getuserbase() have the same code.
Also: renamed the package to be consistent with the rest of the
Python versions.
This addresses the "small caveat" issue mentioned on #7531 that
affects all python versions, by making sure that both site.py's
and sysconfig.py's copies of _getuserbase() have the same code.
This addresses the "small caveat" issue mentioned on #7531 that
affects all python versions, by making sure that both site.py's
and sysconfig.py's copies of _getuserbase() have the same code.
This addresses the "small caveat" issue mentioned on #7531 that
affects all python versions, by making sure that both site.py's
and sysconfig.py's copies of _getuserbase() have the same code.
The so version is the same as in 8.6.12 therefore the recipe was just renamed.
OpenCASCADE's DRAW still runs.
Tests don't run successfully. Some tests hang, and one test even crashes with an assertion in free.
This commit also clears out older recipes from the recipe directory.
There is no need to keep them: stable rust itself is fully backward
compatible with older code in almost all cases, and it is unlikely
that someone will ever want/need to build an older compiler.
* python310: bump revision to 3.10.8.
* Use "make altinstall".
* Documented problematic tests, and skipped the ones that hang/stall.
* Enable optimizations.
* Added a note regarding tests that invoke the crash dialog.
Running "hp --test python310" now gives the same results[*] for both
non-optimized, and optimized builds, so let's just enable
optimizations for 3.10.8.
[*] As there's some randomness involved in the test runs, YMMV.
Anecdotal/aditional info:
Building and testing with "--disable-test-modules" might be
considered? Python's docs read:
"The test package is meant for internal use by Python only."
And that those are used for regression testing mostly. See:
https://docs.python.org/3/library/test.html#module-test
Personal experience: I got more consistent results with that flag
enabled, than witout it. I left it out, trying to avoid hiding
problems (a.k.a.: failing silently. A big NO-NO in QA/QC), and
because I assume that packaging Python counts as "internal use".
* python310: patch tests that need several GB of storage.
They now behave like on Windows or MacOSX, requiring to be enabled
by the use of the "largefile" resource usage flag.
* python3.10: rename package from python310 to python3.10.
This matches the rename of python3 to python3.7, and the similar
change for Python 3.9.
Renamed patchset files to match the recipe naming.
Sorted sections according to the Haikuporter Guidelines.
Also: build with "--with-readline=editline", which enables line-editting,
history, and tab-completion on the interactive interpreter prompt.
Closes#7183.
