Hi,
I have a few more questions on the PEP 446:
(A) How should we support support where os.set_inheritable() is not
supported? Can we announce that os.set_inheritable() is always
available or not? Does such platform exist?
(B) Should subprocess make the file descriptors of pass_fds
inheritable?
From: Paul Moore
> I'm a bit confused by your comment about "people who prefer to associate
> scripts
> with an editor", though. This is only done in precisely those situations when
> the installer associates .py scripts with py.exe (the launcher). So if you
> switch that off, you don't get PATHE
On 27 July 2013 21:14, Steve Dower wrote:
> Any chance of this being made optional when installing? It provides no
> benefit for people who prefer to associate scripts with an editor and may
> be a source of confusion/complaints.
>
Personally, I don't know how to do this so someone else would h
Any chance of this being made optional when installing? It provides no benefit
for people who prefer to associate scripts with an editor and may be a source
of confusion/complaints.
Env var changes typically require a reboot to take full effect, which I've also
seen cause confusion.
Also, it s
2013/7/27 Guido van Rossum :
> P.S. perhaps more important than a PEP rewrite is a working patch to see how
> realistic this is. Could you make the alpha 1 release?
I already ran the whole Python test suite with non-inheritable file
descriptors when I developed the PEP 433: it just works. So I'm
c
P.S. perhaps more important than a PEP rewrite is a working patch to see
how realistic this is. Could you make the alpha 1 release?
On Saturday, July 27, 2013, Guido van Rossum wrote:
>
>
> On Saturday, July 27, 2013, Victor Stinner wrote:
>
>> 2013/7/27 Guido van Rossum :
>> > Do we even need a
On Saturday, July 27, 2013, Victor Stinner wrote:
> 2013/7/27 Guido van Rossum >:
> > Do we even need a new PEP, or should we just do it? Or can we adapt
> > Victor's PEP 446?
>
> I can rewrite the PEP 446 to:
>
> * make all file descriptors and handles non-inheritable
> * remove the cloexec param
2013/7/27 Guido van Rossum :
> Do we even need a new PEP, or should we just do it? Or can we adapt
> Victor's PEP 446?
I can rewrite the PEP 446 to:
* make all file descriptors and handles non-inheritable
* remove the cloexec parameter
* remove everything about non-blocking sockets (O_NONBLOCK),
On 23 July 2013 17:33, Paul Moore wrote:
> On 23 July 2013 17:11, "Martin v. Löwis" wrote:
>
>> Am 15.07.13 10:26, schrieb Paul Moore:
>> > Does anyone have any objections to this? I could try to write a patch,
>> > but I know next to nothing about building MSIs, so if any of the
>> > installer
