On Tue, Sep 28, 2010 at 4:03 PM, Jesus Cea <jcea at jcea.es> wrote: > On 29/09/10 00:56, Guido van Rossum wrote: >> On Tue, Sep 28, 2010 at 3:23 PM, Amaury Forgeot d'Arc >> <amauryfa at gmail.com> wrote: >>> 2010/9/28 Nick Coghlan <ncoghlan at gmail.com>: >>>> Converting to a Py3k warning sounds like the best option. >>> >>> Can someone please explain why converting to a PyCapsule object is not >>> an option? >>> PyCObject_AsVoidPtr() and PyCObject_Import() accept Capsules and will >>> work as before. >> >> Because bsddb is an external module? > > Uhm?. I am confused... > > The reason to rollback the deprecation warning is because it is breaking > other external modules too, see a previous post. Since there is no 2.8 > planned, a deprecation warning is not useful. See the thread linked in > the tracker. > > About converting the deprecation warning to a py3k warning... Would a > py3k warning be converted to an error when python is invoked as "-We"?. > If that is the case, we are in the same situation. Hm, I am okay with programs not working if -We -3 is selected. Why would anyone want to run in that mode anyway? And if -We crashes you have a bug in your C code (not enouggh error checking),. -- --Guido van Rossum (python.org/~guido)
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