Closed astrelsky closed 1 month ago
Attention: Patch coverage is 97.87234%
with 1 line
in your changes missing coverage. Please review.
Project coverage is 87.21%. Comparing base (
66f8c6c
) to head (1b76a40
). Report is 3 commits behind head on master.
Files with missing lines | Patch % | Lines |
---|---|---|
native/python/pyjp_package.cpp | 75.00% | 1 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Minor suggestion.... given that all uses of this function should be placed in a JPPyObject wrapper via call
to we don't leak it would seem like combining the two would make sense. It would take some minor reworking of a few sections which were already dangerous for exceptions.
Minor suggestion.... given that all uses of this function should be placed in a JPPyObject wrapper via
call
to we don't leak it would seem like combining the two would make sense. It would take some minor reworking of a few sections which were already dangerous for exceptions.
Agreed. I'll do this tonight.
The changes were mostly painless. I only had to think about one change which was in PyJPClass_FromSpecWithBases
. I left a comment where it should not be used in that function.
Seems like the mac compiler is a bit over picky about constexpr
. It's technically not wrong, but the standard is not that strict. It was only added out of habit to begin with. Not sure why it doesn't fail to compile anything using a standard c++ header :joy:.
Merge for upcoming release.
This prevents simple mistakes such as the following
https://github.com/jpype-project/jpype/blob/66f8c6c07e051eb430326418798736004b0f833b/native%2Fpython%2Fpyjp_number.cpp#L390