Re: [Django] #16006: Make cache lazy to allow test runners to switch cache backends

[Django]

#16006: Make cache lazy to allow test runners to switch cache backends
-+-
 Reporter:  brianjaystanley  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.3
Component:  Core (Cache system)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:  Design
 Keywords:   |  decision needed
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 The argument in favor of this change is:
 > Switching cache backends at runtime would be useful in test runners, in
 order to be able to test caching-related functionality without populating
 a production cache.

 Running tests on a production server, with production settings, certainly
 isn't something we want to encourage. You should use a different settings
 file, or even better, a clone of your production environment.

-- 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16006: Make cache lazy to allow test runners to switch cache backends

[Django]

#16006: Make cache lazy to allow test runners to switch cache backends
-+-
   Reporter: |  Owner:  nobody
  brianjaystanley| Status:  new
   Type: |  Component:  Core (Cache system)
  Cleanup/optimization   |   Severity:  Normal
  Milestone: |   Keywords:
Version:  1.3|  Has patch:  1
 Resolution: |Needs tests:  1
   Triage Stage:  Design |  Easy pickings:  0
  decision needed|
Needs documentation:  1  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by brianjaystanley):

 * cc: brianjaystanley (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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16006: Make cache lazy to allow test runners to switch cache backends

[Django]

#16006: Make cache lazy to allow test runners to switch cache backends
-+-
   Reporter: |  Owner:  nobody
  brianjaystanley| Status:  new
   Type: |  Component:  Core (Cache system)
  Cleanup/optimization   |   Severity:  Normal
  Milestone: |   Keywords:
Version:  1.3|  Has patch:  1
 Resolution: |Needs tests:  1
   Triage Stage:  Design |  Easy pickings:  0
  decision needed|
Needs documentation:  1  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by zimnyx):

 * cc: zimnyx@… (added)
 * ui_ux:   => 0


Comment:

 It would be reasonable for Django test runner to switch cache backend
 (from production to testing one) or add a cache key prefix to default
 backend.

-- 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16006: Make cache lazy to allow test runners to switch cache backends

[Django]

#16006: Make cache lazy to allow test runners to switch cache backends
-+-
   Reporter: |  Owner:  nobody
  brianjaystanley| Status:  new
   Type: |  Component:  Core (Cache system)
  Cleanup/optimization   |   Severity:  Normal
  Milestone: |   Keywords:
Version:  1.3|  Has patch:  1
 Resolution: |Needs tests:  1
   Triage Stage:  Design |  Easy pickings:  0
  decision needed|
Needs documentation:  1  |
Patch needs improvement:  0  |
-+-
Changes (by aaugustin):

 * needs_docs:  0 => 1
 * needs_tests:  0 => 1
 * stage:  Unreviewed => Design decision needed


-- 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16006: Make cache lazy to allow test runners to switch cache backends

[Django]

#16006: Make cache lazy to allow test runners to switch cache backends
-+-
   Reporter: |  Owner:  nobody
  brianjaystanley| Status:  new
   Type: |  Component:  Core (Cache system)
  Cleanup/optimization   |   Severity:  Normal
  Milestone: |   Keywords:
Version:  1.3|  Has patch:  1
 Resolution: |Needs tests:  0
   Triage Stage: |  Easy pickings:  0
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by brianjaystanley):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 The patch also allows any cache backend loaded through get_cache to
 register a request_finished signal handler if it needs to. In the
 original, the signal registration is only available for the default cache,
 so loading another cache that needs to do cleanup will not register its
 handler. In the patch, registration will happen later because of the cache
 being lazy, but that should be fine since no cache backend should need to
 receive request_finished signals if it was never even loaded.

-- 
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 this group at 
http://groups.google.com/group/django-updates?hl=en.