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
convert not coerce padics symbolic function arguments #17790
Comments
comment:1
So, either it's a problem of p-adics not being coercible into |
Commit: |
Author: Ralf Stephan |
comment:3
It was the latter alternative, as there is no coercion. Please review. New commits:
|
comment:4
The recent #17852 makes So what should |
comment:5
@jdemeyer, what reason is there in the respective snippet of
i.e. not throwing at all. I keep needing exceptions like the Do we have a fundamental problem here? Why can |
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:10
one failing doctest see patchbot report |
comment:12
I think this ticket is wontfix because a better solution would be to write a global Python function accepting everything (as in rings.arith...) and dispatch to the symbolic function for symbolic arguments. In the ticket case just do
|
This affects authors of function code but shows also in:
test.
CC: @jdemeyer
Component: symbolics
Author: Ralf Stephan
Branch/Commit: u/rws/builtinfunction_doesn_t_pass_non_sr_coercible_arguments_to_function_code @
e4a30b6
Issue created by migration from https://trac.sagemath.org/ticket/17790
The text was updated successfully, but these errors were encountered: