Add ARM64 Windows builds for Python 3.11+ #387

zanieb · 2024-10-30T02:31:08Z

Picking up #93

zanieb · 2024-10-30T15:06:56Z

We're failing missing applink.c:


cpython>     38>ClCompile:
cpython>          C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Tools\MSVC\14.41.34120\bin\HostX64\arm64\CL.exe /c /I"C:\Users\RUNNER~1\AppData\Local\Temp\python-build-3k85bya8\openssl\arm64\include" /I"C:\Users\runneradmin\AppData\Local\Temp\python-build-3k85bya8\Python-3.13.0\Include" /I"C:\Users\runneradmin\AppData\Local\Temp\python-build-3k85bya8\Python-3.13.0\Include\internal" /I"C:\Users\runneradmin\AppData\Local\Temp\python-build-3k85bya8\Python-3.13.0\Include\internal\mimalloc" /I"C:\Users\RUNNER~1\AppData\Local\Temp\python-build-3k85bya8\Python-3.13.0\PCbuild\obj\\313arm64_PGInstrument\pythoncore\\" /I"C:\Users\runneradmin\AppData\Local\Temp\python-build-3k85bya8\Python-3.13.0\PC" /Zi /nologo /W3 /WX- /diagnostics:column /MP /O2 /Oi /Oy- /GL /D _CRT_SECURE_NO_WARNINGS /GF /Gm- /MD /GS /Gy /fp:precise /Zc:wchar_t /Zc:forScope /Zc:inline /Fo"C:\Users\RUNNER~1\AppData\Local\Temp\python-build-3k85bya8\Python-3.13.0\PCbuild\obj\313arm64_PGInstrument\_ssl\\" /Fd"C:\Users\RUNNER~1\AppData\Local\Temp\python-build-3k85bya8\Python-3.13.0\PCbuild\obj\313arm64_PGInstrument\_ssl\vc143.pdb" /external:W3 /Gd /TC /analyze- /FC /errorReport:queue /utf-8 "C:\Users\RUNNER~1\AppData\Local\Temp\python-build-3k85bya8\openssl\arm64\include\openssl\applink.c"
cpython>          applink.c
cpython>     38>C:\Users\RUNNER~1\AppData\Local\Temp\python-build-3k85bya8\openssl\arm64\include\openssl\applink.c(1,1): error C1083: Cannot open source file: 'C:\Users\RUNNER~1\AppData\Local\Temp\python-build-3k85bya8\openssl\arm64\include\openssl\applink.c': No such file or directory [C:\Users\RUNNER~1\AppData\Local\Temp\python-build-3k85bya8\Python-3.13.0\PCbuild\_ssl.vcxproj]
cpython>          (compiling source file '../../../../../../../RUNNER~1/AppData/Local/Temp/python-build-3k85bya8/openssl/arm64/include/openssl/applink.c')

on amd64, you can see we copy this file

