This pull request [fails](http://travis-ci.org/sympy/sympy/builds/2050388)
(merged 2b0aa284 into 65b65820).
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1457#issuecomment-7533348
--
You received this message because you are subscribed to the Google
On Mon, Aug 6, 2012 at 11:38 PM, Tom Bachmann
wrote:
> @smichr specifically: From the examples you show, I agree there does not seem
> to be a problem with combsimp any more.
> @smichr generally: *awesome* work.
Thanks...now I've got to do some awesome work here! Before checking
out on this, I
This pull request [passes](http://travis-ci.org/sympy/sympy/builds/2050704)
(merged 851886ed into 65b65820).
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1457#issuecomment-7534297
--
You received this message because you are subscribed to the Google
This massive overhaul of the orthogonal polynomials module is ready for serious
review now.
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1457#issuecomment-7534697
--
You received this message because you are subscribed to the Google Groups
"sympy-p
This pull request [fails](http://travis-ci.org/sympy/sympy/builds/2050993)
(merged 8f5ba4a2 into 65b65820).
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1457#issuecomment-7535550
--
You received this message because you are subscribed to the Google
This pull request [passes](http://travis-ci.org/sympy/sympy/builds/2051041)
(merged 82a723cc into 65b65820).
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1457#issuecomment-7536124
--
You received this message because you are subscribed to the Google
Ha, nice! Awesome work, thanks. From quick look it looks excellent. I will give
it a thorough review soon.
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1457#issuecomment-7536947
--
You received this message because you are subscribed to the Google G
Thanks!
We should review/merge PR 1433 first.
And no need to hurry, I'll be off for a few days.
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1457#issuecomment-7538298
--
You received this message because you are subscribed to the Google Groups
"sym
I.e.
```ImmutableMatrix.__add__ = MatrixBase.__add__```
instead of
```ImmutableMatrix.__add__ = MatExpr.__add__```
This causes ``ImmutableMatrix * ImmutableMatrix => ImmutableMatrix```
instead of ```ImmutableMatrix * ImmutableMatrix => MatExpr```
I.e. ImmutableMatrices evaluate by default.
You
This pull request [passes](http://travis-ci.org/sympy/sympy/builds/2052585)
(merged e3a033ee into 65b65820).
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1467#issuecomment-7539882
--
You received this message because you are subscribed to the Google
Would it also work to just swap the superclasses?
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1467#issuecomment-7541345
--
You received this message because you are subscribed to the Google Groups
"sympy-patches" group.
To post to this group, sen
Okay, now it should print each prompt interspersed with the results. I've
pushed the changes to the server.
Also, I fixed the bug where preexecs weren't getting evaluated...turns out I
was overwriting a variable.
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sy
You accidentally removed app.yaml
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy-live/pull/59#issuecomment-7542001
--
You received this message because you are subscribed to the Google Groups
"sympy-patches" group.
To post to this group, send email to symp
Can you update the live demo?
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy-live/pull/59#issuecomment-7542027
--
You received this message because you are subscribed to the Google Groups
"sympy-patches" group.
To post to this group, send email to sympy-pa
Sorry, fixed.
Still some issues:
- Code like
>>> def ctimesd():
... """
... This function returns whatever c is times whatever d is.
... """
... return c*d
isn't getting executed properly.
- Tracebacks don't show the original prompt
---
Reply to thi
I have pushed the changes to the demo at http://docs.sympy.org/live-demo/ and
at http://59.sympy-live-tests.appspot.com/ .
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy-live/pull/59#issuecomment-7542054
--
You received this message because you are subscri
OK, so I guess the behavior should be like this: If there are multiple things
in the same input, it should only print the last one. This is how even the
IPython notebook works. For the Sphinx extension, it should parse the `>>>`
and `...` to determine what should be executed as one block.
Okay, so to clarify: revert to the old behavior (only the results of the last
statement are printed), except for Sphinx?
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy-live/pull/59#issuecomment-7542388
--
You received this message because you are subscribe
Well, even for sphinx. The point is how you parse the sphinx input. Each
`>>>` plus any additional `...` should be run as a separate block. I guess if
the queueing ends up being tricky, you can just jump to executing one prompt at
a time, and worry about how to queue up whole blocks later.
-
Oh, okay. So instead of a backend change, change the Sphinx frontend to
evaluate each block separately.
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy-live/pull/59#issuecomment-7542474
--
You received this message because you are subscribed to the Google G
In that case we would have to explicitly make some MatExpr methods default. For
example MatrixBase has a subs method.
In general I prefer to keep MatExpr the default because I know it better and
trust it much more than MatrixBase. MatExpr is much simpler and closer to
Basic.
It could be that
Tests?
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1467#issuecomment-7543986
--
You received this message because you are subscribed to the Google Groups
"sympy-patches" group.
To post to this group, send email to sympy-patches@googlegroups.com.
To
@rlamy is this done correctly? Should it perhaps use `super()`?
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1467#issuecomment-7544056
--
You received this message because you are subscribed to the Google Groups
"sympy-patches" group.
To post to th
This is a just a framework of functions that will replace plot which took care
of all the possible plots.
The behaviour that is expected is provided in the docstrings. This pull request
was made to get an opinion
on the names of the functions and the behaviour that has to be expected of
these fu
This pull request [fails](http://travis-ci.org/sympy/sympy/builds/2054782)
(merged 85cd5a99 into 65b65820).
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1468#issuecomment-7544733
--
You received this message because you are subscribed to the Google
25 matches
Mail list logo
