-
Notifications
You must be signed in to change notification settings - Fork 747
python 3.7 issues #609
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
Comments
I am seeing the same error when attempting to build Docker images for https://github.com/jonemo/pythonnet-docker for all combinations that involve Python 3.6.5:
Python 3.5.5 and 3.4.8 are not affected. Here is the output I get for the command
|
Same issue here with python3.6.5 on a clean pipenv environment. |
any hope of Windows pythonnet wheel under Python-3.7 ? where a few days before RC. |
I have the same issue on the Windows Linux subsystem using (Python, Mono, Dotnet) = (3.6.5, 5.12, 2.1.300) building out of master. However, you can "cheat" to make it work until a fix is in place, as follows:
(instruction from Installation page) |
also if someone can attach debug files generated by pycparser/ply during this error, that would be helpful too. |
It appears to be 3.6.5 -- it works on 3.6.{2, 3, 4}. On master, it fails on l. 220 of
Not sure how to generate the debug files of pycparser. Ps. This is run in conda environments ( |
@fractus it appears that this additional header https://docs.python.org/3/whatsnew/changelog.html#id8 |
@denfromufa Not sure if this is what you're looking for, but I've attached a trace log file generated when trying to build pythonnet 2.3.0 from source on Pop!_OS 18.04 LTS (Linux x64). I obtained the source from https://anaconda.org/pythonnet/pythonnet/files . I get the same errors noted above. |
@thomasmortiz that trace does not contain the pycparser error. this is probably only tracing of python imports. actually we don't need any debug/log, just fix/avoid crypt.h parsing. |
Python-3.7.0 is out. |
@stonebig waiting for this 😸 appveyor/ci#2475 I added a py37 branch in the meantime with interop37.cs copied from interop36.cs as-is. |
appveyor seems ready, now. |
the wheel pythonnet-2.4.0.dev0-cp37-cp37m-win32.whl from cgohlke works great on Python-3.7 ! |
This also occurs for me on Python 3.5.2 |
still a huge improvement over nothing, and it passes my stupid test. |
some progress on the python 3.7 support, but now an error from clang during parsing: I have no idea how to fix this! |
On the problem related to https://bugs.python.org/issue31370, maybe @pitrou could give you a quick suggestion. Let's pray. |
The only suggestion is to build Python on a platform that has support for threads (either pthreads, or Win32). |
@pitrou thanks for stepping in, but this is ubuntu trusty/xenial and normal cpython 2.7-3.7 from travis ci with obvious support of threads. So do I need to pass some special flag to clang in order to parse this header https://travis-ci.org/pythonnet/pythonnet/jobs/415741697#L1999 |
Well, you probably know better than me what this build chain does. But just be aware that Python 3.7 compiles fine in CPython's own Travis-CI setup ;-) At least the command line looks unusual ( |
fake_libc_include from pycparser is documented pretty well and used all
over to parse c-header files non-conformant to c99.
And the build used to parse the headers for python37-dev.
…On Tue, Aug 14, 2018, 12:56 PM Antoine Pitrou ***@***.***> wrote:
Well, you probably know better than me what this build chain does. But
just be aware that Python 3.7 compiles fine in CPython's own Travis-CI
setup ;-)
At least the command line looks unusual ('-I',
'tools/geninterop/fake_libc_include'?):
https://travis-ci.org/pythonnet/pythonnet/jobs/415741697#L2017
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#609 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHgZ5awd_hsamDXQoIElUgk-ipsz0dBQks5uQw9FgaJpZM4Rvzar>
.
|
ok, reported in pycparser: eliben/pycparser#276 |
Maybe we should try out this pycparser extended version or/and gcc parser: |
This is now fixed, like @eliben suggested it was a missing https://github.com/pythonnet/pythonnet/blob/py37/tools/geninterop/geninterop.py#L177
|
Next is nuget/msbuild issue under Mono: |
Python 3.7 support is merged! |
oh, and this fixes reported parsing errors on Python 3.6+ with geninterop/pycparser/ply. |
The pythonnet VS2017 GUI build fails for Python 3.7. Apparently due to not have interop37.cs in Python.Runtime.csproj (but I'm not a Visual Studio expert):
|
@Jeff17Robbins my bad, can you please submit a PR to include this file to project file? |
@denfromufa I'll get help from some actual programmers at work on this. I'm not too git savvy. |
some follow-up issues: @Jeff17Robbins you can just make this change from github UI without git. |
@denfromufa @paulie4 and I discussed, and he created the PR. As he already stated, we are only able to test with VS2017. Also already stated, the UnmanagedExports tool doesn't seem to know how to find The Release Notes on the nuget site says
But...that's not a good thing! The failure shows up at runtime, not build time:
We couldn't find the source code site for that UnmanagedExports tool, so we don't know how to fix it. |
pycparser error:
https://travis-ci.org/pythonnet/pythonnet/jobs/334432678#L1991
pycparser.plyparser.ParseError: /usr/include/crypt.h:33:6: before: __THROW
The text was updated successfully, but these errors were encountered: