On 11-10-26 10:51 AM, Vinay Sajip wrote:
...
> auto-translation via 2to3 (because you generally are calling log.warn()
>> rather than logging.warning, but sometimes you are doing getattr( log,
>> log_level ) and then passing that method around a few times), and it
> That doesn't sound like a good u
Mike C. Fletcher vrplumber.com> writes:
> More: an undocumented entry point is not "deprecated" because, after
> all, it shows up in PyDoc as a regular method.
Deprecated methods also show up in PyDoc. Of course, if the deprecation is
mentioned in the docstring, users would see this - but if it
On 11-10-26 05:12 AM, Vinay Sajip wrote:
> Mike C. Fletcher vrplumber.com> writes:
>
>> I actually consider .warning() a nit :) . After all, it's 3 extra
>> characters :) , and *who* actually reads documentation instead of just
>> poking around and finding the shortest-named method in the instanc
Mike C. Fletcher vrplumber.com> writes:
> I actually consider .warning() a nit :) . After all, it's 3 extra
> characters :) , and *who* actually reads documentation instead of just
> poking around and finding the shortest-named method in the instance?
Readability counts :-) Are you saying there
On 11-10-24 04:28 AM, Vinay Sajip wrote:
>> I think that is a real shame - it seems to be gratuitous breakage for almost
>> zero benefit. That issue shows that Trac makes heavy use of .warn, I've use
>> .warn almost exclusively for many years, and code.google.com shows it is
>> used
>> extensi
Vinay Sajip wrote:
I think that is a real shame - it seems to be gratuitous breakage for almost
zero benefit. That issue shows that Trac makes heavy use of .warn, I've use
.warn almost exclusively for many years, and code.google.com shows it is used
extensively in the wild.
Ok
> I think that is a real shame - it seems to be gratuitous breakage for almost
> zero benefit. That issue shows that Trac makes heavy use of .warn, I've use
> .warn almost exclusively for many years, and code.google.com shows it is used
> extensively in the wild.
Okay, but it's easy enough to
On 22/10/2011 11:09 PM, Vinay Sajip wrote:
In response to an issue (#13235) raised on the Python bug tracker, I'm going to
deprecate the warn() methods in the Logger and LoggerAdapter classes in the
stdlib logging package, as well the module-level warn() function.
The warn() variants were synony
In response to an issue (#13235) raised on the Python bug tracker, I'm going to
deprecate the warn() methods in the Logger and LoggerAdapter classes in the
stdlib logging package, as well the module-level warn() function.
The warn() variants were synonyms for the warning() methods and function, an
