GSoC Idea: Improving SymPy-Bot

[Aaron Meurer]

Hi.

Do people think that there would be enough work involved in a
potential GSoC project to improve SymPy-Bot? Right now, there are 33
open issues for it (https://github.com/sympy/sympy-bot/issues). Most
of these are simple bugs, but many things are non-trivial, such as
setting a system up that can serve out requests (the "sympy-bot work"
idea) and improving the formatting of the test output.

Even with those ideas, I feel that it's not enough, though such a
project would be useful to have. Can anyone think of more things that
could go in such a project to make it sufficient, so we can add it to
the ideas list?

Aaron Meurer

[Chris Smith]

Doing a coverage fingerprint -- report lines that are added or changed that are not covered. 

[Aaron Meurer]

From what I understand, you've already got a script that does this,
right? Maybe you could clean it up and submit it for inclusion as
part of the coverage_test script (maybe as something like
`./bin/coverage_test.py --compare`, which would compare against an
already existing built coverage). It would then be easy to adapt that
into SymPy bot.

Also look to see if the coverage module has something like this
already supported.

Aaron Meurer

[Chris Smith]

I would be happy to share the script with anyone who is interested in the project, but it's not a project I want to take on at this time.

[Chris Smith]

One thing my script doesn't do is check for regression in coverage. That's almost as important. So if code is reorganized and suddenly a code path is no longer tested, it should have a test written or else have the code removed if it is now dead code.

[Marchael]

I want to apply for GSoC 2012 and improving sympy-bot may become good
project for me, I'll try to solve some issues from tracker.
You could send code directly to my email or share with any other
comfortable way.

[Marchael]

I have questions about sympy-bot/examples. It'd be greate if someone
could contact me on #sympy

[Joachim Durchholz]

Am 24.02.2012 14:07, schrieb Marchael:
> I want to apply for GSoC 2012 and improving sympy-bot may become good
> project for me, I'll try to solve some issues from tracker.
> You could send code directly to my email or share with any other
> comfortable way.

You can get the code from https://github.com/sympy/sympy .

The description for the easiest/best way to hack on SymPy is at
https://github.com/sympy/sympy/wiki/Development-workflow .

HTH

[Aaron Meurer]

I think he meant Chris's coverage script.

Aaron Meurer

> --
> You received this message because you are subscribed to the Google Groups
> "sympy" group.
> To post to this group, send email to sy...@googlegroups.com.
> To unsubscribe from this group, send email to
> sympy+un...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/sympy?hl=en.
>

[Chris Smith]

On Sun, Feb 26, 2012 at 4:19 AM, Aaron Meurer <asme...@gmail.com> wrote:

I think he meant Chris's coverage script.

In that case, it is located at http://pastebin.com/sYkbbA35 .