[issue17213] ctypes loads wrong version of C runtime, leading to error message box from system

Igor Skochinsky added the comment: Just had this issue when using networkx (which imports uuid). One keyword that would help visibility is R6034 (the runtime error number). A couple of reports related to this: https://projects.blender.org/tracker/index.php?func=detailaid=27666 http

[issue28687] Python 2.7.12 windows x64 installer fails after previous bad uninstall

New submission from Igor Skochinsky: It's somewhat my fault but I think it's not such an uncommon scenario. I had installed 2.7.10 x64 some time ago into C:\Python27_64 but then had to delete it to save space. Rather foolishly instead of using the uninstaller, I just trashed the directory

[issue31767] Windows Installer fails with error 0x80091007 when trying to install debugging symbols

Igor Skochinsky <skochin...@gmail.com> added the comment: Hi Steve, Thanks for the suggestion! I tried that and while it did not succeed it gave me an idea of what went wrong last time since it complained about lack of disk space. I have *not* run the /layout but now that I checked I

[issue31767] Windows Installer fails with error 0x80091007 when trying to install debugging symbols

New submission from Igor Skochinsky <skochin...@gmail.com>: Trying to install 3.6.3 on Windows 10 and getting this error. Repro steps: 1. Download python-3.6.3.exe or python-3.6.3-amd64.exe, run it 2. Select "Customize Installation" 3. Next 4. In Advanced Options, select [x]

[issue40939] Remove the old parser

Igor Skochinsky added the comment: > But Py_CompileString() function was not removed, it's still in the master > branch (future Python 3.10). Why do you think that it has been removed? Thank you. It looked that way because of the removed block of lines in the

[issue40939] Remove the old parser

Igor Skochinsky added the comment: Hi All, It seems this patch removes some functions provided by the Stable ABI (PEP 384), most notably Py_CompileString. Was this the intention? If not, is there still a chance to reintroduce it before the release? -- nosy: +Igor.Skochinsky

[issue40939] Remove the old parser

Igor Skochinsky added the comment: Attached is a sample program which works on 3.9 but fails linking with 3.10.0a2 The .so is missing the symbol: igor@LAPTOP:~/py_limited_api_example$ nm /home/igor/lib/libpython3.9.so | grep Py_CompileString 00212720 T Py_CompileString

[issue42545] Check that all symbols in the limited ABI are exported

Change by Igor Skochinsky : -- nosy: +Igor.Skochinsky ___ Python tracker <https://bugs.python.org/issue42545> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue40939] Remove the old parser

Igor Skochinsky added the comment: Thanks for the fix! I'd like to submit a test to avoid this and similar issues in future. Are there any guidelines for this? Sorry if this is a wrong place to ask. -- ___ Python tracker <ht

[issue40939] Remove the old parser

Igor Skochinsky added the comment: > I am currently working on test that checks that the stable API symbols are > correctly exported. Thank you very much! For added motivation, the 3.8.0 release was unusable thanks to issue37633 which was somewhat similar (also in pythonrun). For ref