John Whitlock
John Whitlock
No, issue #226 is not fixed. You could try the code in PR #258, which would give us some confirmation that the fix works.
Does this still happen with django-nose 1.4? Do you have a public project that demonstrates the error?
@greylurk Thanks for confirming.
I'm inclined to merge this because it works for you, but there are still no tests in the `django-nose` test suite that exercise `FastFixtureTestRunner`, so I'm not sure if it...
Maybe the tests can be imported from #258.
That code was removed in django-nose 1.4.4. Can you try re-installing django-nose 1.4.6? These should both show ``(1, 4, 6)`` for the installed version: ``` /usr/local/python3/bin/python3.6 -c "import django_nose; print(django_nose.VERSION)"...
This is an interesting solution. There is a lot of broken magic with REUSE_DB=1 right now, so I am reluctant to add any more features until the bugs are fixed.
The README says as much, see https://github.com/jazzband/django-nose#note-to-users: > [nose](https://nose.readthedocs.io/en/latest/) has been in maintenance mode since at least 2015. ``django-nose`` is in maintenance mode as well, and the sole maintainer is...
Without more context, it would be impossible to determine what is going on. Can you point to public code that demonstrates this bug?
Is this still an issue with django-nose 1.4 and a current Django?