Added tag 0.3.2 for changeset 08f6194a87ee
threadfree warning disable
I have only thread-free python installed on my M1 Macbook running macOS. But it looks like I have been testing the wrong thing, as now the whole thing compiles. My shell history doesn't have all the information ( e.g. not in which directory you execute a ccommand and since I have a lot of terminal windows open at the same time I have a whole list of cds that could apply). What is better is that ruamel.yaml.clibz compiles and works with thread-free as well, so I might just switch over to that sooner...
Maybe you missed that in my email: the code genrated with Cython 3.2.2, will not compile with Python 3.13.9t (and probably also not with 3.14.2t I did not try), so getting the sdist up to pypi is not going to solve anything.
I have a version done with Cython 3.2.2 as part of https://sourceforge.net/p/ruamel-yaml-clibz/code/ci/default/tree/_ruamelyamlclibz.c and it only slightly differs. When I tried to compile that for ruamel.yaml.clib with 3.13t on macOS it would not work and I had no time to investigate. Without that working I am not going to create all the wheels for a new version (which takes a day or so if github is spinning with their CI again) I have commited the 3.2.2 generated version to this repo. I can tag...
using Cython 3.2.2
add i686
What is going wrong here is that ruamel.yaml now indicates that for 3.14 the ruamel.yaml.clib should be installed. It used not do that only for up to and including 3.13. Since ruamel.yaml.clib is not available as .whl for the free threaded version, pip will try to build it from source. So AFAICT nothing to do with the changes for ruamel.yaml.clibz, and that is unlikely to compile for threaded without changes, without me making changes (for Cython). If you just use ruamel.yaml for it preserving format...