Re: Test runner with search

On 06/14/2012 07:25 AM, Jannis Leidel wrote: > On 14.06.2012, at 12:35, Chris Wilson wrote: >> Hi all, >> >> I've made some improvements (in my view) to the >> DjangoTestSuiteRunner. I got tired of having to remember my test >> class names and of typing so much: >> >> ./manage.py test

Re: Test runner with search

On Thu, Jun 14, 2012 at 7:35 AM, Chris Wilson wrote: > Hi all, > > I've made some improvements (in my view) to the DjangoTestSuiteRunner. I > got tired of having to remember my test class names and of typing so much: > >  ./manage.py test

Re: Test runner with search

Hi Andrew, On Thu, 14 Jun 2012, Andrew Godwin wrote: > +1 from me as well - the test runner you linked to looks reasonably > sane, only a few small things that I'm questioning (like why types is > imported inside the for loop). I prefer to keep the imports as close to the code that uses them

Re: Test runner with search

On 14.06.2012, at 12:35, Chris Wilson wrote: > Hi all, > > I've made some improvements (in my view) to the DjangoTestSuiteRunner. I > got tired of having to remember my test class names and of typing so much: > > ./manage.py test binder.BinderTest.test_can_create_users > > This new version

Re: Test runner with search

On 14/06/12 11:51, Anssi Kääriäinen wrote: > On 14 kesä, 13:35, Chris Wilson wrote: >> I've made some improvements (in my view) to the DjangoTestSuiteRunner. I >> got tired of having to remember my test class names and of typing so much: >> >> ./manage.py test

Re: Test runner with search

On 14 kesä, 13:35, Chris Wilson wrote: > I've made some improvements (in my view) to the DjangoTestSuiteRunner. I > got tired of having to remember my test class names and of typing so much: > >   ./manage.py test binder.BinderTest.test_can_create_users > > This new version

Test runner with search

Hi all, I've made some improvements (in my view) to the DjangoTestSuiteRunner. I got tired of having to remember my test class names and of typing so much: ./manage.py test binder.BinderTest.test_can_create_users This new version searches for tests with the given name in all INSTALLED_APPS,

Re: QuerySet refactoring

On 14 kesä, 10:59, Aymeric Augustin wrote: > Hello Anssi, > > I'm familiar with the topic since I tried to review some of your > refactoring patches (before you gained the ability to commit them > yourself). > > I'm convinced that this refactoring is useful,

Re: ModelForms and the Rails input handling vulnerability

On 14 kesä, 09:03, Alex Ogier wrote: > Right, the Django situation is already considerably more secure than the > Rails status quo. They have a whitelist or blacklist of attributes that > they have declared "accessible", independent of forms, making it easy to >

Re: QuerySet refactoring

Hello Anssi, I'm familiar with the topic since I tried to review some of your refactoring patches (before you gained the ability to commit them yourself). I'm convinced that this refactoring is useful, because it is likely to fix some bugs, especially in features that were added to the ORM long

Re: ModelForms and the Rails input handling vulnerability

On Jun 14, 2012 1:54 AM, "Torsten Bronger" wrote: > > But can one guarantee that fields rendered in the browser are also > sent back in the POST request? Even worse, how about non-browser > requests? > Ugh. I forget that checkboxes don't return anything else when

Re: ModelForms and the Rails input handling vulnerability

On Jun 14, 2012 12:48 AM, "Anssi Kääriäinen" wrote: > > This seems to be different from what Rails do: they have > update_attributes which updates all model attributes present in the > request, but lefts all others untouched. So, in Rails if you render > only part of the