This is done for several reasons:
- Recent CPython versions such as 3.13 have mostly caught up
with Pyston in terms of performance. If the trend continues,
CPython may supersede Pyston's performance in the long term.
This is especially the case if the experimental JIT is
eventually able to run Godot's SCons setup.
- Pyston is not maintained anymore (its last release was in 2022),
and the last Python version it can run is 3.8. Python 3.8 is now
end-of-life. Godot's SCons setup (as well as SCons itself) will
eventually require Python versions newer than 3.8.
* Ubuntu APT oneliner to install system builtin alternatives
Might work on Debian, not sure - tested on Ubuntu 24.04 LTS
* Use new table syntax (easier to maintain), add Debian
---------
Co-authored-by: Hugo Locurcio <hugo.locurcio@hugo.pro>
- List Wayland dependency and packages on most distributions.
- Use `sudo` on distributions that are set up to use it by default.
- Use unattended install-friendly commands (e.g. `-y` switch).
- Mention required commands to run before installing, such as
`apt-get update`.
- Fix install commands on some distributions:
- Alpine no longer packages libexecinfo since 3.17, so it was removed
from the list.
- Solus requires `-c` for `system.devel`.
- Reorder distributions so they're in alphabetical order.
The document suggests copy `/usr/lib/libatomic_ops.a` to
`/usr/lib/libatomic.a`. Instead of copying, using a soft link to
libatomic_ops is also an option. The reason to soft link is also added.
I have successfully built Godot by using soft link.
Since there is no "3.x " branch of the docs, I'm not sure which branch the link should point to instead. I went with the latest 3.x, but maybe 3.0 is better?
The Introduction to the buildsystem page still mentions this parameter
in case it needs to be changed, but in most situations, the default
value of `(number of CPU threads) - 1` does a good job.
- Merge Community/Contributing and Engine Development into one top-level section, Contributing.
- Structure it in a way that gives equal priority to various ways to contribute, including documentation.
- Rename several articles to be more comprehensive and in line with the overall state of the documentation.
- Rewrite the guide for class reference contributions.
