Tests introduced in patch for #17327 causing errors

2012-03-07 Thread Ryan Kaskel
Hi all. I've pulled in the latest changes and it seems like ticket #17327 [1] introduces a few new tests that are raising errors when I run contrib.auth tests via my project: - auth.MultiDBChangepasswordManagementCommandTestCase.test_that_changepassword_command_with_database_option_uses_given_

Re: Django participation in Google Summer of Code 2012

2012-03-07 Thread Kushagra Sinha
Thanks a lot for the reply. On Wed, Mar 7, 2012 at 5:02 AM, Russell Keith-Magee wrote: > > On 07/03/2012, at 5:35 AM, Kushagra Sinha wrote: > > > Are there plans for Django participating in this year's Google Summer of > Code. The organization application deadline is on 9th March. I would love >

Re: Django participation in Google Summer of Code 2012

2012-03-07 Thread Russell Keith-Magee
One quick update -- Django's 2012 GSoC wiki page is now up, at the somewhat predictable URL: https://code.djangoproject.com/wiki/SummerOfCode2012 Yours, Russ Magee %-) On 07/03/2012, at 5:03 PM, Kushagra Sinha wrote: > Thanks a lot for the reply. > > On Wed, Mar 7, 2012 at 5:02 AM, Russell K

Re: Tests introduced in patch for #17327 causing errors

2012-03-07 Thread Ryan Kaskel
In addition to the above (which I can confirm causes tests to fail in a new project), I also goofed up a patch related to a different set of auth tests. I've created #17848 (release blocker) to fix this. [1] Ticket #16366 [2] required the template context processor cache to be cleared. The code

Re: Tests introduced in patch for #17327 causing errors

2012-03-07 Thread Calvin Cheng
Thanks. I stumbled upon the same problem. On Wednesday, March 7, 2012 4:40:56 PM UTC+8, Ryan Kaskel wrote: > > Hi all. > > I've pulled in the latest changes and it seems like ticket #17327 [1] > introduces a few new tests that are raising errors when I run contrib.auth > tests via my project:

Re: Tests introduced in patch for #17327 causing errors

2012-03-07 Thread Brian Riley
Thanks for catching this. I worked on that patch. The problem is that those two test cases shouldn't be in the auth tests but rather somewhere in top-level tests folder (with the other multi DB tests). I'm not sure exactly where they belong though. If a core dev wants to chime in and suggest a

Re: Tests introduced in patch for #17327 causing errors

2012-03-07 Thread Brian Riley
I added a new patch to move these two failing tests to regressiontests--where they get run with the correct settings and pass. https://code.djangoproject.com/ticket/17327#comment:8 If this isn't the proper place for management command tests like this, I'll move them to wherever is more appropr