[sage-devel] Re: classifying trac tickets as silently incorrect results

2016-07-09 Thread Travis Scrimshaw
> If a ticket describes an issue where sage silently returns a wrong answer, > please update the ticket description, adding a 'wrongAnswerLabel' to the > stopgap field. > > Please don't. That field is suppose to be used for tickets which implement the stopgap when it is applicable (which it w

[sage-devel] Re: classifying trac tickets as silently incorrect results

2016-07-09 Thread Jakob Kroeker
> > Please don't. That field is suppose to be used for tickets which implement > the stopgap when it is applicable Unfortunately stopgaps for all the silent wrong results will hardly be accepted. I already experienced heavy opposition as I created some and was not able to create them in full

[sage-devel] Re: classifying trac tickets as silently incorrect results

2016-07-10 Thread Travis Scrimshaw
On Saturday, July 9, 2016 at 5:17:48 PM UTC-5, Jakob Kroeker wrote: > > Please don't. That field is suppose to be used for tickets which implement >> the stopgap when it is applicable > > > Unfortunately stopgaps for all the silent wrong results will hardly be > accepted. > That's just not tru

Re: [sage-devel] Re: classifying trac tickets as silently incorrect results

2016-07-09 Thread Vincent Delecroix
On 09/07/16 18:17, Jakob Kroeker wrote: Please don't. That field is suppose to be used for tickets which implement the stopgap when it is applicable Unfortunately stopgaps for all the silent wrong results will hardly be accepted. I already experienced heavy opposition as I created some and

Re: [sage-devel] Re: classifying trac tickets as silently incorrect results

2016-07-09 Thread Jakob Kroeker
using a keyword the ticket will not added to the list of mathematically wrong answers. It is about make silent wrong answers _visible_. Stopgaps are an extreme tool and are hard to enforce. Also I do not (yet) have the time to create 72 stopgaps and nobody else seems to care. Jakob Am S

Re: [sage-devel] Re: classifying trac tickets as silently incorrect results

2016-07-10 Thread Dima Pasechnik
On Saturday, July 9, 2016 at 11:32:57 PM UTC+1, vdelecroix wrote: > > On 09/07/16 18:17, Jakob Kroeker wrote: > > > >> > >> Please don't. That field is suppose to be used for tickets which > implement > >> the stopgap when it is applicable > > > > > > Unfortunately stopgaps for all the si

Re: [sage-devel] Re: classifying trac tickets as silently incorrect results

2016-07-10 Thread Johan S . H . Rosenkilde
> well, we already have this: https://trac.sagemath.org/report/79 > IMHO it's a great idea to have all such places explicitly marked. +1. I think it's great to have such a list which contains both the ones for which we wish to add a stopgap, as well as those we don't/haven't yet. If the stopgap f