On Friday, May 6, 2016 at 4:11:42 AM UTC-7, Alasdair Nicol wrote:
>
>
>>
>> But In this particular run I'm currently tracing, rich is already in the
>> db (as the only entry) as pk=5 (via fixture loading process). For one,
>> this tells me the sequence generators aren't always resetting betwe
On Thursday, May 5, 2016 at 4:22:11 PM UTC-7, Mike Dewhirst wrote:
>
> Are you using setUp() and tearDown() as class methods in your test class?
>
>
No, the code was using setUpClass(), which is a classmethod.
--
You received this message because you are subscribed to the Google Groups
"Djan
Hi Rich,
Regarding a couple of things you mentioned on Django-developers:
On Thursday, 5 May 2016 19:20:16 UTC+1, Rich Rauenzahn wrote:
>
>
> Thanks, Tim.
>
> Unfortunately I can't move past Django 1.7 yet -- dependencies. I've been
> marching my way up one revision at a time hopefully up to 1.
On 6/05/2016 8:42 AM, Rich Rauenzahn wrote:
I've been tracing into django core code, and it looks to me that I have
a case where the fixture has a auth.User(username=rich) with a pk=1 in
the fixture. Â But sometimes as the User fixture with pk=1 is being
added (updated?) through Model._save_tabl
I've been tracing into django core code, and it looks to me that I have a
case where the fixture has a auth.User(username=rich) with a pk=1 in the
fixture. But sometimes as the User fixture with pk=1 is being added
(updated?) through Model._save_table(), the same User with pk=5 is already
in
I'm having a strange problem. My test environment has been working fine,
but I am upgrading my environment's Django revision slowly, which means I
also need to move away from django-nose's FastFixtureTestCase.
I'm now at Django 1.7. I have a TestCase which is more or less...
class Foo(TestC
6 matches
Mail list logo
