Updates:
Status: Accepted
Labels: Milestone-Release0.7.2
Comment #6 on issue 2619 by asmeurer: Should we give a better error message
on unsupported versions of Python?
http://code.google.com/p/sympy/issues/detail?id=2619
Exactly. If the Python 3 port is not ready by the next release, we should
add a note to __init__.py. And similarly for Python 2.4, someone might
think it is a bug, maybe not even realizing that they are running it in
Python 2.4. Right now, they would see
Traceback (most recent call last):
File "<stdin>", line 1, in ?
File "sympy/__init__.py", line 20, in ?
from sympy.core import *
File "sympy/core/__init__.py", line 4, in ?
from sympify import sympify
File "sympy/core/sympify.py", line 5, in ?
from core import all_classes as sympy_classes
File "sympy/core/core.py", line 2, in ?
from sympy.core.compatibility import cmp
File "sympy/core/compatibility.py", line 160
r = n if r is None else r
So I'm 100% convinced that we should do this. For Python 3.0, let's wait
until the port is finished, and see how things work there.
--
You received this message because you are subscribed to the Google Groups
"sympy-issues" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sympy-issues?hl=en.
