Re: [Python-Dev] [RELEASED] Python 3.1 final

2009-06-27 Thread Nick Coghlan
Benjamin Peterson wrote: > On behalf of the Python development team, I'm thrilled to announce the first > production release of Python 3.1. Excellent news! Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia --

Re: [Python-Dev] [RELEASED] Python 3.1 final

2009-06-27 Thread Arc Riley
On Sat, Jun 27, 2009 at 6:59 PM, Christian Heimes wrote: > > Gratulations! You did a fantastic job! :) +1 ! ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailm

Re: [Python-Dev] [RELEASED] Python 3.1 final

2009-06-27 Thread Christian Heimes
Benjamin Peterson schrieb: > On behalf of the Python development team, I'm thrilled to announce the first > production release of Python 3.1. Gratulations! You did a fantastic job! :) Christian PS: I hope that I'm able to spare more of my work time on the development of Python 3.2 ... __

Re: [Python-Dev] [RELEASED] Python 3.1 final

2009-06-27 Thread Raymond Hettinger
On behalf of the Python development team, I'm thrilled to announce the first production release of Python 3.1. Sweet! Raymond ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http:/

[Python-Dev] [RELEASED] Python 3.1 final

2009-06-27 Thread Benjamin Peterson
On behalf of the Python development team, I'm thrilled to announce the first production release of Python 3.1. Python 3.1 focuses on the stabilization and optimization of the features and changes that Python 3.0 introduced. For example, the new I/O system has been rewritten in C for speed. File

Re: [Python-Dev] pthread sem PyThread_acquire_lock

2009-06-27 Thread Florian Mayer
Martin v. Löwis wrote: Can you please explain what you mean by "swallowing"? The signals don't get through when acquiring the lock. What is the sequence of actions triggering the case you are talking about, what happens, and what do you expect to happen instead? Easiest way is to create a Queue

Re: [Python-Dev] pthread sem PyThread_acquire_lock

2009-06-27 Thread Florian Mayer
Martin v. Löwis wrote: > Can you please explain what you mean by "swallowing"? The signals don't get through when acquiring the lock. > What is the sequence of actions triggering the case you are talking > about, what happens, and what do you expect to happen instead? Create a Lock object, call .a

Re: [Python-Dev] pthread sem PyThread_acquire_lock

2009-06-27 Thread Martin v. Löwis
> Now to my real question. I have noticed that PyThread_acquire_lock > swallows all signals with pthread using sems. Looking at the source code > it appears that this is intended, but I cannot see the reason for that. > It seems the pthread sem implementation is the only one doing so. Can > any of

[Python-Dev] pthread sem PyThread_acquire_lock

2009-06-27 Thread Florian Mayer
Hello. As this is my first post I will try to introduce myself as requested in the welcome email. If you aren't interested in my person, just continue reading at the next paragraph. I'm a student from Vienna/Austria. I attend what would match high school in the United States. I have been writi