Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

incompatiblity with profile plugin #124

Closed
hexsprite opened this issue May 29, 2013 · 1 comment
Closed

incompatiblity with profile plugin #124

hexsprite opened this issue May 29, 2013 · 1 comment

Comments

@hexsprite
Copy link

Both use prepareTest to do some initialization.

prepareTest by design only calls it on the first plugin it finds it on that returns a truth value and then stops processing any further plugins.

django_nose uses this hook to setup the database. Where else could it do that in the nose plugin architecture?

@naktinis
Copy link

naktinis commented Jun 4, 2013

This seems to be a duplicate of #121.

I've proposed a solution for that - increasing the DjangoSetUpPlugin priority so its prepareTest is run before profiler's prepareTest.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants