Updates:
Status: Fixed
Cc: krastano...@gmail.com
Labels: -NeedsReview
Comment #26 on issue 3272 by vlada.pe...@gmail.com: Python 3.3 test failures
http://code.google.com/p/sympy/issues/detail?id=3272
Well, there don't appear to be any failures in master anymore, I'll go
Updates:
Cc: ness...@gmail.com
Comment #22 on issue 3272 by asmeu...@gmail.com: Python 3.3 test failures
http://code.google.com/p/sympy/issues/detail?id=3272
Issue 3345 has been merged into this issue.
--
You received this message because you are subscribed to the Google Groups
Comment #23 on issue 3272 by ness...@gmail.com: Python 3.3 test failures
http://code.google.com/p/sympy/issues/detail?id=3272
Issue 3345 has been merged into this issue.
--
You received this message because you are subscribed to the Google Groups
sympy-issues group.
To post to this group,
Comment #24 on issue 3272 by smi...@gmail.com: Python 3.3 test failures
http://code.google.com/p/sympy/issues/detail?id=3272
Issue 3345 has been merged into this issue.
--
You received this message because you are subscribed to the Google Groups
sympy-issues group.
To post to this group, send
Comment #25 on issue 3272 by smi...@gmail.com: Python 3.3 test failures
http://code.google.com/p/sympy/issues/detail?id=3272
https://github.com/sympy/sympy/pull/1462
--
You received this message because you are subscribed to the Google Groups
sympy-issues group.
To post to this group, send
Comment #21 on issue 3272 by asmeu...@gmail.com: Python 3.3 test failures
http://code.google.com/p/sympy/issues/detail?id=3272
It seems the test_Subs error is a result of me having test_functions.py
left over in py3k-sympy (as opposed to test_function.py). I'm looking into
the
Comment #18 on issue 3272 by smi...@gmail.com: Python 3.3 test failures
http://code.google.com/p/sympy/issues/detail?id=3272
I believe that all error-raising randomization problems have been fixed now.
--
You received this message because you are subscribed to the Google Groups
sympy-issues
Comment #19 on issue 3272 by asmeu...@gmail.com: Python 3.3 test failures
http://code.google.com/p/sympy/issues/detail?id=3272
There are still some in Python 3.3 at least:
sympy/core/tests/test_functions.py:test_Subs
Updates:
Labels: NeedsReview
Comment #20 on issue 3272 by asmeu...@gmail.com: Python 3.3 test failures
http://code.google.com/p/sympy/issues/detail?id=3272
Fixing some of these at https://github.com/sympy/sympy/pull/1455.
--
You received this message because you are subscribed to the
Issue 3272: Python 3.3 test failures
http://code.google.com/p/sympy/issues/detail?id=3272
This issue is now blocking issue sympy:2855.
See http://code.google.com/p/sympy/issues/detail?id=2855
--
You received this message because you are listed in the owner
or CC fields of this issue, or because
Comment #17 on issue 3272 by asmeu...@gmail.com: Python 3.3 test failures
http://code.google.com/p/sympy/issues/detail?id=3272
A bit of good news: I just tested Python 3.3b1, and the doctests no longer
crash, thanks to Ronan's patch. A big thanks for that.
--
You received this message
Comment #15 on issue 3272 by asmeu...@gmail.com: Python 3.3 test failures
http://code.google.com/p/sympy/issues/detail?id=3272
At https://github.com/sympy/sympy/pull/1379 we have an important first
step: hash randomization is enabled by default in all test and doctest runs
(with a seed
Updates:
Blockedon: sympy:3301
Comment #14 on issue 3272 by asmeu...@gmail.com: Python 3.3 test failures
http://code.google.com/p/sympy/issues/detail?id=3272
(No comment was entered for this change.)
--
You received this message because you are subscribed to the Google Groups
Updates:
Labels: Milestone-Release0.7.2
Comment #7 on issue 3272 by asmeu...@gmail.com: Python 3.3 test failures
http://code.google.com/p/sympy/issues/detail?id=3272
I've started a branch where I am fixing these issues. So far I've only
fixed the Decimal private attributes problem.
Updates:
Labels: Python3
Comment #8 on issue 3272 by vlada.pe...@gmail.com: Python 3.3 test failures
http://code.google.com/p/sympy/issues/detail?id=3272
Could we modify our test runner to print out the result *and* what it's
supposed to be in case of an AssertionError? It would make
Comment #9 on issue 3272 by asmeu...@gmail.com: Python 3.3 test failures
http://code.google.com/p/sympy/issues/detail?id=3272
I'll see if it's easy to do. I know that py.test would do it for us if we
used that. I've also been researching how to get and set the random hash
seed, and I will
Comment #10 on issue 3272 by ronan.l...@gmail.com: Python 3.3 test failures
http://code.google.com/p/sympy/issues/detail?id=3272
Here's the result of a py.test run - which shows what the actual issues are.
Attachments:
test.log 97.5 KB
--
You received this message because you are
Comment #11 on issue 3272 by vlada.pe...@gmail.com: Python 3.3 test failures
http://code.google.com/p/sympy/issues/detail?id=3272
Unless I'm missing something, it should be possible to set the
PYTHONHASHSEED command-line option (new in 3.2.3 and 3.3 I guess) and fix
the seed for hash
Comment #12 on issue 3272 by ronan.l...@gmail.com: Python 3.3 test failures
http://code.google.com/p/sympy/issues/detail?id=3272
The metaclass thing under doctest looks indeed like a bug of 3.3, cf.
http://bugs.python.org/issue14938
--
You received this message because you are subscribed to
Comment #13 on issue 3272 by asmeu...@gmail.com: Python 3.3 test failures
http://code.google.com/p/sympy/issues/detail?id=3272
Thanks for looking into that. That would have taken me some time to figure
out (though now that I see it, I do remember seeing the odd
__import__(__init__) thing
Comment #5 on issue 3272 by smi...@gmail.com: Python 3.3 test failures
http://code.google.com/p/sympy/issues/detail?id=3272
An assertion that the number is not in (Decimal('Infinity'),
Decimal('NaN')) could be used instead, perhaps.
--
You received this message because you are subscribed to
Comment #6 on issue 3272 by asmeu...@gmail.com: Python 3.3 test failures
http://code.google.com/p/sympy/issues/detail?id=3272
Oh is that what it tests? According to the documentation, is_finite will
do that.
--
You received this message because you are subscribed to the Google Groups
Status: Valid
Owner:
Labels: Type-Defect Priority-Critical Testing
New issue 3272 by asmeu...@gmail.com: Python 3.3 test failures
http://code.google.com/p/sympy/issues/detail?id=3272
There are many test failures in Python 3.3. It's still in alpha stage, so
you have to download it from
Comment #1 on issue 3272 by asmeu...@gmail.com: Python 3.3 test failures
http://code.google.com/p/sympy/issues/detail?id=3272
Also we need to make sure that use2to3 works with Python 3.3 (it seems to
work for me, but there may be subtle issues that crop up).
--
You received this message
Comment #2 on issue 3272 by asmeu...@gmail.com: Python 3.3 test failures
http://code.google.com/p/sympy/issues/detail?id=3272
Here's a full list of test failures (I didn't get the expand hang this
time; whether it's because of luck with the hash randomization or because I
ran use2to3 with
Comment #3 on issue 3272 by asmeu...@gmail.com: Python 3.3 test failures
http://code.google.com/p/sympy/issues/detail?id=3272
OK, I just manually verified with a diff that 2to3 produces the exact same
output with Python 3.3 as with Python 3.2. So that is not an issue.
--
You received this
Updates:
Cc: smi...@gmail.com
Comment #4 on issue 3272 by asmeu...@gmail.com: Python 3.3 test failures
http://code.google.com/p/sympy/issues/detail?id=3272
The is_special problem is because Decimal no longer has that private
attribute. Chris, you added that assertion. Can you
27 matches
Mail list logo
