Marking the existing test as @slow and adding the faster test seems like a good workaround to me.
Aaron Meurer On Thu, Sep 4, 2014 at 7:12 AM, Sergey B Kirpichev <[email protected]> wrote: > On Thu, Sep 04, 2014 at 08:47:58AM +0200, Joachim Durchholz wrote: >> Personally, I do not like slow tests. Practice has shown that they >> tend to be ignored, and they aren't even always run before a merge. > > AFAIK, we check slow tests before merge (at least for reduced > number of versions of the python interpreters and so on). > > -- > You received this message because you are subscribed to the Google Groups > "sympy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/sympy. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sympy/20140904121225.GA9964%40debian. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sympy. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CAKgW%3D6Kptd_MhDdM7SW79_Qiq7R1joMMhUuMeAoSyjTTZYUcNA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
