Re: Issue 1616 in sympy: Bug in subs

2011-12-16 Thread sympy
Comment #22 on issue 1616 by asmeu...@gmail.com: Bug in subs http://code.google.com/p/sympy/issues/detail?id=1616 Yes, it was. -- You received this message because you are subscribed to the Google Groups "sympy-issues" group. To post to this group, send email to sympy-issues@googlegroups.com.

Re: Issue 1616 in sympy: Bug in subs

2011-12-13 Thread sympy
Comment #21 on issue 1616 by smi...@gmail.com: Bug in subs http://code.google.com/p/sympy/issues/detail?id=1616 Thanks for checking this out, SgtMook. Did you undertake this as a GCI exercise? -- You received this message because you are subscribed to the Google Groups "sympy-issues" group.

Re: Issue 1616 in sympy: Bug in subs

2011-12-13 Thread sympy
Updates: Status: Fixed Comment #20 on issue 1616 by asmeu...@gmail.com: Bug in subs http://code.google.com/p/sympy/issues/detail?id=1616 Thanks. -- You received this message because you are subscribed to the Google Groups "sympy-issues" group. To post to this group, send email to sympy

Re: Issue 1616 in sympy: Bug in subs

2011-12-13 Thread sympy
Comment #19 on issue 1616 by sgtmook...@gmail.com: Bug in subs http://code.google.com/p/sympy/issues/detail?id=1616 I run the coverage_report.py on core.mul, and the _eval_subs function is well covered. In addition, no coverage increase is found by the tests in comment 10. -- You received

Re: Issue 1616 in sympy: Bug in subs

2011-10-24 Thread sympy
Updates: Labels: CodeInCategory-QA Comment #15 on issue 1616 by asmeu...@gmail.com: Bug in subs http://code.google.com/p/sympy/issues/detail?id=1616 For the Code-In issues, please add both a difficulty and a category. Issues like this that require tests or coverage tests fall under QA

Re: Issue 1616 in sympy: Bug in subs

2011-10-24 Thread sympy
Updates: Labels: CodeInDifficulty-Easy Comment #14 on issue 1616 by smi...@gmail.com: Bug in subs http://code.google.com/p/sympy/issues/detail?id=1616 (No comment was entered for this change.) -- You received this message because you are subscribed to the Google Groups "sympy-issues" g

Re: Issue 1616 in sympy: Bug in subs

2011-06-14 Thread sympy
Updates: Labels: EasyToFix Comment #13 on issue 1616 by smi...@gmail.com: Bug in subs http://code.google.com/p/sympy/issues/detail?id=1616 (No comment was entered for this change.) -- You received this message because you are subscribed to the Google Groups "sympy-issues" group. To pos

Re: Issue 1616 in sympy: Bug in subs

2011-02-06 Thread sympy
Comment #12 on issue 1616 by smi...@gmail.com: Bug in subs http://code.google.com/p/sympy/issues/detail?id=1616 These all pass in current master. The coverage should be checked to see if these are necessary. -- You received this message because you are subscribed to the Google Groups "sympy

Re: Issue 1616 in sympy: Bug in subs

2009-12-02 Thread sympy
Updates: Labels: Matching Comment #11 on issue 1616 by ronan.l...@gmail.com: Bug in subs http://code.google.com/p/sympy/issues/detail?id=1616 (No comment was entered for this change.) -- You received this message because you are listed in the owner or CC fields of this issue, or because

Issue 1616 in sympy: Bug in subs

2009-09-15 Thread codesite-noreply
Comment #10 on issue 1616 by wflynny: Bug in subs http://code.google.com/p/sympy/issues/detail?id=1616 Here is a slightly updated test_subs, one that I said I would send at the end of August. It basically adds basic test cases that were causing examples in PyDy to fail, only a couple though