On Thu, Jan 14, 2010 at 6:56 AM, Jesse Noller <jnol...@gmail.com> wrote: > On Thu, Jan 14, 2010 at 9:08 AM, Vinay Sajip <vinay_sa...@yahoo.co.uk> wrote: >>> From: Jesse Noller <jnol...@gmail.com> >> >>> I'm generally +1 - but given I know that Django 1.2 is slated to >>> implement something somewhat similar, I'm interested to hear how this >>> proposal meshes with their plan(s).. >> >> Django 1.2 will most likely not implement logging - they're now in feature >> freeze for big features. See Russ Magee's post: >> >> http://groups.google.com/group/django-developers/msg/4ef81a2160257221 >> >> They're waiting for a Python decision and (from Russ Magee's post) seem to >> be in favour of the changes proposed in PEP 391. If we get these changes >> into Python soon, then Django 1.3 may be able to make use of them in its >> logging (which encompasses not just configuring Django logging in a >> settings.py, but also using logging internally throughout Django where it >> makes sense to do so). >> >> Assuming PEP 391 gets the nod, then after implementing the changes into >> Python, I plan to work with the Django community to get improved logging >> support in Django for 1.3. >> >> Regards, >> >> Vinay Sajip >> > > Cool, +1 then :)
<nod> Having read the PEP I heartily approve. The PEP can be moved to Accepted state. This can be implemented in Python 2.7 and 3.2, right? -- --Guido van Rossum (python.org/~guido) _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