openssl> *** Installing runtime libraries
openssl> created directory `C:/Users/RUNNER~1/AppData/Local/Temp/openssl-build-upok1jaj/x64/install'
openssl> created directory `C:/Users/RUNNER~1/AppData/Local/Temp/openssl-build-upok1jaj/x64/install/64'
openssl> created directory `C:/Users/RUNNER~1/AppData/Local/Temp/openssl-build-upok1jaj/x64/install/64/bin'
openssl> Copying: libcrypto-1_1-x64.dll to C:/Users/RUNNER~1/AppData/Local/Temp/openssl-build-upok1jaj/x64/install/64/bin/libcrypto-1_1-x64.dll
openssl> Copying: libssl-1_1-x64.dll to C:/Users/RUNNER~1/AppData/Local/Temp/openssl-build-upok1jaj/x64/install/64/bin/libssl-1_1-x64.dll
openssl> Copying: libcrypto-1_1-x64.pdb to C:/Users/RUNNER~1/AppData/Local/Temp/openssl-build-upok1jaj/x64/install/64/bin/libcrypto-1_1-x64.pdb
openssl> Copying: libssl-1_1-x64.pdb to C:/Users/RUNNER~1/AppData/Local/Temp/openssl-build-upok1jaj/x64/install/64/bin/libssl-1_1-x64.pdb
openssl> *** Installing development files
openssl> created directory `C:/Users/RUNNER~1/AppData/Local/Temp/openssl-build-upok1jaj/x64/install/64/include'
openssl> created directory `C:/Users/RUNNER~1/AppData/Local/Temp/openssl-build-upok1jaj/x64/install/64/include/openssl'
openssl> Copying: ./ms/applink.c to C:/Users/RUNNER~1/AppData/Local/Temp/openssl-build-upok1jaj/x64/install/64/include/openssl/applink.c

but we don't on arm64

2024-10-30T14:25:05.2679998Z openssl> *** Installing runtime libraries
2024-10-30T14:25:05.2957214Z openssl> created directory `C:/Users/RUNNER~1/AppData/Local/Temp/openssl-build-hynbk0h3/arm64/install'
2024-10-30T14:25:05.2959360Z openssl> created directory `C:/Users/RUNNER~1/AppData/Local/Temp/openssl-build-hynbk0h3/arm64/install/arm64'
2024-10-30T14:25:05.2961110Z openssl> created directory `C:/Users/RUNNER~1/AppData/Local/Temp/openssl-build-hynbk0h3/arm64/install/arm64/bin'
2024-10-30T14:25:05.3572257Z openssl> Copying: libcrypto-3-arm64.dll to C:/Users/RUNNER~1/AppData/Local/Temp/openssl-build-hynbk0h3/arm64/install/arm64/bin/libcrypto-3-arm64.dll
2024-10-30T14:25:05.3574146Z openssl> Copying: libssl-3-arm64.dll to C:/Users/RUNNER~1/AppData/Local/Temp/openssl-build-hynbk0h3/arm64/install/arm64/bin/libssl-3-arm64.dll
2024-10-30T14:25:05.4293375Z openssl> Copying: libcrypto-3-arm64.pdb to C:/Users/RUNNER~1/AppData/Local/Temp/openssl-build-hynbk0h3/arm64/install/arm64/bin/libcrypto-3-arm64.pdb
2024-10-30T14:25:05.4295870Z openssl> Copying: libssl-3-arm64.pdb to C:/Users/RUNNER~1/AppData/Local/Temp/openssl-build-hynbk0h3/arm64/install/arm64/bin/libssl-3-arm64.pdb
2024-10-30T14:25:05.4709900Z openssl> *** Installing development files
2024-10-30T14:25:05.4964299Z openssl> created directory `C:/Users/RUNNER~1/AppData/Local/Temp/openssl-build-hynbk0h3/arm64/install/arm64/include'
2024-10-30T14:25:05.4966851Z openssl> created directory `C:/Users/RUNNER~1/AppData/Local/Temp/openssl-build-hynbk0h3/arm64/install/arm64/include/openssl'
2024-10-30T14:25:05.5798950Z openssl> Copying: ./include/openssl/aes.h to C:/Users/RUNNER~1/AppData/Local/Temp/openssl-build-hynbk0h3/arm64/install/arm64/include/openssl/aes.h

Looks like -D"OPENSSL_USE_APPLINK" is set on amd64 but not arm64

zanieb · 2024-10-30T17:27:52Z

By manually copying the applink.c file, we make it to

