Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

_nanosvg.obj : error LNK2001: unresolved external symbol _PyGen_Send reported when building wxPython on Python 3.10 #2016

Closed
zosun opened this issue Oct 7, 2021 · 4 comments · Fixed by #2017

Comments

@zosun
Copy link

zosun commented Oct 7, 2021

OS: Windows 10 64bits

I am trying to install wxPython for Python 3.10.

MSVC build tool v14

Operating system:
Python 3.10 64 bit
wxPython 4.1.1

Creating library build/wxsvg\temp.win-amd64-3.10\Release\wx/svg_nanosvg.cp310-win_amd64.lib and object build/wxsvg\temp.win-amd64-3.10\Release\wx/svg_nanosvg.cp310-win_amd64.exp
_nanosvg.obj : error LNK2001: unresolved external symbol _PyGen_Send
build\wxsvg\lib.win-amd64-3.10\wx\svg_nanosvg.cp310-win_amd64.pyd : fatal error LNK1120: 1 unresolved externals
error: command 'C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Tools\MSVC\14.29.30133\bin\HostX86\x64\link.exe' failed with exit code 1120
Command 'C:\Python3.10\python.exe setup-wxsvg.py build_ext --inplace' failed with exit code 1.

after searching the wxPython code:

wx/svg/_nanosvg.c:20946: ret = _PyGen_Send((PyGenObject*)yf, value == Py_None ? NULL : value);
wx/svg/_nanosvg.c:20951: ret = _PyGen_Send((PyGenObject*)yf, value == Py_None ? NULL : value);
wx/svg/_nanosvg.c:21035: ret = _PyGen_Send((PyGenObject*)yf, NULL);

According to Python forum, the _PyGen_Send is replaced by PyIter_Send().

Maybe wxPython should check Python version to determine which function is called, PyIter_Send or PyGen_Send()

Thanks/Gavin

@swt2c
Copy link
Collaborator

swt2c commented Oct 7, 2021

Thanks, this seems to be fixed in newer Cython, see #2017

@zosun
Copy link
Author

zosun commented Oct 15, 2021

When is this fix merged to mainline branch and released?

@swt2c
Copy link
Collaborator

swt2c commented Oct 16, 2021

Whenever @RobinD42 re-emerges and gets back to working on wxPython again.

@RobinD42
Copy link
Member

This issue has been mentioned on Discuss wxPython. There might be relevant details there:

https://discuss.wxpython.org/t/serious-upgrade-problem/35604/4

jamesdbrock added a commit to jamesdbrock/nixpkgs that referenced this issue Sep 29, 2022
Add wxPython v4.2.0 for Python v3.10
Disable wxPython v4.1.1 for Python v3.10, because wxWidgets/Phoenix#2016
jamesdbrock added a commit to jamesdbrock/nixpkgs that referenced this issue Sep 29, 2022
Add wxPython v4.2.0
Disable wxPython v4.1.1 for Python v3.10, because wxWidgets/Phoenix#2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants