Hi,
On 14 November 2011 23:02, Mateusz Paprocki wrote:
> Hi,
>
> Is there a chance we could release SymPy 0.7.2 in two weeks? Early
> December I will give a tutorial about SymPy and I would like to take
> advantage of Python 3 support and new features.
>
I started https://github.com/sympy/sympy
On Nov 16, 2:41 am, Mateusz Paprocki wrote:
>
> > By the way, where are you giving the tutorial at?
>
> SciPy.In in Mumbai (Bombay), India.
\o/
Have fun in Mumbai Mateusz! Its a really friendly place. Go easy
on the local street food though ;-)
BTW, you can mention to the students there that yo
In pull request 673 there is a new plotting module. It's functional and
Aaron and Ondrej were interested in merging it before the next release.
It seems that the release will be sooner than expected. Does this change
the plans about the pull request 673? As I've said the code is mostly
ready, but
On Tue, Nov 15, 2011 at 9:20 PM, krastanov.ste...@gmail.com
wrote:
> In pull request 673 there is a new plotting module. It's functional and
> Aaron and Ondrej were interested in merging it before the next release.
>
> It seems that the release will be sooner than expected. Does this change the
>
On Tue, Nov 15, 2011 at 1:31 PM, Vladimir Periæ wrote:
> On Tue, Nov 15, 2011 at 9:20 PM, krastanov.ste...@gmail.com
> wrote:
>> In pull request 673 there is a new plotting module. It's functional and
>> Aaron and Ondrej were interested in merging it before the next release.
>>
>> It seems that t
On Tue, Nov 15, 2011 at 12:37 PM, Mateusz Paprocki wrote:
> Hi,
>
> On 14 November 2011 23:02, Mateusz Paprocki wrote:
>>
>> Hi,
>> Is there a chance we could release SymPy 0.7.2 in two weeks? Early
>> December I will give a tutorial about SymPy and I would like to take
>> advantage of Python 3 s
So I saw that Vladimir removed the milestone on some issues, but he
wasn't nearly as aggressive as I would have hoped, so I just went
through myself, and removed the milestone from many issues, and
postponed some others. What remains are eight issues, two of which
could be further postponed if nec
This has obviously been postponed, I guess we all underestimated the
amount of work we'll have from GCI (so I couldn't really help with any
release-related stuff). I guess in light of GCI and the current fast
pace of development, it might be a good idea to postpone the release
to January (GCI ends
Yeah, I'm totally free until the end of January, starting in two
weeks. We'll probably need to do some cleaning up from pull requests
and stuff after GCI too (e.g., right now, I'm basically ignoring all
non-critical non-gci pull requests).
Aaron Meurer
On Wed, Nov 30, 2011 at 10:13 AM, Vladimir
Hi,
On 30 November 2011 22:50, Aaron Meurer wrote:
> Yeah, I'm totally free until the end of January, starting in two
> weeks. We'll probably need to do some cleaning up from pull requests
> and stuff after GCI too (e.g., right now, I'm basically ignoring all
> non-critical non-gci pull request
On Fri, Dec 2, 2011 at 2:22 AM, Mateusz Paprocki wrote:
> Hi,
>
> On 30 November 2011 22:50, Aaron Meurer wrote:
>>
>> Yeah, I'm totally free until the end of January, starting in two
>> weeks. We'll probably need to do some cleaning up from pull requests
>> and stuff after GCI too (e.g., right
On Fri, Dec 2, 2011 at 5:05 PM, Aaron Meurer wrote:
> On Fri, Dec 2, 2011 at 2:22 AM, Mateusz Paprocki wrote:
>> Hi,
>>
>> On 30 November 2011 22:50, Aaron Meurer wrote:
>>>
>>> Yeah, I'm totally free until the end of January, starting in two
>>> weeks. We'll probably need to do some cleaning u
On Fri, Dec 2, 2011 at 10:57 AM, Vladimir Perić wrote:
> On Fri, Dec 2, 2011 at 5:05 PM, Aaron Meurer wrote:
>> On Fri, Dec 2, 2011 at 2:22 AM, Mateusz Paprocki wrote:
>>> Hi,
>>>
>>> On 30 November 2011 22:50, Aaron Meurer wrote:
Yeah, I'm totally free until the end of January, start
On Fri, Dec 2, 2011 at 10:42 AM, Aaron Meurer wrote:
> On Fri, Dec 2, 2011 at 10:57 AM, Vladimir Perić wrote:
>> On Fri, Dec 2, 2011 at 5:05 PM, Aaron Meurer wrote:
>>> On Fri, Dec 2, 2011 at 2:22 AM, Mateusz Paprocki wrote:
Hi,
On 30 November 2011 22:50, Aaron Meurer wrote:
>>>
On the topic of testing: What is the reason that the pull requests are not
all tested automatically? And tox run every week or so. I thought that all
the code for the automated testing is already written. And there is that
google app engine instance. If it's only a processing power issue I have a
r
On Dec 2, 2011, at 1:49 PM, "Ondřej Čertík" wrote:
> On Fri, Dec 2, 2011 at 10:42 AM, Aaron Meurer wrote:
>> On Fri, Dec 2, 2011 at 10:57 AM, Vladimir Perić
>> wrote:
>>> On Fri, Dec 2, 2011 at 5:05 PM, Aaron Meurer wrote:
On Fri, Dec 2, 2011 at 2:22 AM, Mateusz Paprocki wrote:
> Hi
On 2 December 2011 22:23, Aaron Meurer wrote:
> On Dec 2, 2011, at 1:49 PM, "Ondřej Čertík"
> wrote:
>
> > On Fri, Dec 2, 2011 at 10:42 AM, Aaron Meurer
> wrote:
> >> On Fri, Dec 2, 2011 at 10:57 AM, Vladimir Perić
> wrote:
> >>> On Fri, Dec 2, 2011 at 5:05 PM, Aaron Meurer
> wrote:
> On
2011/12/2 krastanov.ste...@gmail.com :
> On the topic of testing: What is the reason that the pull requests are not
> all tested automatically? And tox run every week or so. I thought that all
That's the plan, but I got busy to set this up, so it's not done yet.
> the code for the automated testi
2011/12/2 Ondřej Čertík :
> 2011/12/2 krastanov.ste...@gmail.com :
>> On the topic of testing: What is the reason that the pull requests are not
>> all tested automatically? And tox run every week or so. I thought that all
>
> That's the plan, but I got busy to set this up, so it's not done yet.
>
Oh, and if someone could go through and add priority labels and code
in labels to all the sympy-bot issues
(https://github.com/sympy/sympy-bot/issues?sort=created&direction=desc&state=open),
then we can put these in the next round for code-in, and maybe some of
them will be fixed through that. I t
We need to implement "sympy-bot work" to do automated testing, but other
than that, I think we just need computing power. Ondřej was going to use
linode or something, but if you can donate computing power, that would be
great.
Aaron Meurer
Sent from my iPhone.
On Dec 2, 2011, at 2:19 PM, "krasta
That "take a test from the queue and distribute it, deal with downtimes
and failures, do some reporting"... that sounds like a wheel already
invented by Hudson/Jenkins. And if Jenkins doesn't work for Python
stuff, test-on-commit isn't exactly an uncommon demand, so something for
Python should
A company named "Shining Panda" offers free Jenkins hosts for Python to
FLOSS projects.
See https://www.shiningpanda.com/pricing/
--
You received this message because you are subscribed to the Google Groups
"sympy" group.
To post to this group, send email to sympy@googlegroups.com.
To unsubscri
On Sat, Dec 3, 2011 at 8:18 AM, Joachim Durchholz wrote:
> That "take a test from the queue and distribute it, deal with downtimes and
> failures, do some reporting"... that sounds like a wheel already invented by
> Hudson/Jenkins. And if Jenkins doesn't work for Python stuff, test-on-commit
> isn
Am 03.12.2011 11:39, schrieb Vladimir Perić:
> [...]
Yep, I had found your work through Google, but only after sending my
messages, so I thought "aw heck, he'll talk if he's still behind it, I
don't want to pressure Vladimir into coming forth" :-)
Jo, if you are interested in playing around
I agree with Vladimir that using Jenkins is the right solution. But for the
moment I've written a very ugly and short script to automate the pull
request testing. I'll start running it today (It's still not tested)
Stefan
On 3 December 2011 12:50, Joachim Durchholz wrote:
> Am 03.12.2011 11:39,
I forgot copy the link to the script:
https://github.com/sympy/sympy-bot/pull/74
On 3 December 2011 14:04, krastanov.ste...@gmail.com <
krastanov.ste...@gmail.com> wrote:
> I agree with Vladimir that using Jenkins is the right solution. But for
> the moment I've written a very ugly and short scri
The biggest problem with Jenkins in my opinion is that it has such a
terrible user interface.
SymPy-Bot is nice in that it allows completely distributed testing.
The script is so simple and self-contained that anyone can just clone
it and run it (I guess there are a few Python dependencies to inst
I went ahead and registered for the Shining Panda thing, since it was
free. There apparently is a waiting list for the free open source
plan, and we are number 6. I'll let you know when it goes online.
Aaron Meurer
On Sat, Dec 3, 2011 at 7:53 AM, Aaron Meurer wrote:
> The biggest problem with J
It looks like shining panda gives one hour per day free to foss projects.
Is this sufficient for our needs? Or rather, how much compute time would a
nice testing system require?
On Sat, Dec 3, 2011 at 8:57 AM, Aaron Meurer wrote:
> I went ahead and registered for the Shining Panda thing, since i
I've started the script I've written about in the previous mail. Now every
6 hours all open mergeable pull requests that are not tested will be tested
in python 2.7.1.
The computer I'm using will continue to do the tests unless there is a
hardware problem (which is possible as there are some fault
Am 03.12.2011 15:53, schrieb Aaron Meurer:
The biggest problem with Jenkins in my opinion is that it has such a
terrible user interface.
In configuration, or when reading and interpreting test results?
--
You received this message because you are subscribed to the Google Groups
"sympy" group.
On Sat, Dec 3, 2011 at 10:47 AM, Joachim Durchholz wrote:
> Am 03.12.2011 15:53, schrieb Aaron Meurer:
>
>> The biggest problem with Jenkins in my opinion is that it has such a
>> terrible user interface.
>
>
> In configuration, or when reading and interpreting test results?
>
I haven't even play
Probably not, if we want to test all the pull requests.
But if we set up a system like what I was talking about where the
server can server out tests, then I too can probably set up an old
computer or two to do testing with. Old computers like this are
actually not that hard to come by (indeed, as
Le samedi 03 décembre 2011 à 11:39 +0100, Vladimir Perić a écrit :
> On Sat, Dec 3, 2011 at 8:18 AM, Joachim Durchholz wrote:
> > That "take a test from the queue and distribute it, deal with downtimes and
> > failures, do some reporting"... that sounds like a wheel already invented by
> > Hudson/
Am 03.12.2011 20:48, schrieb Aaron Meurer:
Right now, Stefan's script works only for his machine, if I were to
run the same script, we would just get duplicate reports (unless we
timed them to be offset or something). So we really need to get some
poling mechanism implemented,
This sounds worr
As I've said in the mail introducing the script and in the commit with the
script itself the script is just a quick 20-line workaround so we can have
the testing now. Aaron has rightfully referred to it as "testing" only in
quotes as it's only an ugly script, not a distributed continuous
integratio
On Sat, Dec 3, 2011 at 3:35 PM, Joachim Durchholz wrote:
> Am 03.12.2011 20:48, schrieb Aaron Meurer:
>
>> Right now, Stefan's script works only for his machine, if I were to
>> run the same script, we would just get duplicate reports (unless we
>> timed them to be offset or something). So we rea
On Sat, Dec 3, 2011 at 6:53 AM, Aaron Meurer wrote:
> The biggest problem with Jenkins in my opinion is that it has such a
> terrible user interface.
>
> SymPy-Bot is nice in that it allows completely distributed testing.
> The script is so simple and self-contained that anyone can just clone
> it
39 matches
Mail list logo
