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

create_connection signal only fired if app name given #80

Open
patrickcd opened this issue Jun 25, 2012 · 4 comments
Open

create_connection signal only fired if app name given #80

patrickcd opened this issue Jun 25, 2012 · 4 comments

Comments

@patrickcd
Copy link

I've got a sql aggregate function that registers via the create_connection signal. This works with django-nose if I pass an app name, but not otherwise.

manage.py test # signal receiver not called
manage.py test myapp # signal receiver called

Easy to work around this, so no worries, but I thought the report might be useful

thanks

@almostabc
Copy link

I've been running into this same issue. Does anyone know why this might be occurring?

@fabiosantoscode
Copy link
Contributor

It seems like an import-time issue.

You could try out my pull request #111 which might fix this.

@almostabc
Copy link

Yeah, it seems like it was some type of import issue. I managed to get everything working by adding a 'uid' parameter to each of my signal receiver registrations.

@jwhitlock
Copy link
Contributor

I don't see a create_connection signal. Is this an old signal, or was it connection_created?

https://docs.djangoproject.com/en/1.4/ref/signals/#connection-created

Is this still an issue w/ django-nose 1.4.1 and a current Django version?

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

No branches or pull requests

4 participants