2011/3/4 Simon Cross :
> On Fri, Mar 4, 2011 at 3:26 PM, Victor Stinner
> wrote:
>> faulthandler is also a little bit special, because it is very specific
>> to CPython: it is based on CPython internal structures.
>
> If faulthandler is a public part of the standard library, what should
> other Py
On Fri, Mar 4, 2011 at 3:26 PM, Victor Stinner
wrote:
> faulthandler is also a little bit special, because it is very specific
> to CPython: it is based on CPython internal structures.
If faulthandler is a public part of the standard library, what should
other Python implementations do about impl
On Fri, Mar 4, 2011 at 11:05 PM, Simon Cross
wrote:
> There may be reasons for including a shiny new module in the standard
> library despite the drawbacks (the rest of the standard library might
> wish to use the new feature, for example). If there are such reasons
> it would be nice to see them
Le vendredi 04 mars 2011 à 15:05 +0200, Simon Cross a écrit :
> While I like this module I'm against it going into the standard
> library so soon. Modules need time to mature, develop and gain wide
> adoption outside the standard library where they are less constrained
> by maintaining compatibilit
On Fri, Mar 4, 2011 at 2:58 AM, Victor Stinner
wrote:
> Some months ago, I proposed a patch to display the Python backtrace on a
> segfault. The API was not stable, it was too for Python 3.2, and it was
> enabled by default. I wrote a module instead of a patch so it can be
> used on any version of
On Fri, 04 Mar 2011 13:40:16 +0100
Victor Stinner wrote:
> > I am still bothered by the fact that,
> >
> > >>> import faulthandler
> > >>> faulthandler.enable()
> > >>> import sys
> > >>> sys.stderr.close()
> > >>> sys.stderr = open('logs/error.log', 'wb')
> > >>> faulthandler.sigsegv()
> >
> >
Le vendredi 04 mars 2011 à 06:32 -0500, Scott Dial a écrit :
> On 3/4/2011 6:10 AM, Nick Coghlan wrote:
> > On Fri, Mar 4, 2011 at 10:58 AM, Victor Stinner
> > wrote:
> >> So, what do you think?
> >
> > Something we may want to consider is enabling it by default in
> > interactive mode, and also
On Fri, Mar 4, 2011 at 9:32 PM, Scott Dial
wrote:
> I am still bothered by the fact that,
>
import faulthandler
faulthandler.enable()
import sys
sys.stderr.close()
sys.stderr = open('logs/error.log', 'wb')
faulthandler.sigsegv()
>
> , does the wrong thing. In this inc
On 3/4/2011 6:10 AM, Nick Coghlan wrote:
> On Fri, Mar 4, 2011 at 10:58 AM, Victor Stinner
> wrote:
>> So, what do you think?
>
> Something we may want to consider is enabling it by default in
> interactive mode, and also when `-i` is specified on the command line.
I am still bothered by the fac
Le vendredi 04 mars 2011 à 21:10 +1000, Nick Coghlan a écrit :
> > Some months ago, I proposed a patch to display the Python backtrace on a
> > segfault. The API was not stable, it was too for Python 3.2, and it was
> > enabled by default. I wrote a module instead of a patch so it can be
> > used o
On Fri, Mar 4, 2011 at 10:58 AM, Victor Stinner
wrote:
> Hi,
>
> Some months ago, I proposed a patch to display the Python backtrace on a
> segfault. The API was not stable, it was too for Python 3.2, and it was
> enabled by default. I wrote a module instead of a patch so it can be
> used on any v
Hi,
Some months ago, I proposed a patch to display the Python backtrace on a
segfault. The API was not stable, it was too for Python 3.2, and it was
enabled by default. I wrote a module instead of a patch so it can be
used on any version of Python, and it has a better API. And now I would
like to
12 matches
Mail list logo
