Since no Python code should be generating the warning (I would double-check that, obviously), I say take it out. At least from a PEP 352 perspective there is nothing about keeping it (or removing it). -Brett On 5/26/06, Richard Jones <richard at commonground.com.au> wrote: > > On 25/05/2006, at 9:00 PM, Jim Jewett wrote: > >> +/* > >> + * OverflowWarning extends Warning > >> + */ > >> +SimpleExtendsException(PyExc_Warning, OverflowWarning, "Base > >> class for warnings about numeric overflow. Won't exist in Python > >> 2.5."); > > > > Take it out now? > > What do people say? I implemented this one because it was implemented > in the old code in 2.5. Happy to remove it. > > > Richard > > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/brett%40python.org > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/python-dev/attachments/20060526/d72666ef/attachment.html
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4