Hi,
google now for some time allows to sort the issues as we want, so if you go to:
http://code.google.com/p/sympy/issues/list
the first issues are the ones with a milestone set, the rest is sorted
according to a priority.
Usually, the time each of us can put into sympy is scattered - so what
I
On Tue, Jan 01, 2008 at 02:50:13PM +0100, Ondrej Certik wrote:
>
> Hi,
>
> google now for some time allows to sort the issues as we want, so if you go
> to:
>
> http://code.google.com/p/sympy/issues/list
>
> the first issues are the ones with a milestone set, the rest is sorted
> according to
On Tue, Jan 01, 2008 at 05:04:06PM +0300, Kirill Smelkov wrote:
>
> On Tue, Jan 01, 2008 at 02:50:13PM +0100, Ondrej Certik wrote:
> >
> > Hi,
> >
> > google now for some time allows to sort the issues as we want, so if you go
> > to:
> >
> > http://code.google.com/p/sympy/issues/list
> >
>
> Also, maybe let's write xfailing tests for reported issues *before*
> fixing them?
Why not. But I think if someone goes to write the test, he can as well
fix it. :)
Ondrej
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
On Tue, Jan 01, 2008 at 03:56:26PM +0100, Ondrej Certik wrote:
>
> > Also, maybe let's write xfailing tests for reported issues *before*
> > fixing them?
>
> Why not. But I think if someone goes to write the test, he can as well
> fix it. :)
Yes, but only later -- time is the issue. And one can
On Jan 1, 2008 4:08 PM, Kirill Smelkov <[EMAIL PROTECTED]> wrote:
>
>
> On Tue, Jan 01, 2008 at 03:56:26PM +0100, Ondrej Certik wrote:
> >
> > > Also, maybe let's write xfailing tests for reported issues *before*
> > > fixing them?
> >
> > Why not. But I think if someone goes to write the test, he
