Re: [Django] #19212: app_cache_ready signal

[Django]

#19212: app_cache_ready signal
-+-
 Reporter:  cdestigter   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |  1.5-alpha-1
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by fcurella):

 * cc: flavio.curella@… (added)


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19212: app_cache_ready signal

[Django]

#19212: app_cache_ready signal
-+-
 Reporter:  cdestigter   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |  1.5-alpha-1
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by russellm):

 * status:  new => closed
 * needs_docs:   => 0
 * resolution:   => duplicate
 * needs_tests:   => 0
 * needs_better_patch:   => 0


Comment:

 This is a long standing request, but it's not as simple as "just add a
 signal", because there isn't currently any reliable point at which we can
 guarantee that all apps have been loaded. To see the historical
 discussion, search for "App Refactor" or "App loading refactor" in the
 archives; ticket #3591 is the placeholder for the work.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19212: app_cache_ready signal

[Django]

#19212: app_cache_ready signal
--+-
 Reporter:  cdestigter|  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.5-alpha-1
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+-
 [https://groups.google.com/d/topic/django-users/OziphrWlcYo/discussion
 This thread] on django-users proposed the concept of a signal for when all
 apps are loaded. We've also come across a use case that requires this.

 Basically class_prepared is fired during loading of the app cache. So
 during handling of class_prepared, ForeignKey.rel.to may not yet be
 resolved, and that limits what we can do.

 So we wrote a 3-line patch which adds a signal that gets fired when the
 app cache finishes loading.

 Because this can't be done outside of core without monkey-patching, I'd
 say it belongs in core.

 Here's another request for this on SO:
 http://stackoverflow.com/questions/1333019/django-audittrail-lazy-
 relations


 Our 3 line patch:
 
[https://github.com/koordinates/django/commit/cfa687409698ab9c5ffd150d0c89aba7d361739f]

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.