Am 19.01.2013 20:30, schrieb Benjamin Peterson:
> It's been almost a year since 2.7.3, so it's time for another 2.7
> bugfix release.
>
> 2013-02-02 - 2.7.4 release branch created; rc released
> 2013-02-16 - 2.7.4 released
>
> Does this work for you, Martin and Ned?
I would propose to sync this
I don't have a concrete case where a socket object's setblocking() method
is called with a value in one module, handed off to another module (which
does not know what the first did with it) which in turn also calls
setblocking() with the same value. It certainly seems that that not is a
common patt
On Sat, Jan 19, 2013 at 8:49 PM, Peter Portante
wrote:
> I noticed while stracing a process that sock.setblocking() calls always
> result in pairs of fcntl() calls on Linux. Checking 2.6.8, 2.7.3, and 3.3.0
> Modules/socketmodule.c, the code seems to use the following (unless I have
> missed somet
2013/1/19 Peter Portante :
> Hello folks,
>
> I noticed while stracing a process that sock.setblocking() calls always
> result in pairs of fcntl() calls on Linux. Checking 2.6.8, 2.7.3, and 3.3.0
> Modules/socketmodule.c, the code seems to use the following (unless I have
> missed something):
>
>
Hello folks,
I noticed while stracing a process that sock.setblocking() calls always
result in pairs of fcntl() calls on Linux. Checking 2.6.8, 2.7.3, and 3.3.0
Modules/socketmodule.c, the code seems to use the following (unless I have
missed something):
delay_flag = fcntl(s->sock_fd, F_GETFL
On Sat, 2013-01-19 at 14:30 -0500, Benjamin Peterson wrote:
> It's been almost a year since 2.7.3, so it's time for another 2.7
> bugfix release.
>
> 2013-02-02 - 2.7.4 release branch created; rc released
> 2013-02-16 - 2.7.4 released
>
> Does this work for you, Martin and Ned?
I have a pet issu
On Sat, Jan 19, 2013 at 9:30 PM, Benjamin Peterson wrote:
> It's been almost a year since 2.7.3, so it's time for another 2.7
> bugfix release.
>
> 2013-02-02 - 2.7.4 release branch created; rc released
> 2013-02-16 - 2.7.4 released
The Cape Town Python User Group is having a Python Bug Day next
In article
,
Benjamin Peterson wrote:
> It's been almost a year since 2.7.3, so it's time for another 2.7
> bugfix release.
>
> 2013-02-02 - 2.7.4 release branch created; rc released
> 2013-02-16 - 2.7.4 released
>
> Does this work for you, Martin and Ned?
That works for me. There are also s
It's been almost a year since 2.7.3, so it's time for another 2.7
bugfix release.
2013-02-02 - 2.7.4 release branch created; rc released
2013-02-16 - 2.7.4 released
Does this work for you, Martin and Ned?
--
Regards,
Benjamin
___
Python-Dev mailing li
