Re: [Django] #27685: Allow autoreloader to use watchman

[Django]

#27685: Allow autoreloader to use watchman
-+-
 Reporter:  Aymeric Augustin |Owner:  Tom
 Type:   |  Forbes
  Cleanup/optimization   |   Status:  assigned
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tom Forbes):

 * needs_better_patch:  1 => 0


Comment:

 I've completed what I think is the bulk of the work for the first stage of
 this, refactoring the autoreloader to allow us to add support for Watchman
 in the future. After making the autoreloader more modular I've expanded
 the tests (including ones for the inotify reloader) and fleshed out the
 API for triggering arbitrary watches.

 I think with this we can easily close #25624, #25791 and #28602 in the
 near future.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.df997a4fc1d88b0cb2500d730b855f3f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25791: Implement autoreload behaviour for cached template loader

[Django]

#25791: Implement autoreload behaviour for cached template loader
-+-
 Reporter:  Jaap Roes|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  autoreload   | Triage Stage:  Accepted
  templates cached loader|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tom Forbes):

 * cc: Tom Forbes (added)


Comment:

 With my work on #27685 this should be easy to do. I've implemented a
 generic `autoreload_started` and `file_changed` signal, and the i18n
 package uses this to reset it's translation cache when a `.mo` file
 changes. We could implement similar logic here to call `reset()` on the
 cached loader when a template changes?

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.ec0c111b71d753a90d6e9ab8f0f2effb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29771: Support database-specific syntax for bulk_update

[Django]

#29771: Support database-specific syntax for bulk_update
-+-
 Reporter:  Tom Forbes   |Owner:  Tom
 Type:   |  Forbes
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Brillgen Developers):

 * cc: Brillgen Developers (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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/061.a8ca0f49cef1d195ec9ea8cda203a12b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.