2024-10-30T17:22:46.9472354Z Traceback (most recent call last):
2024-10-30T17:22:46.9481385Z   File "D:\a\python-build-standalone\python-build-standalone\cpython-windows\build.py", line 2046, in <module>
2024-10-30T17:22:46.9482543Z     sys.exit(main())
2024-10-30T17:22:46.9483423Z   File "D:\a\python-build-standalone\python-build-standalone\cpython-windows\build.py", line 2010, in main
2024-10-30T17:22:46.9484169Z     tar_path = build_cpython(
2024-10-30T17:22:46.9485025Z   File "D:\a\python-build-standalone\python-build-standalone\cpython-windows\build.py", line 1596, in build_cpython
2024-10-30T17:22:46.9486058Z     tests = subprocess.run(
2024-10-30T17:22:46.9486654Z   File "C:\hostedtoolcache\windows\Python\3.9.13\x64\lib\subprocess.py", line 505, in run
2024-10-30T17:22:46.9488654Z     with Popen(*popenargs, **kwargs) as process:
2024-10-30T17:22:46.9489422Z   File "C:\hostedtoolcache\windows\Python\3.9.13\x64\lib\subprocess.py", line 951, in __init__
2024-10-30T17:22:46.9491810Z     self._execute_child(args, executable, preexec_fn, close_fds,
2024-10-30T17:22:46.9492618Z   File "C:\hostedtoolcache\windows\Python\3.9.13\x64\lib\subprocess.py", line 1420, in _execute_child
2024-10-30T17:22:46.9495394Z     hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
2024-10-30T17:22:46.9496711Z OSError: [WinError 216] This version of %1 is not compatible with the version of Windows you're running. Check your computer's system information and then contact the software publisher
2024-10-30T17:22:46.9845209Z ##[error]Process completed with exit code 1.

Where we fail to run the PGO tests because, of course, we're not on an ARM runner.

https://github.com/indygreg/python-build-standalone/blob/00ea84cd2a525c8d20566482633903878bae2996/cpython-windows/build.py#L1596-L1602

zanieb · 2024-10-30T17:31:44Z

I don't really know what the plan is here. There aren't public ARM Windows runners (though they might be eventually actions/runner-images#10820 / github/roadmap#970). We (Astral) could pay for runners, but I can't set that up in this repository.

We could skip PGO, but we're still going to fail later (we need to invoke python.exe for various things).

zanieb · 2024-12-18T03:13:04Z

Now that this is in the Astral org, I intend to try adding an ARM runner.

zanieb · 2025-02-19T19:13:09Z

As a note, before releasing this we need to add proper prioritization for these builds to uv — as arm64 wheels are not prevalent we may not want to actually use these builds by default.

zooba · 2025-02-19T19:42:23Z

before releasing this we need to add proper prioritization for these builds to uv — as arm64 wheels are not prevalent we may not want to actually use these builds by default

FWIW, we still consider them experimental in upstream, and I'm regularly tracking whether to make them non-experimental. Right now, that's not going to happen anytime soon, unless I get sick of the people who are meant to be using them going "I'm not going to fix my package/tool until it's non-experimental" when it's still experimental because they haven't fixed anything (okay, clearly I'm already sick of them, but I can't shout at them all at once 😆 )

When we think it's time to unleash users on these builds by default, it'll be announced as part of an upstream beta release (or earlier, but probably not earlier - definitely no later than beta).

zanieb · 2025-04-16T00:31:07Z

3.9 fails validation due to missing tkinter extension module

2025-04-15T00:31:54.0323918Z cpython> WARNING  Failed to find TCL_LIBRARY
...
2025-04-15T00:32:03.7913938Z cpython> extension not present: _tkinter

3.13 fails more eagerly with the same problem

2025-04-15T00:16:13.8958569Z cpython> replacing `b'<_TclTkDLL Include="$(tcltkdir)\\bin\\$(tclZlibDllName)" />'` with `b''` in C:\Users\RUNNER~1\AppData\Local\Temp\python-build-ojo0tbal\Python-3.13.3\PCbuild\_tkinter.vcxproj
....
2025-04-15T00:19:07.5442513Z cpython>        ClCompile:
2025-04-15T00:19:07.5530958Z cpython>          C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Tools\MSVC\14.43.34808\bin\HostX86\arm64\CL.exe /c /I"C:\Users\RUNNER~1\AppData\Local\Temp\python-build-ojo0tbal\cpython-bin-deps-e3c3e9a2856124aa32b608632a52742d479eb7a9\arm64\include" /I"C:\Users\runneradmin\AppData\Local\Temp\python-build-ojo0tbal\Python-3.13.3\Include" /I"C:\Users\runneradmin\AppData\Local\Temp\python-build-ojo0tbal\Python-3.13.3\Include\internal" /I"C:\Users\runneradmin\AppData\Local\Temp\python-build-ojo0tbal\Python-3.13.3\Include\internal\mimalloc" /I"C:\Users\RUNNER~1\AppData\Local\Temp\python-build-ojo0tbal\Python-3.13.3\PCbuild\obj\\313arm64_PGInstrument\pythoncore\\" /I"C:\Users\runneradmin\AppData\Local\Temp\python-build-ojo0tbal\Python-3.13.3\PC" /Zi /nologo /W3 /WX- /diagnostics:column /MP /O2 /Oi /Oy- /GL /D "Py_TCLTK_DIR=\"C:\\Users\\RUNNER~1\\AppData\\Local\\Temp\\python-build-ojo0tbal\\cpython-bin-deps-e3c3e9a2856124aa32b608632a52742d479eb7a9\\arm64\"" /D WITH_APPINIT /D _Py_USING_PGO=1 /D WIN32 /D "PY3_DLLNAME=L\"python3t\"" /D _WIN32 /D NDEBUG /D _ARM64_WINAPI_PARTITION_DESKTOP_SDK_AVAILABLE=1 /D _WINDLL /GF /Gm- /MD /GS /Gy /fp:precise /Zc:wchar_t /Zc:forScope /Zc:inline /Fo"C:\Users\RUNNER~1\AppData\Local\Temp\python-build-ojo0tbal\Python-3.13.3\PCbuild\obj\313arm64_PGInstrument\_tkinter\\" /Fd"C:\Users\RUNNER~1\AppData\Local\Temp\python-build-ojo0tbal\Python-3.13.3\PCbuild\obj\313arm64_PGInstrument\_tkinter\vc143.pdb" /external:W3 /Gd /TC /analyze- /FC /errorReport:queue /utf-8 ..\Modules\_tkinter.c ..\Modules\tkappinit.c
...
2025-04-15T00:19:31.0026512Z cpython>        "C:\Users\RUNNER~1\AppData\Local\Temp\python-build-ojo0tbal\Python-3.13.3\PCbuild\_tkinter.vcxproj" (Build target) (41) ->
2025-04-15T00:19:31.0027038Z cpython>        (ClCompile target) ->
2025-04-15T00:19:31.0027984Z cpython>          C:\Users\runneradmin\AppData\Local\Temp\python-build-ojo0tbal\Python-3.13.3\Modules\tkappinit.c(16,10): error C1083: Cannot open include file: 'tcl.h': No such file or directory [C:\Users\RUNNER~1\AppData\Local\Temp\python-build-ojo0tbal\Python-3.13.3\PCbuild\_tkinter.vcxproj]
2025-04-15T00:19:31.0029929Z cpython>          C:\Users\runneradmin\AppData\Local\Temp\python-build-ojo0tbal\Python-3.13.3\Modules\_tkinter.c(52,12): error C1083: Cannot open include file: 'tcl.h': No such file or directory [C:\Users\RUNNER~1\AppData\Local\Temp\python-build-ojo0tbal\Python-3.13.3\PCbuild\_tkinter.vcxproj]

Looks like this is because the artifact we use for tcl/tk does not include arm64 binaries — so we'll try the newer version.

cpython-windows/build.py

zanieb · 2025-04-21T14:12:01Z

Okay now this is working on 3.11+, I don't want to get side-tracked debugging the 3.9 / 3.10 tkinter problems.

We'll also need to add these builds to the release targets.

zooba · 2025-04-21T14:55:31Z

I don't want to get side-tracked debugging the 3.9 / 3.10 tkinter problems

Neither did I, which is why we never enabled it upstream for those versions.

Honestly, I wouldn't bother with 3.11 and 3.12 either. There are potentially bugs in those that were never fixed.

There's also a known compiler bug in 14.43 (searching build output for 14.4 should find your version) that causes OpenSSL to crash. It's fixed in 14.44 (not released yet) and didn't exist in 14.40 (possibly also 14.41), so if you run into that issue also don't waste too much of your time. If you're using the same pre-built OpenSSL we use for CPython then you should be okay.

See astral-sh#12906 and astral-sh/python-build-standalone#387 - as soon as we start shipping arm64 Windows Python builds in python-build-standalone, uv is going to start discovering them, and there aren't enough arm64 Windows wheels for that to make sense as a default yet. As a very minimal stopgap, consider those builds incompatible. No functional change expected at the moment, but this unblocks python-build-standalone shipping arm64 Windows Python builds and lets us manage the transition in some better way like a configuration knob.

Refs: astral-sh/python-build-standalone#387 (comment) astral-sh/uv#12906 astral-sh/uv#13719 astral-sh/uv#13724

Co-authored-by: Adrian Antkowiak <[email protected]>

This reverts commit a9748a9.

and prefer emulated x64 windows in its stead. This is preparatory work for shipping support for uv downloading and installing aarch64 (arm64) windows Pythons. We've [had builds for this platform ready for a while](astral-sh/python-build-standalone#387), but have held back on shipping them due to a fundamental problem: **The Python packaging ecosystem does not have strong support for aarch64 windows**, e.g., not many projects build aarch64 wheels yet. The net effect of this is that, if we handed you an aarch64 python interpreter on windows, you would have to build a lot more sdists, and there's a high chance you will simply fail to build that sdist and be sad. Yes unfortunately, in this case a non-native Python interpreter simply *works better* than the native one... in terms of working at all, today. Of course, if the native interpreter works for your project, it should presumably have better performance and platform compatibility. We do not want to stand in the way of progress, as ideally this situation is a temporary state of affairs as the ecosystem grows to support aarch64 windows. To enable progress, on aarch64 Windows builds of uv: * We will still use a native python interpreter, e.g., if it's at the front of your `PATH` or the only installed version. * If we are choosing between equally good interpreters that differ in architecture, x64 will be preferred. * If the aarch64 version is newer, we will prefer the aarch64 one. * We will emit a diagnostic on installation, and show the python request to pass to uv to force aarch64 windows to be used. * Will be shipping [aarch64 Windows Python downloads](astral-sh/python-build-standalone#387) * Will probably add some kind of global override setting/env-var to disable this behaviour. * Will be shipping this behaviour in [astral-sh/setup-uv](https://github.com/astral-sh/setup-uv) We're coordinating with Microsoft, GitHub (for the `setup-python` action), and the CPython team (for the `python.org` installers), to ensure we're aligned on this default and the timing of toggling to prefer native distributions in the future. See discussion in - #12906 --- This is an alternative to * #13719 which uses sorting rather than filtering, as discussed in * #13721

zanieb force-pushed the zb/arm64 branch from e581c83 to 4a10c10 Compare October 30, 2024 02:32

zanieb mentioned this pull request Oct 30, 2024

Add aarch64 windows releases #386

Open

zanieb force-pushed the zb/arm64 branch 3 times, most recently from 116a612 to bb7bc6e Compare October 30, 2024 13:24

zanieb force-pushed the zb/arm64 branch 3 times, most recently from 49b6f84 to 00ea84c Compare October 30, 2024 17:09

zanieb mentioned this pull request Dec 18, 2024

WIP: Windows arm64 builds - help needed #93

Closed

zanieb added platform:windows Specific to the Windows platform arch:aarch64 labels Apr 14, 2025

zanieb force-pushed the zb/arm64 branch from 00ea84c to 2350279 Compare April 14, 2025 23:55

burgholzer mentioned this pull request Apr 15, 2025

uv installs x86_64 Python on arm64 Windows astral-sh/uv#12906

Open

zanieb force-pushed the zb/arm64 branch from 9bda576 to 2711fb9 Compare April 16, 2025 00:40

zanieb changed the title ~~Add ARM64 builds for Windows~~ Add ARM64 Windows builds for Python 3.10+ Apr 16, 2025

zanieb changed the title ~~Add ARM64 Windows builds for Python 3.10+~~ Add ARM64 Windows builds for Python 3.11+ Apr 16, 2025

burgholzer mentioned this pull request Apr 16, 2025

Python linker errors when running cibuildwheel on the new Windows 11 ARM runners pypa/cibuildwheel#2364

Open

zooba reviewed Apr 17, 2025

View reviewed changes

cpython-windows/build.py Show resolved Hide resolved

zanieb force-pushed the zb/arm64 branch 2 times, most recently from 57fee9e to 4e98498 Compare April 21, 2025 14:11

mbland mentioned this pull request Apr 22, 2025

Support Bzlmod and add rules_scala to bazel-central-registry bazel-contrib/rules_scala#1482

Closed

geofft mentioned this pull request May 29, 2025

Disallow arm64 Windows Python installs for now astral-sh/uv#13719

Closed

kdeldycke added a commit to kdeldycke/workflows that referenced this pull request Jun 8, 2025

Force uv to ignore managed Python on Windows ARM 64

ef6263f

Refs: astral-sh/python-build-standalone#387 (comment) astral-sh/uv#12906 astral-sh/uv#13719 astral-sh/uv#13724

Avasam mentioned this pull request Jun 13, 2025

Native Linux ARM64 builds Toufool/AutoSplit#328

Merged

Gankra mentioned this pull request Jun 13, 2025

disfavor aarch64 windows in its own house astral-sh/uv#13724

Merged

zanieb and others added 17 commits June 16, 2025 13:52

Add ARM64 builds for Windows

f80dc1f

Co-authored-by: Adrian Antkowiak <[email protected]>

Add arm64 to collect_python_build_artifacts

56339b6

Use the newer tcl-tk bin for arm64 builds

6b8d80c

Add recognized triple

66b7be1

All Tcl/Tk patch to fail

c539516

Update abi platform

527957b

Disable 3.9 / 3.10

aa7e8e7

Add platformt ag entry

140bd79

Update validation for arm64

137ba57

Allow arm64 libssl

8f6311b

Fix double underscore

238f27c

Add timeout to jobs

b76ccc0

Delete x86_64-w64-mingw32-nmakehlp.exe from tcltk

4323f7d

Patch tcltk toggle?

e2ed7fa

Allow api-ms-win-crt-private-l1-1-0.dll

11ec9b3

Enable 3.9 and 3.10 again?

dd7e34c

Revert "Enable 3.9 and 3.10 again?"

024f688

This reverts commit a9748a9.

zanieb force-pushed the zb/arm64 branch 2 times, most recently from 465c0b7 to 1b37af1 Compare June 16, 2025 19:22

Use consistency exception type

d49911d

zanieb force-pushed the zb/arm64 branch from 1b37af1 to d49911d Compare June 16, 2025 20:33

zanieb merged commit 97c36a3 into main Jun 28, 2025
16 checks passed

zanieb deleted the zb/arm64 branch June 28, 2025 03:12

zanieb mentioned this pull request Jun 28, 2025

Revisit handling of applink.c on arm64 Windows builds #669

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

Add ARM64 Windows builds for Python 3.11+ #387

Add ARM64 Windows builds for Python 3.11+ #387

Uh oh!

zanieb commented Oct 30, 2024 •

edited

Loading

Uh oh!

zanieb commented Oct 30, 2024 •

edited

Loading

Uh oh!

zanieb commented Oct 30, 2024

Uh oh!

zanieb commented Oct 30, 2024 •

edited

Loading

Uh oh!

zanieb commented Dec 18, 2024

Uh oh!

zanieb commented Feb 19, 2025

Uh oh!

zooba commented Feb 19, 2025 •

edited

Loading

Uh oh!

zanieb commented Apr 16, 2025 •

edited

Loading

Uh oh!

Uh oh!

zanieb commented Apr 21, 2025 •

edited

Loading

Uh oh!

zooba commented Apr 21, 2025

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Add ARM64 Windows builds for Python 3.11+ #387

Add ARM64 Windows builds for Python 3.11+ #387

Uh oh!

Conversation

zanieb commented Oct 30, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

zanieb commented Oct 30, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

zanieb commented Oct 30, 2024

Uh oh!

zanieb commented Oct 30, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

zanieb commented Dec 18, 2024

Uh oh!

zanieb commented Feb 19, 2025

Uh oh!

zooba commented Feb 19, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

zanieb commented Apr 16, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

zanieb commented Apr 21, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

zooba commented Apr 21, 2025

Uh oh!

Uh oh!

Uh oh!

zanieb commented Oct 30, 2024 •

edited

Loading

zanieb commented Oct 30, 2024 •

edited

Loading

zanieb commented Oct 30, 2024 •

edited

Loading

zooba commented Feb 19, 2025 •

edited

Loading

zanieb commented Apr 16, 2025 •

edited

Loading

zanieb commented Apr 21, 2025 •

edited

Loading