Re: Issue 2612 in sympy: Error in quantum/__init__.py under Python 3

Comment #6 on issue 2612 by asmeurer: Error in quantum/__init__.py under Python 3 http://code.google.com/p/sympy/issues/detail?id=2612 Ah, then it's clearly a bug in the doctester. It shouldn't be trying to run tests in a file that has no doctests. -- You received this message because yo

Re: Issue 2620 in sympy: Eq(x, x) is not True

Comment #2 on issue 2620 by asmeurer: Eq(x, x) is not True http://code.google.com/p/sympy/issues/detail?id=2620 Before you fix this, take a look at issue 1887. -- You received this message because you are subscribed to the Google Groups "sympy-issues" group. To post to this group, send email t

Re: Issue 2620 in sympy: Eq(x, x) is not True

Comment #1 on issue 2620 by mrock...@gmail.com: Eq(x, x) is not True http://code.google.com/p/sympy/issues/detail?id=2620 Pull request https://github.com/sympy/sympy/pull/523 -- You received this message because you are subscribed to the Google Groups "sympy-issues" group. To post to this grou

Issue 2620 in sympy: Eq(x, x) is not True

Status: Accepted Owner: mrock...@gmail.com Labels: Type-Defect Priority-Medium New issue 2620 by mrock...@gmail.com: Eq(x, x) is not True http://code.google.com/p/sympy/issues/detail?id=2620 x = Symbol('x') Eq(x, x) x = x Shouldn't this just evaluate to True? -- You received this message bec

Re: Issue 2619 in sympy: Should we give a better error message on unsupported versions of Python?

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

Re: Issue 2608 in sympy: test_pickling errors under Python 3

Comment #5 on issue 2608 by asmeurer: test_pickling errors under Python 3 http://code.google.com/p/sympy/issues/detail?id=2608 Yes, hasattr() in Python 2 masks bugs. I though this was a pretty well advertised change for Python 3, but I guess you hadn't heard of it. But they are still bugs,

Re: Issue 2612 in sympy: Error in quantum/__init__.py under Python 3

Updates: Cc: ronan.l...@gmail.com Comment #5 on issue 2612 by vlada.pe...@gmail.com: Error in quantum/__init__.py under Python 3 http://code.google.com/p/sympy/issues/detail?id=2612 (No comment was entered for this change.) -- You received this message because you are subscribed to t

Re: Issue 2612 in sympy: Error in quantum/__init__.py under Python 3

Updates: Status: NeedsDecision Cc: asmeurer Labels: Documentation Comment #4 on issue 2612 by vlada.pe...@gmail.com: Error in quantum/__init__.py under Python 3 http://code.google.com/p/sympy/issues/detail?id=2612 Well, the thing is that the advertised behavior works i

Re: Issue 2619 in sympy: Should we give a better error message on unsupported versions of Python?

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

Re: Issue 2608 in sympy: test_pickling errors under Python 3

Comment #4 on issue 2608 by vlada.pe...@gmail.com: test_pickling errors under Python 3 http://code.google.com/p/sympy/issues/detail?id=2608 Yes, a quick search leads me to this issue upstream: http://bugs.python.org/issue9666 ("'hasattr' fix to suppress only AttributeError"). To quote the

Re: Issue 2608 in sympy: test_pickling errors under Python 3

Comment #3 on issue 2608 by vlada.pe...@gmail.com: test_pickling errors under Python 3 http://code.google.com/p/sympy/issues/detail?id=2608 This seems to be related to using the @property decorator (or properties in general) as it's the only common thing between the two errors. It fails on

Re: Issue 2619 in sympy: Should we give a better error message on unsupported versions of Python?

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

Re: Issue 2619 in sympy: Should we give a better error message on unsupported versions of Python?

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

Re: Issue 2612 in sympy: Error in quantum/__init__.py under Python 3

Comment #3 on issue 2612 by vlada.pe...@gmail.com: Error in quantum/__init__.py under Python 3 http://code.google.com/p/sympy/issues/detail?id=2612 This seems to fail only for the two functions using __all__ (qapply and represent, which are imported as qapmod and repmod). This is obvious,

Re: Issue 2619 in sympy: Should we give a better error message on unsupported versions of Python?

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

Re: Issue 2619 in sympy: Should we give a better error message on unsupported versions of Python?

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