Comment #3 on issue 2619 by vlada.pe...@gmail.com: Should we give a better error message on unsupported versions of Python?
http://code.google.com/p/sympy/issues/detail?id=2619

Oh, I see. Yeah, that's probably a good idea then. It also occurs to me that an ImportError is more robust than our current test in setup.py (as SymPy doesn't need to be installed to be used), so I guess I'm in favor of such a change.

... on the other hand, I haven't run tests with 3.0, but it could actually (mostly) work. Perhaps we shouldn't hard-fail if the code will mostly work, rather just output a warning or such ("This version is NOT supported. If it works, it's completely by accident and you should update asap."). This way a user who is forced to use 3.0 could still accomplish something simple in SymPy (without eg. hacking the code). This might be moot for 3.0, but it could be useful for 3.1 (the whole IGNORE_EXCEPTION_DETAIL stuff and so on). Thoughts?

--
You received this message because you are subscribed to the Google Groups 
"sympy-issues" group.
To post to this group, send email to sympy-issues@googlegroups.com.
To unsubscribe from this group, send email to 
sympy-issues+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/sympy-issues?hl=en.

Reply via email to