[issue13235] logging.warn() is not documented

2011-10-22 Thread Roundup Robot
Roundup Robot added the comment: New changeset 4a90d1ed115d by Vinay Sajip in branch 'default': Closes #13235: Changed PendingDeprecationWarning to DeprecationWarning. http://hg.python.org/cpython/rev/4a90d1ed115d -- resolution: -> fixed status: open -> closed

[issue13235] logging.warn() is not documented

2011-10-22 Thread Vinay Sajip
Vinay Sajip added the comment: > PendingDeprecations are not so useful now that warnings are silenced by > default. > Since it wasn't documented, you could deprecate it in 3.3 and remove it in > 3.4 IMHO. Hmmm, you're probably right. I'll change it to a DeprecationWarning. --

[issue13235] logging.warn() is not documented

2011-10-22 Thread Ezio Melotti
Ezio Melotti added the comment: PendingDeprecations are not so useful now that warnings are silenced by default. Since it wasn't documented, you could deprecate it in 3.3 and remove it in 3.4 IMHO. -- ___ Python tracker

[issue13235] logging.warn() is not documented

2011-10-22 Thread Vinay Sajip
Vinay Sajip added the comment: > BTW, you could have used a DeprecationWarning instead of a > PendingDeprecationWarning, especially if it was already deprecated. It wasn't officially deprecated, just "deprecation via obscurity";-) which is why I made it a PendingDeprecationWarning.

[issue13235] logging.warn() is not documented

2011-10-22 Thread Vinay Sajip
Vinay Sajip added the comment: > Just to me it clear - why do you want warn() to be removed aside from code > duplication? > > My argument to leave it and document is that it is convenient and makes lines > shorter (and won't break existing code). From logging module I also see that > there

[issue13235] logging.warn() is not documented

2011-10-22 Thread Ezio Melotti
Ezio Melotti added the comment: Because there should be only one way to do things. BTW, you could have used a DeprecationWarning instead of a PendingDeprecationWarning, especially if it was already deprecated. -- ___ Python tracker

[issue13235] logging.warn() is not documented

2011-10-22 Thread anatoly techtonik
anatoly techtonik added the comment: Just to me it clear - why do you want warn() to be removed aside from code duplication? My argument to leave it and document is that it is convenient and makes lines shorter (and won't break existing code). From logging module I also see that there are al

[issue13235] logging.warn() is not documented

2011-10-20 Thread Roundup Robot
Roundup Robot added the comment: New changeset 37479f0f68bc by Vinay Sajip in branch 'default': Closes #13235: Added deprecation for warn() methods and function in logging. http://hg.python.org/cpython/rev/37479f0f68bc -- nosy: +python-dev resolution: -> fixed stage: needs patch -> com

[issue13235] logging.warn() is not documented

2011-10-20 Thread Ezio Melotti
Ezio Melotti added the comment: I think it's better to avoid "deprecations by missing documentation" and document explicitly if something is deprecated. What happens is that people working on some old code find the deprecated method, check the doc to see what it does, don't find anything, get

[issue13235] logging.warn() is not documented

2011-10-20 Thread anatoly techtonik
anatoly techtonik added the comment: ./trac/env.py:self.log.warn('base_url option not set in configuration, ' ./trac/env.py:self.log.warn('Couldn\'t write sample configuration file (%s)', e, ./trac/web/main.py:##env.log.warn("%d uncollectable objects

[issue13235] logging.warn() is not documented

2011-10-20 Thread Vinay Sajip
ik > To: vinay_sa...@yahoo.co.uk > Cc: > Sent: Thursday, 20 October 2011, 20:32 > Subject: [issue13235] logging.warn() is not documented > > > anatoly techtonik added the comment: > > I've got a traceback, because forgot to implement this method in logging >

[issue13235] logging.warn() is not documented

2011-10-20 Thread anatoly techtonik
anatoly techtonik added the comment: I've got a traceback, because forgot to implement this method in logging wrapper. It should be either deprecated and removed or documented. -- status: closed -> open ___ Python tracker

[issue13235] logging.warn() is not documented

2011-10-20 Thread Vinay Sajip
Vinay Sajip added the comment: That's deliberate. The original code (before incorporation into Python) had warn(), which was kept for backward compatibility. The docs refer to warning() because that's what everyone is supposed to use. The method names map to the lower case of the appropriate

[issue13235] logging.warn() is not documented

2011-10-20 Thread Ezio Melotti
Changes by Ezio Melotti : -- nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue13235] logging.warn() is not documented

2011-10-20 Thread anatoly techtonik
New submission from anatoly techtonik : No docs for logging.warn() alias. -- assignee: docs@python components: Documentation messages: 146039 nosy: docs@python, techtonik priority: normal severity: normal status: open title: logging.warn() is not documented versions: Python 2.7, Python 3