[sympy] Re: how to make code self correcting...almost

2010-05-12 Thread smichr
In order to keep the workaround code clean I'd suggest that the NotBrokenException should be raised in the broken() function, or maybe  check_if_still_broken() ? if hasattr(foo, 'is_number) and foo.is_number:     check_if_still_broken(Function.is_number)     bar() I like this idea. But

Re: [sympy] Re: how to make code self correcting...almost

2010-05-12 Thread Felix Kaiser
On 05/12/2010 07:55 PM, smichr wrote: In order to keep the workaround code clean I'd suggest that the NotBrokenException should be raised in the broken() function, or maybe check_if_still_broken() ? if hasattr(foo, 'is_number) and foo.is_number: check_if_still_broken(Function.is_number)

[sympy] Re: how to make code self correcting...almost

2010-05-11 Thread jegerjensen
On 11 Mai, 08:03, smichr smi...@gmail.com wrote: As we run into problem where a workaround is necessary, it would be good to have a way to be able to mark the code so that when the problem is fixed we can update the code. e.g. in issue 1934 is raised the issue of Function not having a

[sympy] Re: how to make code self correcting...almost

2010-05-11 Thread Vinzent Steinberg
Another variant would be to use xfailed tests for this. Vinzent On 11 Mai, 08:03, smichr smi...@gmail.com wrote: As we run into problem where a workaround is necessary, it would be good to have a way to be able to mark the code so that when the problem is fixed we can update the code. e.g.