-
Notifications
You must be signed in to change notification settings - Fork 525
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
zsys access from python #1684
Comments
Yes that is a known problem, since they are not generated by zproject there's no binding generation. No idea how we can solve it. |
I have an issue on Windows. Either a crash or a stall (after last python code) zsys_shutdown is called atexit. if i call
at the end of my python program, i have no issue at all... |
I thought there was no atexit on windows? |
That was with a DLL build though, might not be your case: |
Is there a deficiency in zproject or oddity about https://github.com/zeromq/zproject/blob/dfb1af34e52350cd6a94956f618e41611c8eb152/api/myclass.api#L99 |
Honestly not sure. Perhaps it's simply that nobody has tried to convert it until now. PRs welcome as usual :-) |
Right, I just wanted to see if there was a known deficiency in the zproject API model, since I helped design it (however many years ago). |
So @diorcety if you wanted to try your hand at writing an API def for |
I manage do create the api. but i have two issues. First one: |
Push your changes to your fork and I'll have a look at it.
Am 15.06.2017 09:23 schrieb "Diorcet Yann" <notifications@github.com>:
I manage do create the api. but i have two issues. First one:
(zproject_nodejs.gsl 704) Undefined expression:
Second one: Even if I skip nodejs, python binding is not built.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1684 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAeGugJVFIkUYcySPwzI_AArp4WqsLBuks5sENwPgaJpZM4N4wFW>
.
|
I found the problem: zeromq/zproject#912 |
Now the Python test errors with:
|
Certainly due to inaddr_t |
I guess we have to fix it in zproject? |
or remove this method from the api too |
I guess the only problem is that the inaddr_t type is not supported - that would be worth adding |
The problem was that the "type" was not specified together with the "c_type", so zproject's Python generation was not happy: #1688 @sappo now the last thing to fix is JNI, any idea what this is all about:
|
Seems like at least the first error is due to |
Sorry I triggerd lot of issues :s |
eheh no worries, on the contrary it's good, many issues fixed |
This issue has been automatically marked as stale because it has not had recent activity for 90 days. It will be closed if no further activity occurs within 21 days. Thank you for your contributions. |
There is no way to access zsys_* functions from python binding
The text was updated successfully, but these errors were encountered: