Disabled float and bool implicit conversions
#1584
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lostmsu
force-pushed
the
no-implicit-float-or-bool
branch
3 times, most recently
from
26add1e
to
682fcce
Compare
… point types arbitrary Python objects are no longer implicitly converted to .NET bool type this is a continuation of pythonnet#1568
lostmsu
force-pushed
the
no-implicit-float-or-bool
branch
from
682fcce
to
93d4840
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
What does this implement/fix? Explain your changes.
Disabled using
__float__during implicit conversions to .NET floating-point types. Explicit conversion is possible in Python withfloat(val)and .NET with(double)dynamicPyObj.Arbitrary Python objects are no longer implicitly converted to .NET
booltype.Does this close any currently open issues?
this is a continuation of #1568
related to #1539
Checklist
Check all those that are applicable and complete.
CHANGELOG