Russell Keith-Magee wrote:
> Django has made a value judgement that an empty field in a form will
> be interpreted as an empty string. If you don't like this default
> behaviour, you can override it at the form level.
That makes sense for forms (where input is coming from the end user),
but why
Glad to see this debate happening, because for a long time I felt like I
was the only one who had issues with CBVs. I forced myself to use CBVs
(custom and generics) on two major projects and I'm still struggling to see
the real value in them.
Luke's post did an excellent job of articulating th
Glad to see this debate happening, because for a long time I felt like I
was the only one who had issues with CBVs. I forced myself to use CBVs
(custom and generics) on two major projects and I'm still struggling to see
the real value in them.
Luke's post did an excellent job of articulating th
I'm not suggesting that CBVs make it harder to test (I actually think it
should be no different because the tests should avoid being implementation
specific). I just feel that the pattern of testing/refactoring is different
than the typical TDD approach (one could argue that this is not necessar
On Tuesday, June 5, 2012 10:12:45 AM UTC-4, dstufft wrote:
>
> On Tuesday, June 5, 2012 at 9:55 AM, Zach Mathew wrote:
>
> For example, I would avoid unit testing the "get_context_data" method on a
> CBV and instead have a test that performs a request on the view
