-
Notifications
You must be signed in to change notification settings - Fork 717
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
Incorrectly using a non-generic type with type parameters now produces a helpful Python error instead of throwing NullReferenceException #1326
Conversation
The tests appear to be failing for the reasons addressed by PR #1260. Applying those changes should make the tests pass. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice addition, thank you. If you can just move the test to Python, this is good to go :)
@lostmsu My only point was that the test failures are the same as the ones in the current master, and those are due to finalization/deallocation bugs. |
f2ceaf6
to
24683d0
Compare
Please make this just a normal Python test. You can run pytest from within VisualStudio using our normal APIs ( |
Ah, I see that you have already moved the test. Would you be okay with splitting the |
5db975a
to
d1103ec
Compare
…s a helpful Python error instead of throwing NullReferenceException
Removed unused GenericUtil.GenericsForType. Other code quality improvements.
Added EmbeddedPythonTest with the capability to run any desired Python tests within NUnit.
d1103ec
to
20e673f
Compare
What does this implement/fix? Explain your changes.
Fixes #1325
Does this close any currently open issues?
Fixes #1325
Any other comments?
...
Checklist
Check all those that are applicable and complete.
AUTHORS
CHANGELOG