On Sun, Dec 26, 2010 at 9:55 PM, Will Hardy wrote:
> It's true that there isn't any rich API for the Error/Fail distinction. The
> best I can think of would be to create a custom exception eg
> FailedAssumption, which is raised when the TestCase.failedException (same as
> AssertionError) is caugh
It's true that there isn't any rich API for the Error/Fail distinction. The
best I can think of would be to create a custom exception eg
FailedAssumption, which is raised when the TestCase.failedException (same as
AssertionError) is caught while testing an assumption.
Here are four ways I can thin
I'm sorry, I misspelled Jannis' name by mistake.
2010/12/26 Miguel Araujo
> Hi Stephan,
>
> I'm sorry but I didn't get any answer on Github :)
>
> In that case, if you already discussed it with Jannie Leidel and Russell
> Keith-Magee, then I guess they liked the idea of replacing it with you app
Hi Stephan,
I'm sorry but I didn't get any answer on Github :)
In that case, if you already discussed it with Jannie Leidel and Russell
Keith-Magee, then I guess they liked the idea of replacing it with you app
when it has some more work done. In that case if you are planning on working
on it, I
Hi Miguel,
I saw your message on GitHub and I thought I had answered that I'll work on
the formwizard within the next weeks. But maybe I missed to press the "send"
button :-)
Regarding your points, I had the same thoughts in 02/2010 and started to
write django-formwizard. There were also som
Hi everyone,
I think FormWizard solves a common problem when you need forms to be split
into steps, many frameworks have solutions to this pattern. I started using
it and soon realized there is much left to be done and it looks like it's
been postponed too long.
In brief it's missing support for:
