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 wrote:
> On Thu, Sep 04, 2014 at 08:47:58AM +0200, Joachim Durchholz wrote:
>> Personally, I do not like slow tests. Practice has show
On Tuesday, September 2, 2014 11:17:35 PM UTC-7, Joachim Durchholz wrote:
>
> Am 03.09.2014 um 02:07 schrieb Richard Fateman:
> > Sure. Unlikely to be easy to do by simply hacking on trees. Here's a
> > classic pattern:
> >
> > a*x^2+b*x+c.a,b,c are pattern variables. x, in this con
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 pyth
