Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #14921
| Date | 2011-10-24 16:34 +0200 |
|---|---|
| From | Jean-Michel Pichavant <jeanmichel@sequans.com> |
| Subject | Re: logging: warn() methods and function to be deprecated. |
| References | <loom.20111022T135016-802@post.gmane.org> <4EA4A65F.2090205@gmail.com> <1319444908.73851.YahooMailNeo@web25801.mail.ukl.yahoo.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.2178.1319466878.27778.python-list@python.org> (permalink) |
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. >> > > Okay, but it's easy enough to change, and people are getting a reasonable amount of time to deal with it. > > >> Is there still a chance to reconsider? >> > > I'm not dogmatic about things like this; warn() is just a hangover from a long time ago and bit of a nit, that's all. I suppose I should have removed it when 3.0 was released, but it went under my radar at that time. > > Hence my post here, to get feedback from logging users about this proposed change. > > Regards, > > Vinay Sajip > I'm not using python 3, I'm not sure my feedback matters, but I wouldn't mind refactoring warn into warning If I'd have to. It's better to use documented API anyway. JM PS : I also had an issue with my logging wrappers where I did not implement warn, quite confusing the first time I had this error.
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: logging: warn() methods and function to be deprecated. Jean-Michel Pichavant <jeanmichel@sequans.com> - 2011-10-24 16:34 +0200
csiph-web