-
Notifications
You must be signed in to change notification settings - Fork 17
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
Exposing sympy API #299
Comments
Yeah you're probably right about this. The original reason for doing this is that there is probably a lot of useful stuff in sympy that people want to have access to, and it's a changing list over time. Is there a smart way to get both proper paths and a maintenance free way of exposing sympy? |
Yes I understand the reasoning and I frequently use this issue is related to: sympy/sympy#12115 The only fix I can think of is manually importing what could be useful. But if you look in |
In api.py the sympy API is exposed by:
This has the consequence that:
What? symfit.core is not sympy.core.core? Its probably not a problem but it caused me a lot of confusion since you can't import anymore like this:
Maybe we can only import the useful stuff from sympy instead of importing *?
The text was updated successfully, but these errors were encountered: