Bug #73847 using connecion_created signal in django causing runtime error
Submitted: 9 Sep 2014 6:04 Modified: 23 Sep 2014 15:46
Reporter: Peeyush Gupta Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / Python Severity:S3 (Non-critical)
Version:1.2.3 OS:Any
Assigned to: CPU Architecture:Any
Tags: Django

[9 Sep 2014 6:04] Peeyush Gupta 
Description:
Using connection_created signal defined in django.db.backends.signals
causes maximum recursion depth reached runtime error when the engine is
mysql.connector.django

Courtsey: http://stackoverflow.com/questions/25683570/cant-set-character-set-results-to-latin1

How to repeat:
use connection_created.connect(...) in a django script
[23 Sep 2014 15:46] Paul DuBois 
Noted in 1.2.4, 2.0.2 changelogs.

Using a connection_created signal defined in
django.db.backends.signals caused a "maximum recursion depth reached"
runtime error.