Should we include the IPython version too? Otherwise, it looks fine.
Aaron Meurer
On Mar 17, 2010, at 4:24 PM, Ondrej Certik wrote:
> Hi Fernando,
>
> On Fri, Jan 1, 2010 at 12:47 PM, Fernando Perez
> wrote:
>> Hey Ondrej,
>>
>> I got that screenshot from Davi
It does not rebase trivially over master, due to mpmath being updated.
Aaron Meurer
On Mar 17, 2010, at 4:27 PM, Ondrej Certik wrote:
> On Wed, Mar 17, 2010 at 2:13 PM, Priit Laes wrote:
>> Hey!
>>
>> Now that auditing support is in master, I went out there and picke
I was actually referring to Priit's branch, but I guess polys will need to
fixed too. :)
Aaron Meurer
On Mar 17, 2010, at 5:10 PM, Mateusz Paprocki wrote:
> Hi,
>
> On Wed, Mar 17, 2010 at 04:59:50PM -0600, Aaron Meurer wrote:
>> It does not rebase trivially over master,
Just so you know, you've replied to the forwarded email to the patches
list, which does not automatically create an issue in the issue
tracker (this only works for replies to direct emails from
sy...@googlecode.com).
Aaron Meurer
On Tue, Jul 12, 2011 at 6:25 AM, Alan Bromborsky wrote:
&g
else
there might too).
Aaron Meurer
2011/9/19 Ondřej Čertík :
> Hi Markus,
>
> Thanks for your patch. Would you mind sending us a pull request
> against the official repository?
>
> https://github.com/sympy/sympy
>
> Then we can easily review it and push it in.
> Thank
In case anyone's wondering what this is, this should make new pull
request notifications show up on this list.
Aaron Meurer
On Jun 19, 2012, at 5:25 PM, SymPy wrote:
> Developers with Push Access to Everything grants 16 users push access to 8
> repositories.
> View team: http
This fixes issue 3282, and is an alternative to pull request #1364.
You can merge this Pull Request by running:
git pull https://github.com/asmeurer/sympy circuitutils
Or you can view, comment on it, or merge it online at:
https://github.com/sympy/sympy/pull/1366
-- Commit Summary --
* Us
This also fixes a test failure (issue 3293).
You can merge this Pull Request by running:
git pull https://github.com/asmeurer/sympy auto_symbols_fix
Or you can view, comment on it, or merge it online at:
https://github.com/sympy/sympy/pull/1367
-- Commit Summary --
* Fix automatic symbols
This enables testing with hash randomization. Hash randomization is a new
feature of Python where hash values are randomized, so as to prevent against a
hash collision security issue. It causes many test failures (see [issue
3272](http://code.google.com/p/sympy/issues/detail?id=3272)) because
I am going to just commit this as I go. Feel free to review and merge at any
time.
You can merge this Pull Request by running:
git pull https://github.com/asmeurer/sympy python3.3
Or you can view, comment on it, or merge it online at:
https://github.com/sympy/sympy/pull/1394
-- Commit Su
As before, merge at any time (though please make sure that the Travis tests
pass first).
You can merge this Pull Request by running:
git pull https://github.com/asmeurer/sympy python3.3
Or you can view, comment on it, or merge it online at:
https://github.com/sympy/sympy/pull/1399
-- Comm
I'm attempting to fix all the errors in the Sphinx docs. I'm not done yet, but
feel free to start reviewing.
You can merge this Pull Request by running:
git pull https://github.com/asmeurer/sympy html-docs
Or you can view, comment on it, or merge it online at:
https://github.com/sympy/sym
See `python --help`.
You can merge this Pull Request by running:
git pull https://github.com/asmeurer/sympy hash_seed
Or you can view, comment on it, or merge it online at:
https://github.com/sympy/sympy/pull/1402
-- Commit Summary --
* Use the actual range of values for PYTHONHASHSEED
-
Just a little gotcha I noticed recently.
You can merge this Pull Request by running:
git pull https://github.com/asmeurer/sympy-bot testcommand
Or you can view, comment on it, or merge it online at:
https://github.com/sympy/sympy-bot/pull/114
-- Commit Summary --
* Add a note about the n
Just some docs updates, inspired by #55. No need to re-upload to the app engine
after pushing this.
You can merge this Pull Request by running:
git pull https://github.com/asmeurer/sympy-live docs
Or you can view, comment on it, or merge it online at:
https://github.com/sympy/sympy-live/pu
This looks much better on high resolution devices such as the retina MacBook
Pro.
In order to keep the exact aspect ratio of the logo I had, it had to be made a
little bigger. I made the "SymPy" header font a little bigger too to
compensate.
A corresponding pull request to SymPy Live is forthcom
This corresponds to sympy/sympy.github.com#53
I could not get the mobile logo to stop being squished. I don't know how to
fix that.
You can merge this Pull Request by running:
git pull https://github.com/asmeurer/sympy-live logo
Or you can view, comment on it, or merge it online at:
http
OK, here it comes...
See the commit message of e716d20 for the description of the bulk of the
changes here, and the motivation for all the changes.
This is **not** ready to be merged yet. There are still test failures. For
one thing, I need #1427 before I can attempt to fix some of the failu
Now that I have a computer with eight cores, I'd like to be able to run the bot
tests in parallel. Something like a command line option `--cores N` with would
spawn up to `N` processes. Can this be done using the current subprocess
framework, or would we need to use the multiprocessing module?
#35 is related to this.
We should save all stdout and stderr to the log (in addition to showing it on
the screen). Right now, only the test run is saved, but this quite often is
not enough, because if there is some bug in sympy-bot (for example), the output
will not be there. And sometimes it
You can merge this Pull Request by running:
git pull https://github.com/asmeurer/sympy nsolve-fix
Or you can view, comment on it, or merge it online at:
https://github.com/sympy/sympy/pull/1438
-- Commit Summary --
* nsolve uses free_symbols instead of atoms(Symbol) (issue 3309)
-- File C
out using this list,
by starring the issue in Google Code or clicking "Enable notifications
for this pull request" at the bottom of the page on GitHub.
Hopefully I've changed the subscription permissions correctly. If you
notice that this list isn't sending out the correct
```pytb
$./sympy-bot list
> Using config file /Users/aaronmeurer/.sympy/sympy-bot.conf
> Loaded configuration file
Traceback (most recent call last):
File "./sympy-bot", line 502, in
main()
File "./sympy-bot", line 150, in main
val = getattr(options, i)
AttributeError: 'Namespace' obje
Fixing some of the remaining test failures in master.
You can merge this Pull Request by running:
git pull https://github.com/asmeurer/sympy test_failure_fixes
Or you can view, comment on it, or merge it online at:
https://github.com/sympy/sympy/pull/1455
-- Commit Summary --
* XFAIL th
This pull request refactors SymPy-Bot a little bit.
Two chief things were done here (unfortunately it would have been too much work
to split them into separate commits):
1. SymPy-Bot now avoids doing redundant things more than once. In particular,
for each pull request, the merge is attempted
This fixes the problem where [OK] was not being printed with --no-colors and
many colored text was (see also issue 3349).
You can merge this Pull Request by running:
git pull https://github.com/asmeurer/sympy test_colors
Or you can view, comment on it, or merge it online at:
https://github.
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
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
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.
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.
-
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
> +The plotting uses an adaptive algorithm which samples recursively to
> +accurately plot the plot. The adaptive algorithm uses a random point near
> +the midpoint of two points that has to be further sampled. Hence the same
> +plots can appear slightly different.
> +
> +Usage
> +
> +The plotting uses an adaptive algorithm which samples recursively to
> +accurately plot the plot. The adaptive algorithm uses a random point near
> +the midpoint of two points that has to be further sampled. Hence the same
> +plots can appear slightly different.
> +
> +Us
> +``xlim`` : tuple of two floats, denoting the x - axis limits.
> +
> +``ylim`` : tuple of two floats, denoting the y - axis limits.
> +
> +Examples
> +
> +>>> plot_line(x**2, (x, -5, 5))
> +
> +Multiple plots
> +>>> plot_line((x**2, (x, -6, 6)), (x, (x, -5, 5))
Why create a new file for this?
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1468#issuecomment-7545659
--
You received this message because you are subscribed to the Google Groups
"sympy-patches" group.
To post to this group, send email to sympy-pat
Or you could test for specific matrices.
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1467#issuecomment-7562891
--
You received this message because you are subscribed to the Google Groups
"sympy-patches" group.
To post to this group, send email to
This fixes http://code.google.com/p/sympy/issues/detail?id=3182. There is now
a `-i` option to isympy, which allows automatic wrapping of integer literals
with Integer. The result is that things like `1/2` will be converted to
`Rational(1, 2)` automatically. For example:
```py
$./bin/isympy
OK, some tests added.
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1470#issuecomment-7569394
--
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@googl
OK, I'll merge it then.
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1454#issuecomment-7569421
--
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@goo
Huh, apparently binary literals were added in Python 2.6. I did not know that.
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1470#issuecomment-7569709
--
You received this message because you are subscribed to the Google Groups
"sympy-patches" group
**[SymPy Bot][sympy-bot] Summary**: :red_circle: There were test failures
(merged raoulb/lazy_orthogonal_polynomials
(82a723cc03d466ecd6da09896abccdc76e24be4c) into master
(c7a4a4a39b9154670f218265e76fd778f6bf487b)).
@raoulb: Please fix the test failures.
**Build HTML Docs:** :red_circle: Ther
**[SymPy Bot][sympy-bot] Summary**: :red_circle: There were test failures
(merged asmeurer/test_colors (f8e8af88029d992b6267dc0c6fc29f90e436f480) into
master (c7a4a4a39b9154670f218265e76fd778f6bf487b)).
@asmeurer: Please fix the test failures.
**Build HTML Docs:** :red_circle: There were test
**[SymPy Bot][sympy-bot] Summary**: :red_circle: There were test failures
(merged scolobb/ct1-diagram-layout (47b7640842f9d79acbc9f2e50cd80b5880828ece)
into master (c7a4a4a39b9154670f218265e76fd778f6bf487b)).
@scolobb: Please fix the test failures.
**Build HTML Docs:** :red_circle: There were t
@scolobb I think these doc failures are due to this branch.
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1429#issuecomment-7570118
--
You received this message because you are subscribed to the Google Groups
"sympy-patches" group.
To post to this gr
It appears that defining a function deletes all user-defined names.
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy-live/pull/59#issuecomment-7571543
--
You received this message because you are subscribed to the Google Groups
"sympy-patches" group.
To post
I think the problem is in the split function. It should not split out the last
line in a function definition.
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy-live/pull/59#issuecomment-7571871
--
You received this message because you are subscribed to the G
So I *think* the correct solution is to check in split if the last line begins
with whitespace, and to not include it in the eval code if it does. But I'm
still trying to understand the code here, so it may not be right.
---
Reply to this email directly or view it on GitHub:
https://github.com/
> +from tokenize import generate_tokens, untokenize, NUMBER, NAME, OP
> +from StringIO import StringIO
> +
> +result = []
> +g = generate_tokens(StringIO(s).readline) # tokenize the string
> +for toknum, tokval, _, _, _ in g:
> +if toknum == NUMBER and '.' not in tokv
> +from tokenize import generate_tokens, untokenize, NUMBER, NAME, OP
> +from StringIO import StringIO
> +
> +result = []
> +g = generate_tokens(StringIO(s).readline) # tokenize the string
> +for toknum, tokval, _, _, _ in g:
> +if toknum == NUMBER and '.' not in tokv
> +Example
> +===
> +
> +>>> from sympy.interactive.session import int_to_Integer
> +>>> from sympy import Integer
> +>>> s = '1.2 + 1/2 - 0x12 + a1'
> +>>> int_to_Integer(s)
> +'1.2 +Integer (1 )/Integer (2 )-Integer (0x12 )+a1 '
> +>>> s = 'print (1/2)'
> +
> @@ -129,6 +129,27 @@ COMMAND LINE OPTIONS
> example, if you define a function in isympy with an undefined
> Symbol, it will not work.
>
> +See also the -i and -I options.
> +
> +-i, --int-to-Integer
> +
> +Automatically wrap int literals with Integer. This makes it so that
>
Well, that doesn't seem to work. So I'm at a loss here.
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy-live/pull/59#issuecomment-7572186
--
You received this message because you are subscribed to the Google Groups
"sympy-patches" group.
To post to this gr
> +below_eye = zeros(n+m,n)
> +A =
> (self.mass_matrix).col_join((self._m_cd).row_join(zeros(m,m)))
> +below_I = below_eye.row_join(A)
> +return I.col_join(below_I)
> +else:
> + A = row1.col_join(row2)
> + return A
> +
> +
Anyway, you don't have to fix that here. It's a bug in master, not a
regression, so it doesn't have any barring on this PR. Are you planning to do
more here, or should I review to merge?
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy-live/pull/59#issuecom
**[SymPy Bot][sympy-bot] Summary**: :red_circle: There were test failures
(merged ness01/agca9 (68dab625d5d5cd254132977a6873188ab68de099) into master
(bd49e6a0b3815b22c559f18535c0e48ab6dfec12)).
@ness01: Please fix the test failures.
**Interpreter 1**: :red_circle: There were test
[failures](h
**[SymPy Bot][sympy-bot] Summary**: :red_circle: There were test failures
(merged jrioux/french-tutorial (728107ee09bf97b80002f366eb7fdfc57817000e) into
master (0d88b25d001e4bf91d5ec36fddd06eb6cba77348)).
@jrioux: Please fix the test failures.
**Build HTML Docs:** :red_circle: There were test
**[SymPy Bot][sympy-bot] Summary**: :red_circle: There were test failures
(merged catchmrbharath/restructured_plot
(d9efa1ea0a5efa812fe4e76e308cf3f6068b69c0) into master
(0d88b25d001e4bf91d5ec36fddd06eb6cba77348)).
@catchmrbharath: Please fix the test failures.
**Interpreter 1**: :red_circle:
**[SymPy Bot][sympy-bot] Summary**: :red_circle: There were test failures
(merged raoulb/lazy_orthogonal_polynomials
(82a723cc03d466ecd6da09896abccdc76e24be4c) into master
(bd49e6a0b3815b22c559f18535c0e48ab6dfec12)).
@raoulb: Please fix the test failures.
**Interpreter 1**: :eight_spoked_aster
**[SymPy Bot][sympy-bot] Summary**: :red_circle: There were test failures
(merged asmeurer/test_colors (f8e8af88029d992b6267dc0c6fc29f90e436f480) into
master (bd49e6a0b3815b22c559f18535c0e48ab6dfec12)).
@asmeurer: Please fix the test failures.
**Interpreter 1**: :eight_spoked_asterisk: All test
**[SymPy Bot][sympy-bot] Summary**: :red_circle: There were test failures
(merged asmeurer/autorat (c1aaae19b1503bc5fe6e38de5193edd2c99843f0) into master
(bd49e6a0b3815b22c559f18535c0e48ab6dfec12)).
@asmeurer: Please fix the test failures.
**Interpreter 1**: :red_circle: There were test
[failu
> +"""Matrix Trace
> +
> +Represents the trace of a matrix expression.
> +
> +>>> from sympy import MatrixSymbol, Trace, eye
> +>>> A = MatrixSymbol('A', 3, 3)
> +>>> Trace(A)
> +Trace(A)
> +
> +>>> Trace(eye(3))
> +3
> +"""
> +is_Trace = True
> +def __ne
I also don't see anything in master. Perhaps this is yet another bug in my
sympy-bot branch. Let me figure it out.
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1429#issuecomment-7598508
--
You received this message because you are subscribed to th
Well, now it's passing for me even in SymPy bot. So maybe it was just fixed
(?). Anyway, if it doesn't show up again, I'm not going to worry about it.
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1429#issuecomment-7598599
--
You received this mess
Ahh, good catch. I made the assumption that a floating point literal must
contain a `.`, but this is clearly not true. I guess I also missed complex
literals. Can you think of any other cases of a float literal? Or maybe there
is something in the standard library that automates this.
---
Rep
Pushed a fix.
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1470#issuecomment-7599280
--
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.
I guess I can just `eval` it and check the type. Let me see if that is not too
slow.
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1470#issuecomment-7600235
--
You received this message because you are subscribed to the Google Groups
"sympy-patches
The way I'm doing it seems to be much faster, so I'll just stick with it for
now.
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1470#issuecomment-7600391
--
You received this message because you are subscribed to the Google Groups
"sympy-patches" gr
I'd like feedback before I do this. I just realized that we can save even more
space. What if the output looked like this:
**[SymPy Bot][sympy-bot] Summary**: :red_circle: There were test failures
(merged mrocklin/trace (71ca3be7d64076064448d8210ba1f51063887cb7) into master
(96259182f9fcc3a63
Code looks OK. Let me test.
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1473#issuecomment-7601046
--
You received this message because you are subscribed to the Google Groups
"sympy-patches" group.
To post to this group, send email to sympy-patche
**[SymPy Bot][sympy-bot] Summary**: :eight_spoked_asterisk: All tests have
passed (merged jrioux/tests (1bf46b5a5253a036ba3a67752b57c8b01b4b27ba) into
master (0d88b25d001e4bf91d5ec36fddd06eb6cba77348)).
**Interpreter 1**: :eight_spoked_asterisk: All tests have
[passed](http://reviews.sympy.org/
**[SymPy Bot][sympy-bot] Summary**: :red_circle: There were test failures
(merged jrioux/tests (1bf46b5a5253a036ba3a67752b57c8b01b4b27ba) into master
(0d88b25d001e4bf91d5ec36fddd06eb6cba77348)).
@jrioux: Please fix the test failures.
**Interpreter 1**: :red_circle: There were test
[failures](h
That test failure is insignificant. The important thing there is that the
randomization is off, because I set the hash seed to 0. I'm also doing a full
test run, and when that comes in I'll merge this.
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1
OK, done. I don't see how the summaries could be made any smaller now, without
removing what is IMHO vital information, or making the formatting much harder
to read.
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy-bot/pull/123#issuecomment-7602543
--
You
OK, the execution here seems to work OK. There are just a couple of user
interface issues. First, the "Run in SymPy Live" should now obviously be
changed. For one thing, it overlaps with the first prompt. Also, it should
probably also be called "Run block in SymPy Live". Is it possible to p
The copy option for the run whole block just copies the first text, but then
executes everything. I think it should just copy everything (and not do any
queueing in that case).
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy-live/pull/59#issuecomment-760280
The problematic doctest from "If you define a circular relationship, you will
get a RuntimeError." in the gotchas seems to have disappeared. Is that because
of the extension or unrelated?
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy-live/pull/59#issuecom
Probably all of the master ImmutableMatrix behavior is useful, which is why we
probably need an UnevaluatedMatrix object. I should be trivial to do,
actually. Just rename ImmutableMatrix to UnevaluatedMatrix, and then make a
subclass called ImmutableMatrix and override the operators there.
--
Was there anything that was not working for which a test can be added?
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1471#issuecomment-7603788
--
You received this message because you are subscribed to the Google Groups
"sympy-patches" group.
To post
Does this change the rendered output?
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1472#issuecomment-7604017
--
You received this message because you are subscribed to the Google Groups
"sympy-patches" group.
To post to this group, send email to sym
**[SymPy Bot][sympy-bot] Summary**: :red_circle: There were test failures
(merged scolobb/fix-categories.rst (a587daec52cdb566aee21b512a691a6044506ccd)
into master (0d88b25d001e4bf91d5ec36fddd06eb6cba77348)).
@scolobb: Please fix the test failures.
**Build HTML Docs:** :red_circle: There were tes
It appears to be just the `_remove_gens`. I don't even understand why the
private functions are included in the docs. @amekelov, can you comment?
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1472#issuecomment-7604062
--
You received this message b
**[SymPy Bot][sympy-bot] Summary**: :red_circle: There were test failures
(merged jrioux/tests (1bf46b5a5253a036ba3a67752b57c8b01b4b27ba) into master
(0d88b25d001e4bf91d5ec36fddd06eb6cba77348)).
@jrioux: Please fix the test failures.
**Interpreter 1**: :eight_spoked_asterisk: All tests have
[p
Seems to render OK to me. I'm merging...
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1472#issuecomment-7604091
--
You received this message because you are subscribed to the Google Groups
"sympy-patches" group.
To post to this group, send email to
OK, merging...
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1473#issuecomment-7604137
--
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
Right. I was also thinking of replacing **Interpreter 1** with **Python 3.2.3
(64-bit)**. And I'm not sure if the operating system is super important, so it
can probably be removed (it's not even in the test header in the full report).
---
Reply to this email directly or view it on GitHub:
http
Regarding the order of the symbol, I did play with putting it before **SymPy
Bot** (see for example
https://github.com/asmeurer/GitHub-Issues-Test/issues/6#issuecomment-7473378),
and it just didn't look good. I don't know how it would look for the
interpreters, but probably it would look best
This will make things easier to work with with the Sphinx SymPy Live
extension.
You can merge this Pull Request by running:
git pull https://github.com/asmeurer/sympy docs-sidebar
Or you can view, comment on it, or merge it online at:
https://github.com/sympy/sympy/pull/1474
-- Commit Summ
See https://github.com/sympy/sympy/pull/1474 for the collapsible sidebar.
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy-live/pull/59#issuecomment-7604421
--
You received this message because you are subscribed to the Google Groups
"sympy-patches" group.
T
**[SymPy Bot][sympy-bot] Summary**: :red_circle: There were test failures
(merged asmeurer/docs-sidebar (9399e0d9e20c9b6b0b2404a16e713c3bc1ed83a0) into
master (15c2c89ad53f5715d7d42a9daf29ae819a8779fb)).
@asmeurer: Please fix the test failures.
**Build HTML Docs:** :red_circle: There were test
[
Hmm. Wasn't expecting that.
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1474#issuecomment-7604994
--
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
**[SymPy Bot][sympy-bot] Summary**: :eight_spoked_asterisk: All tests have
passed (merged asmeurer/docs-sidebar (9399e0d9e20c9b6b0b2404a16e713c3bc1ed83a0)
into master (15c2c89ad53f5715d7d42a9daf29ae819a8779fb)).
**Build HTML Docs:** :eight_spoked_asterisk: All tests have
[passed](http://reviews.
Interesting...
I've changed the default command to `make clean; make html-errors` at
sympy/sympy-bot#123. Hopefully that will clear out a lot of these strange and
spurious doc building errors.
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1474#iss
**[SymPy Bot][sympy-bot] Summary**: :eight_spoked_asterisk: All tests have
passed (merged scolobb/fix-categories.rst
(a587daec52cdb566aee21b512a691a6044506ccd) into master
(15c2c89ad53f5715d7d42a9daf29ae819a8779fb)).
**Build HTML Docs:** :eight_spoked_asterisk: All tests have
[passed](http://re
That time, I changed the default docs building command to `make clean; make
html-errors`. Hopefully that will eliminate spurious errors.
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy/pull/1472#issuecomment-7605152
--
You received this message because y
What about the fetch and merge failure text?
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy-bot/pull/123#issuecomment-7607021
--
You received this message because you are subscribed to the Google Groups
"sympy-patches" group.
To post to this group, send em
I think it would be better to do
:redcircle: **Python 3.2.1 (64-bit)**: Pass
It's strange not seeing what's what, especially with the docs build.
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy-bot/pull/123#issuecomment-7607063
--
You received this messag
Or
**Python 3.2.1 (64-bit)**: :red_circle: Fail
---
Reply to this email directly or view it on GitHub:
https://github.com/sympy/sympy-bot/pull/123#issuecomment-7607074
--
You received this message because you are subscribed to the Google Groups
"sympy-patches" group.
To post to this group, se
**[SymPy Bot][sympy-bot] Summary**: :red_circle: There were test failures
(merged mrocklin/trace (c988b38fbea0f5381714bf733e5c6dedd1f11896) into master
(0d88b25d001e4bf91d5ec36fddd06eb6cba77348)).
@mrocklin: Please fix the test failures.
**Interpreter 1**: :red_circle: There were test
[failures]
1 - 100 of 127 matches
Mail list logo
