Status: NeedsDecision
Owner: asmeurer
Labels: Type-Defect Priority-Medium Python3
New 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
I just noticed that the new IPython 0.11 only supports Py
Comment #8 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
Related to this, we need to find a way to programatically determine whether
bin/use2to3 was ran on the code base.
Comment #9 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
Let's keep it all on the same issue, and try to fix all of it by the next
release.
--
You received this message because you a
Updates:
Labels: NeedsReview
Comment #10 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
Pull request: https://github.com/sympy/sympy/pull/671
--
You received this me
Updates:
Status: Fixed
Labels: -NeedsReview
Comment #11 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
This got in, so fixed.
--
You received this message be
Comment #1 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
Actually, importing under Python 3 does result in an immediate SyntaxError,
and probably will forever. As to raisi
Comment #2 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
No, I mean importing under Python 3.*0*. I just tried it in your
porting-2to3 branch, and it doesn't raise an error at import
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 ou
Comment #4 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
Yeah, I guess we should see what actually happens in Python 3.0.
For 2.4 at least, such an error message would be more user-frie
Comment #5 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
After seeing this post[1] on the mailing list, I'm convinced a more
user-friendly warning is a good idea. I guess
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
Updates:
Status: Started
Owner: vlada.pe...@gmail.com
Comment #7 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
I'll do this.
--
You received this message be
12 matches
Mail list logo