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
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,
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
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
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: 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
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,
I have recently installed sympy. I have the newest version of python. The
symoy site said that it is compatible with the version I have but everytime
I try to import the sympy module using this command:
from sympy import *
I always get the following error:
Traceback (most
On Mon, Aug 1, 2011 at 4:44 PM, Jefferson jbr5...@gmail.com wrote:
I have recently installed sympy. I have the newest version of python. The
symoy site said that it is compatible with the version I have but everytime
I try to import the sympy module using this command:
from sympy
Hello folks,
Long time back, I made a pull request for changing the definition of
limits[0] accordance to issue 1000. I was unable to work on the problem
related to that because of my other engagements. Now to refresh the matter,
my branch is 667 commits ahead of origin/master and I have to
Hi,
I was recently browsing SymPy's SVN repository (sympy-oldcore branch which
contains the original implementation of SymPy) and I noticed that the first
commit was created on 2006-08-01 02:03:30 +0200 (Tue, 01 Aug 2006), which
means that today it's exactly five years since SymPy was started.
It can also help if you commit what you have and push it up, so we can
see what you did.
Aaron Meurer
On Mon, Aug 1, 2011 at 10:28 AM, Vladimir Perić vlada.pe...@gmail.com wrote:
Hi,
On Mon, Aug 1, 2011 at 6:19 PM, Hector hector1...@gmail.com wrote:
Hello folks,
Long time back, I made a
Very cool. I think Ondrej said that he actually started it earlier
than that, but I can't find the thread on the mailing list.
On Mon, Aug 1, 2011 at 3:55 PM, Mateusz Paprocki matt...@gmail.com wrote:
Hi,
I was recently browsing SymPy's SVN repository (sympy-oldcore branch which
contains the
13 matches
Mail list logo
