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
ensure cythonized functions are left untouched #1944
ensure cythonized functions are left untouched #1944
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1944 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 21 21
Lines 3909 3909
Branches 788 788
=========================================
Hits 3909 3909 Continue to review full report at Codecov.
|
thanks so much for the contribution. please can you add tests and a change description. also, in future please fill in the template in pull requests. |
bump |
@kollmats please could you fixthis. |
Hi @samuelcolvin, I'm sorry for this question since it may already be stated clearly somewhere, but where would be a good place to test this in your setup given that a proper test would require a cythonized application? Thanks. |
all tests are run on pydantic when compiled with cython. Just choose the file in |
Made a test on #2208 just to see the CI fail with a test similar to the one in the issue and it didn't fail. I probably miss something |
I see the problem, the point is that the code where It doesn't matter one way or the other whether or not pydantic itself is compiled. I'm just seeing if I can add a simple test for this. |
Change Summary
Extending the check for untouched types to include a check for cython functions or methods.
Related issue number
Resolves #1943