[Python-Dev] phd.pp.ru = phdru.name

2010-12-22 Thread Oleg Broytman
Hello! I need to inform people I'm changing my online identity. Domain
phd.pp.ru will die Dec 27 (I'll try to reregister it to extend its life
for a few months). My new personal domain will be phdru.name, primary
email will be phd (in case one makes a mistake and write phdru two
times - the address is an alias for phd).

The new domain is already delegated, email and site works. I'm working
on changing all my email subscriptions.

Oleg.
-- 
 Oleg Broytmanhttp://phd.pp.ru/p...@phd.pp.ru
   Programmers don't die, they just GOSUB without RETURN.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


[Python-Dev] issue 10296

2010-12-22 Thread Kristján Valur Jónsson
I have this defect here http://bugs.python.org/issue10296
ctypes catches BreakPoint error on windows 32
that I posted a while back and had no response to.  This is ctypes.  Would 
anyone care to take a look?
K
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] [python-committers] [RELEASED] Python 3.2 beta 2

2010-12-22 Thread Eric Smith

On 12/22/2010 8:46 AM, Georg Brandl wrote:

Am 22.12.2010 02:15, schrieb Nick Coghlan:

On Wed, Dec 22, 2010 at 6:18 AM, Georg Brandlge...@python.org  wrote:

Since PEP 3003, the Moratorium on Language Changes, is in effect, there
are no changes in Python's syntax and built-in types in Python 3.2.


Minor nit - we actually did tweak a few of the builtin types a bit
(mostly the stuff to improve Sequence ABC conformance and to make
range objects more list-like)


Indeed, I'll fix this wording for the next announcement.  (And I will
mention SSL, sorry Antoine).


If you're only going to mention some vague some builtins had minor 
changes, then I'm fine with that. If you're going to enumerate all such 
changes, that will be a bigger job. There were 2 such changes I'm aware 
of: str.format_map (#6081) and the addition of alternate (#) 
formatting to float, complex and decimal (#7094) __format__ methods.


For this announcement I don't think it's necessary to list them all.

___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] nonlocal x = value

2010-12-22 Thread Laurens Van Houtven
On Sat, Dec 18, 2010 at 1:12 PM, Georg Brandl g.bra...@gmx.net wrote:
 Am 17.12.2010 17:52, schrieb Laurens Van Houtven:
 +1 for throwing it out of the PEP. Assignment is a thing,
 nonlocal/global is a thing, don't mix them up :) (That in addition to
 the grammar cleanliness argument Stephan already made)

 The trouble is what to make of

 nonlocal x = 3, y

 Is it two nonlocal declarations or one with a tuple assignment?

 Georg

I'm not sure I understand. Isn't that another reason to throw it out?
If you don't allow such assignments, there can't be any ambiguity,
right? (Or am I missing something?)

lvh
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] nonlocal x = value

2010-12-22 Thread Terry Reedy

On 12/22/2010 5:11 PM, Laurens Van Houtven wrote:

On Sat, Dec 18, 2010 at 1:12 PM, Georg Brandlg.bra...@gmx.net  wrote:

Am 17.12.2010 17:52, schrieb Laurens Van Houtven:

+1 for throwing it out of the PEP. Assignment is a thing,
nonlocal/global is a thing, don't mix them up :) (That in addition to
the grammar cleanliness argument Stephan already made)


The trouble is what to make of

nonlocal x = 3, y

Is it two nonlocal declarations or one with a tuple assignment?

Georg


I'm not sure I understand. Isn't that another reason to throw it out?


I am sure he meant it to be, and I agree. We lived without
global x = 3, y
all these years.


If you don't allow such assignments, there can't be any ambiguity,
right? (Or am I missing something?)



--
Terry Jan Reedy

___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


[Python-Dev] Fault handler updated, now disabled by default

2010-12-22 Thread Victor Stinner
Hi,

Thanks to all your useful remarks, I improved my patch twice (version 10
and 11). I think that the last version (11) addresses all reported
issues. The most notable change is that the fault handler is now
disabled by default. It fixes also the function getting the thread
state, it now works in all cases (especially if the thread causing the
fault doesn't hold the GIL).

Summary of the patch (#8863):

 - Add an optional fault handler for SIGSEGV, SIGFPE, SIGILL and SIGBUS
signals displaying the Python backtrace
 - Setting PYTHONFAULTHANDLER environment variable, or using
   -X faulthandler command line option, enables it
 - If it's enabled, display also the Python backtrace on a fatal error

Use case: when a program crashs, the user reruns its application with
the fault handler enabled and tries to reproduce the crash. He/She can
send the Python backtrace to the developer, or use it directly (if
he/she understands it).

I think that this patch helps to isolate crashs in Python or libraries,
especially if the user doesn't have all tools needed to get a Python
backtrace (on a crash) and the developer is unable to reproduce the bug
(because it doesn't have the same OS or libraries). For example, gdb 7
and python-gdb.py are rare on Windows :-) (even on Linux!)

So, do you agree with the fault handler? Does someone want to give a
last review because I commit it?

http://bugs.python.org/issue8863

Victor

___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Issue #8863 adds a new?PYTHONNOFAULTHANDLER?environment variable

2010-12-22 Thread Victor Stinner
Le lundi 20 décembre 2010 à 13:09 -0500, Alexander Belopolsky a écrit :
 What if the program crashes (again) in the signal handler before
 having a chance to restore registers?

If the fault handler crashs, the registers are not restored.

 Also, can you point to documentation that describes register restoring 
 behavior?

I found an article telling that the kernel saves integer and float
registers when calling a signal handler, but I am unable to find it
again, sorry. And I cannot find an article telling the opposite.

Anyway, it would just be horrible if a signal handler was responsible to
save/restore integer registers. If the kernel doesn't do that for us, I
suppose that the compiler or something else does it for us.

Eg. signal_default_int_handler(), the Python handler of SIGINT signal,
doesn't save/restore registers, even if it erases many of them.

 Because I had actual experience with that using R.  Your code may be
 better, but R brings up a dialog on segfault asking ...

You cannot compare a simple handler using simple signal-safe functions
like write(), and a complex handler calling graphical functions. It is
not safe to call graphical functions in a signal handler.

 (I actually use RPy which loads R into  Python as a shared library, 
 so the two handlers will conflict anyways.)

It depends if R handler calls the previous handler. My fault handler is
chained with the previous handler (it calls indirectly the previous
handler). If R fault handler does the same, all handlers will be
executed correctly (I don't think that the execution order matter).

Victor

___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Fault handler updated, now disabled by default

2010-12-22 Thread Martin v. Löwis
 So, do you agree with the fault handler? Does someone want to give a
 last review because I commit it?

It's a new feature, so regardless of whether it's correct or not
(which I haven't reviewed yet), I don't think it should go in before
3.2 is released.

Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com