On Mon, Dec 5, 2011 at 7:08 AM, Terry Reedy wrote:
> My inclination would be #4 on Windows, certainly for 3.3, unless there is a
> clear reason not to.
Yes, there is: that environment is the *exact* environment that should
be passed to the child processes. It's not our place to go implicitly
addi
On 12/4/2011 5:59 AM, Tim Golden wrote:
http://bugs.python.org/issue13524
Someone raised issue13524 yesterday to illustrate that a
subprocess will crash immediately if an environment block is
passed which does not contain a valid SystemRoot environment
variable.
Note that the calling (Python) p
That's why I'm suggesting we look specifically at the cases where *Python*
misbehaves in an empty environment on Windows. Those are legitimately our
issue.
The problem in *general* is a platform one, so I don't think it makes sense
for us to modify the environment that has explicitly been passed i
On 04/12/2011, Tim Golden wrote:
>
> Someone raised issue13524 yesterday to illustrate that a
> subprocess will crash immediately if an environment block is
> passed which does not contain a valid SystemRoot environment
> variable.
...
> 2) Add a doc warning (ironically, considering the recent to-
On 04/12/2011 12:41, Paul Moore wrote:
I'm not 100% clear on the problem here. From how I'm reading things,
the problem is that not supplying SystemRoot will cause (some or all)
invocations of subprocess.Popen to fail - it's not specific to
starting Python.
That's basically the situation.
My
On 4 December 2011 12:20, Tim Golden wrote:
> On 04/12/2011 11:42, Nick Coghlan wrote:
>>
>> There's actually two questions to be answered:
>> 1. What should we do in 3.2 and 2.7?
>> 2. Should we do anything more in 3.3?
See below...
> This is actually a separate issue: how much of Python will w
On 04/12/2011 11:42, Nick Coghlan wrote:
There's actually two questions to be answered:
1. What should we do in 3.2 and 2.7?
2. Should we do anything more in 3.3?
Agreed.
1. Unset 'SystemRoot' in a windows shell
2. Run the test suite and observe the scale of the breakage
Sorry; something I
On Sun, Dec 4, 2011 at 8:59 PM, Tim Golden wrote:
> So... what's our take on this? As I see it we could:
>
> 1) Do nothing: it's the caller's responsibility to understand the
> complications of the chosen Operating System.
>
> 2) Add a doc warning (ironically, considering the recent to-and-fro
>
http://bugs.python.org/issue13524
Someone raised issue13524 yesterday to illustrate that a
subprocess will crash immediately if an environment block is
passed which does not contain a valid SystemRoot environment
variable.
Note that the calling (Python) process is unaffected; this
isn't - strict
> However given advances in locking and garbage collection in the last
> decade, what attempts have been made recently to try these new ideas
> out?
If that's the question you want an answer to, it would have been better
had you listed the efforts that you are already aware of. If you really
are u
Am 04.12.2011 03:55, schrieb Terry Reedy:
> On 12/3/2011 3:58 PM, Antoine Pitrou wrote:
>> On Sat, 3 Dec 2011 21:39:03 +0100
>> Antoine Pitrou wrote:
>>>
>>> One primary example is the performance question:
>>> file:///home/antoine/cpython/32/Doc/build/html/faq/programming.html#my-program-is-too-s
11 matches
Mail list logo
