[Python-Dev] Pronouncement needed in issue9675 (original) (raw)
Guido van Rossum guido at python.org
Wed Sep 29 01:52:33 CEST 2010
- Previous message: [Python-Dev] Pronouncement needed in issue9675
- Next message: [Python-Dev] Pronouncement needed in issue9675
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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? PyCObjectAsVoidPtr() and PyCObjectImport() 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)
- Previous message: [Python-Dev] Pronouncement needed in issue9675
- Next message: [Python-Dev] Pronouncement needed in issue9675
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]