[issue1195571] simple callback system for Py_FatalError

STINNER Victor added the comment: I understand that this issue has been fixed in bpo-36763 with the implementation of the PEP 587. A new API now allow to handle Python initialization error with a new PyStatus structure. By the way, bpo-30560 was a similar issue. Note: if I misunderstood the

[issue1195571] simple callback system for Py_FatalError

Gregory P. Smith added the comment: i obviously didn't add this to 3.3, unassigning to reflect the attention it (isn't) currently getting. sorry! -- assignee: gregory.p.smith -> ___ Python tracker _

[issue1195571] simple callback system for Py_FatalError

Changes by Martin Morrison : -- nosy: +isoschiz, pconnell ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue1195571] simple callback system for Py_FatalError

James Pye added the comment: Thinking about this again.. perhaps a better approach would be to force the embedder to define the symbol in their binary. That is, libpython.x doesn't define Py_FatalError. The binary that links in libpython defines it. (and a "me too" on Jonathan's comments.. fo

[issue1195571] simple callback system for Py_FatalError

Jonathan McDougall added the comment: While trying to come up with a patch, I'm starting to realize the number of modifications needed to make this work. Py_FatalError() is called all over the place assuming that it never returns. The scope of this feature is enormous. I'm wondering what would h

[issue1195571] simple callback system for Py_FatalError

Jonathan McDougall added the comment: The latest patch does not allow changing the default behaviour of aborting the process, which is for me a problem. I am both embedding and extending python using Boost.Python, but scripting is optional. In case python fails to initialize, I want to disable sc

[issue1195571] simple callback system for Py_FatalError

STINNER Victor added the comment: > Sorry, the documentation in the patch is wrong Can you update your patch please? -- ___ Python tracker ___ ___

[issue1195571] simple callback system for Py_FatalError

Amaury Forgeot d'Arc added the comment: Sorry, the documentation in the patch is wrong. It should be: "Cause :cfunc:`Py_FatalError` to invoke the given function before printing to standard error and aborting out of the process." I don't think it's worth making it more complex. If the applica

[issue1195571] simple callback system for Py_FatalError

STINNER Victor added the comment: fatalhook-2.patch: I don't understand the documentation. It says "Cause :cfunc:`Py_FatalError` to invoke the given function instead of printing to standard error and aborting out of the process.", but if the callback does nothing, the message+traceback is pri

[issue1195571] simple callback system for Py_FatalError

Gregory P. Smith added the comment: This makes sense, I'll add it to 3.3. -- assignee: -> gregory.p.smith nosy: +gregory.p.smith ___ Python tracker ___ __

[issue1195571] simple callback system for Py_FatalError

Changes by Tom Whittock : -- nosy: +Tom.Whittock ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue1195571] simple callback system for Py_FatalError

Changes by Antoine Pitrou : -- nosy: +haypo versions: +Python 3.3 -Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue1195571] simple callback system for Py_FatalError

Changes by Amaury Forgeot d'Arc : Added file: http://bugs.python.org/file19098/fatalhook-2.patch ___ Python tracker ___ ___ Python-bugs-list

[issue1195571] simple callback system for Py_FatalError

Changes by Amaury Forgeot d'Arc : Removed file: http://bugs.python.org/file19096/fatalhook-2.patch ___ Python tracker ___ ___ Python-bugs-li

[issue1195571] simple callback system for Py_FatalError

Changes by Amaury Forgeot d'Arc : Added file: http://bugs.python.org/file19096/fatalhook-2.patch ___ Python tracker ___ ___ Python-bugs-list

[issue1195571] simple callback system for Py_FatalError

Amaury Forgeot d'Arc added the comment: Here is a new patch; I lifted the pre-Py_Initialize() restriction, because it seems to me that a wxPython application, for example, could use it. A wxPython application is not embedded, but it already often redirects stdout and even installs a segfault h

[issue1195571] simple callback system for Py_FatalError

Changes by Mark Lawrence : -- versions: +Python 3.2 -Python 2.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue1195571] simple callback system for Py_FatalError

Changes by James William Pye : -- nosy: -jwpye ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue1195571] simple callback system for Py_FatalError

James William Pye added the comment: I guess it seemed so unlikely that (C) extensions should be installing the callback that installation should be restricted pre-Py_Initialize(); the area completely controlled by the embedding app. However, I have no strong attachment to that. --

[issue1195571] simple callback system for Py_FatalError

Antoine Pitrou added the comment: This sounds like a good idea but why the strange semantics of needing it to be defined before calling PyInitialize()? -- nosy: +pitrou ___ Python tracker __

[issue1195571] simple callback system for Py_FatalError

James William Pye added the comment: Would it be possible to require the embedding application to define the Py_FatalError symbol? Admittedly, it would be nice to not have the callback installation code. =\ -- ___ Python tracker

[issue1195571] simple callback system for Py_FatalError

Georg Brandl added the comment: Amaury, any interest in getting this committed for 3.2? -- nosy: +georg.brandl ___ Python tracker ___ _

[issue1195571] simple callback system for Py_FatalError

Amaury Forgeot d'Arc added the comment: Here is a refreshed patch against trunk. Since the previous one did not provide any context, I hope I copied the lines in the right locations. -- keywords: +needs review nosy: +amaury.forgeotdarc Added file: http://bugs.python.org/file14440/fatalh

[issue1195571] simple callback system for Py_FatalError

Changes by STINNER Victor : -- nosy: -haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue1195571] simple callback system for Py_FatalError

James William Pye added the comment: I had actually forgotten that this was still open. Anything I can do to help speed this along? In case nobody remembers, the purpose of this was to provide a facility to embedded applications that allows for a more graceful shutdown in fatal error situations

[issue1195571] simple callback system for Py_FatalError

Changes by Daniel Diniz : -- nosy: +haypo stage: -> test needed title: simple callback system for Py_FatalError -> simple callback system for Py_FatalError type: -> feature request versions: +Python 2.7 -Python 2.4 ___ Python tracker