LGTM, but check the Codacy findings to fix, or ignore any false-positives.

@DaveSkender Yeap. All of those can be ignored

@DaveSkender Just a trivial thing. Which version should be increased? minor or patch?
The thing is that the code change is not that much, but the impact may be big

@DaveSkender Just a trivial thing. Which version should be increased? minor or patch? The thing is that the code change is not that much, but the impact may be big

If there’s no change to the actual API and is not a breaking change, patch is all you’d need. If you consider this a new feature, minor. Just a patch IMO, even if a big relief to users.

I don't have any open concerns with this, LGTM. Please proceed with it.

@DaveSkender An idea came up with!
The problem is we need to convert C# Decimal into Python Decimal, Culture-Invariantly.
And C# double is automatically converted into Python float and this does not affected by locale setting.
Maybe we can use this (if we take precision loss a bit):

1. Convert C# decimal into C# double first
2. And then, it's converted into Python float by pythonnet.

@DaveSkender I had a quick test. And this way has max 3x performance gain!

    if cs_decimal is not None:
        return CsDecimal.ToDouble(cs_decimal)

But few tests fails due to precision problem