Re: [Django] #27931: Clarify the meaning of "django catch-all logger"

2017-08-22 Thread Django 
#27931: Clarify the meaning of "django catch-all logger"
-+-
 Reporter:  Jesse|Owner:  Tim
 Type:   |  Graham 
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

 * status:  new => closed
 * owner:  (none) => Tim Graham 
 * resolution:   => fixed


Comment:

 In [changeset:"f21915bb3ad73001b7d987332b2b4a0ae4ec288d" f21915bb]:
 {{{
 #!CommitTicketReference repository=""
 revision="f21915bb3ad73001b7d987332b2b4a0ae4ec288d"
 Fixed #27931 -- Clarified the meaning of "django catch-all logger."
 }}}

-- 
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.982ce666b86ed16c314b98d8b0c0250f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27931: Clarify the meaning of "django catch-all logger"

2017-08-14 Thread Django 
#27931: Clarify the meaning of "django catch-all logger"
-+-
 Reporter:  Jesse|Owner:  Barry
 Type:   |  Martin
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_better_patch:  1 => 0


Comment:

 [https://github.com/django/django/pull/8901 PR]

-- 
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.7ba98a39b1fce8b7fbfa38a240e0a847%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27931: Clarify the meaning of "django catch-all logger"

2017-05-08 Thread Django 
#27931: Clarify the meaning of "django catch-all logger"
-+-
 Reporter:  Jesse|Owner:  Barry
 Type:   |  Martin
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Barry Martin):

 * owner:  (none) => Barry Martin
 * status:  new => assigned


--
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.a9e02bbcb0c9320dab795744e0cfeacc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27931: Clarify the meaning of "django catch-all logger"

2017-05-03 Thread Django 
#27931: Clarify the meaning of "django catch-all logger"
--+
 Reporter:  Jesse |Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.10
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Vedran Karačić):

 * cc: vedran@… (removed)
 * owner:  Vedran Karačić => (none)
 * status:  assigned => new


--
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.588b5a6ec0539d27a19da260518d9ce4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27931: Clarify the meaning of "django catch-all logger"

2017-03-25 Thread Django 
#27931: Clarify the meaning of "django catch-all logger"
-+-
 Reporter:  Jesse|Owner:  Vedran
 Type:   |  Karačić
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_better_patch:  0 => 1


--
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.8486167307737f72d78c65d8bec13475%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27931: Clarify the meaning of "django catch-all logger"

2017-03-20 Thread Django 
#27931: Clarify the meaning of "django catch-all logger"
-+-
 Reporter:  Jesse|Owner:  Vedran
 Type:   |  Karačić
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Vedran Karačić):

 * has_patch:  0 => 1


--
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.ff695d69b5da91bd5baae869775ab379%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27931: Clarify the meaning of "django catch-all logger"

2017-03-14 Thread Django 
#27931: Clarify the meaning of "django catch-all logger"
-+-
 Reporter:  Jesse|Owner:  Vedran
 Type:   |  Karačić
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Vedran Karačić):

 * cc: vedran@… (added)
 * status:  new => assigned
 * owner:  nobody => Vedran Karačić


--
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.7497192b97d5018b91d5875ce445d189%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27931: Clarify the meaning of "django catch-all logger" (was: Minimum console logging level for DEBUG=True is too high)

2017-03-14 Thread Django 
#27931: Clarify the meaning of "django catch-all logger"
--+
 Reporter:  Jesse |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.10
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Tim Graham):

 * type:  Bug => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 This looks like a misunderstanding of how logging works. "The django
 catch-all logger" only processes messages in the "django" namespace. For
 example, this will log the message:
 {{{
 import logging
 logger = logging.getLogger('django')
 logger.info("info")
 }}}
 It's not the Django's documentation to do a comprehensive explanation of
 Python logging, but some improvement might be possible.

--
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.5e422118146b404341749316b055d39d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.