https://bugzilla.redhat.com/show_bug.cgi?id=2134021
--- Comment #13 from Sandro Mani <[email protected]> --- The python-build approach is turning out to be pretty complex, as it is based on virtual environments, which currently don't work for cross-compilation with mingw-python3. Currently mingw-python works by tweaking the environment basically as follows: pylibdynload=`/usr/bin/python3.11 -c 'import sysconfig; import os; print(os.path.join(sysconfig.get_path("stdlib"), "lib-dynload"))'`; _PYTHON_HOST_PLATFORM=mingw \ _PYTHON_SYSCONFIGDATA_NAME="_sysconfigdata__win32_" \ PYTHONHOME=/usr/x86_64-w64-mingw32/sys-root/mingw \ PYTHONPATH=$PYTHONPATH:/usr/x86_64-w64-mingw32/lib/python3.11:/usr/x86_64-w64-mingw32/lib/python3.11/site-packages:$pylibdynload:/usr/x86_64-w64-mingw32/sys-root/mingw/lib/python3.11:/usr/x86_64-w64-mingw32/sys-root/mingw/lib/python3.11/site-packages \ PYTHONPLATLIBDIR=lib \ /usr/bin/python3.11 I'd need to figure out how to patch venv to ensure that this environment is properly preserved. Before I go down the route of patching venv, might the current pyproject approach be the better/simpler solution after all? -- You are receiving this mail because: You are always notified about changes to this product and component You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2134021 _______________________________________________ package-review mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
