There you go.
Obsoleted-By (optional)
:::
Indicates that this project is no longer being developed. The named
project provides a substitute or replacement.
A version declaration may be supplied and must follow the rules described
in `Version Specifiers`_.
The most common u
http://bugs.python.org/issue16715
I assume that someone changes the LoadError class and goes into the revert
function. How he can figure out that the cookies should return to the previous
state if LoadError was raised ?
___
Python-Dev mailing list
Pyth
Nick Coghlan wrote:
The problem is the mechanism is *not the same* on Windows and POSIX -
the Windows mechanism (noinherit) means the file won't be accessible
in child processes, the POSIX mechanism (cloexec) means it won't
survive exec().
But since there is no such thing as a fork without exe
In article <3ykxmg1ndxz...@mail.python.org>,
giampaolo.rodola wrote:
> http://hg.python.org/cpython/rev/88fadc0d7b20
> changeset: 81498:88fadc0d7b20
> branch: 3.3
> parent: 81495:e1c81ab5ad97
> user:Giampaolo Rodola'
> date:Mon Jan 14 02:24:25 2013 +0100
> summary:
>
2013/1/14 Nick Coghlan :
> I'm a fan of the conservative approach, with an environment variable
> and command line option to close FDs by default in 3.4 (similar to
> PYTHONHASHSEED and -R in the pre-3.3 security releases), and the
> cloexec/noinherit behaviour becoming the default (with no way to
On 01/12/2013 02:46 PM, Eli Bendersky wrote:
The first report is legit, however. PyTuple_New(0) was called and its
return value wasn't checked for NULL.
The author might have been relying on Python caching the empty tuple.
___
Python-Dev mailing list
On Mon, Jan 14, 2013 at 9:23 PM, Victor Stinner
wrote:
>>> XXX Should ``subprocess.Popen`` set the close-on-exec flag on file XXX
>>> XXX descriptors of the constructor the ``pass_fds`` argument? XXX
>>
>> What?
>> Setting them cloexec would prevent them from being inherited in the
>> child p
On Mon, Jan 14, 2013 at 9:23 PM, Victor Stinner
wrote:
> I'm not sure that it's so different than the change on subprocess
> (close_fds=True by default on UNIX since Python 3.2). Do you think
> that it would break more applications?
Don't ignore the possible explanation that the intersection of t
Hi,
Thanks for your feedback, I already updated the PEP for most of your remarks.
2013/1/13 Charles-François Natali :
> Also, ISTM that Windows also supports this flag.
Yes it does, see Appendix: Operating system support > Windows.
>> .. note::
>>OpenBSD older 5.2 does not close the file de
On Mon, Jan 14, 2013 at 8:06 AM, Greg Ewing wrote:
> Nick Coghlan wrote:
>>
>> Agreed, but it's the security implications that let us even
>> contemplate the backwards compatibility break.
>
>
> I don't think that's a sufficient criterion for choosing a
> name. The backwards compatibility issue is
For the record, I do not know of any evidence whatsoever for a supposed
"split" between the tiny VPython community and the huge Python community
concerning floating point variables. Nor do I see anything in Python that
needs to be "fixed".
The new (currently experimental) version of VPython based
Since this was copied to the Python-Dev list, I want to go on record as
stating firmly that there is no evidence whatsoever to substantiate claims
that there has ever been some kind of conflict between VPython and Python.
Since __future__ was also mentioned, I'll take the opportunity to say that
I
On 13/01/2013 00:41, Victor Stinner wrote:
PEP: 433
Title: Add cloexec argument to functions creating file descriptors
Status: Draft
The PEP is still a draft. I'm sending it to python-dev to get a first review.
The main question is the choice between the 3 different options:
* don't set clo
Le Sun, 13 Jan 2013 19:58:52 -0700,
Bruce Sherwood a écrit :
> Since this was copied to the Python-Dev list, I want to go on record
> as stating firmly that there is no evidence whatsoever to
> substantiate claims that there has ever been some kind of conflict
> between VPython and Python.
>
> S
14 matches
Mail list logo
