-
Notifications
You must be signed in to change notification settings - Fork 749
[WIP] Drop tp_call implementation from metatype #496
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
Conversation
This seems to be a patch for broken behaviour in Python. Removing it should solve pythonnet#495 (`__init__` called twice on construction).
350b65a
to
9f64f56
Compare
Codecov Report
@@ Coverage Diff @@
## master #496 +/- ##
==========================================
- Coverage 76.41% 75.95% -0.47%
==========================================
Files 64 64
Lines 5572 5572
Branches 895 894 -1
==========================================
- Hits 4258 4232 -26
- Misses 1020 1044 +24
- Partials 294 296 +2
Continue to review full report at Codecov.
|
Don't merge this yet, apparently the example given by @rickardraysearch is not tested. When running his test:
one can see that without the |
My very naive understanding of what is being done in pythonnet is as follows: Since there's no exact equivalence to a constructor in python indicating which base constructor to use (apart from calling one in Wouldn't it make more sense to have a |
This is exactly what I was looking into right now :) |
This seems to be a patch for broken behaviour in Python. Removing it
should solve #495 (
__init__
called twice on construction).What does this implement/fix? Explain your changes.
#495
Does this close any currently open issues?
#495
Checklist
Check all those that are applicable and complete.
AUTHORS
CHANGELOG