On 18/10/2011 8:59 PM, Sam Partington wrote:
...
I added shebangs to
all files as appropriate for devel/stable branch, and initially I
changed the python build targets from "python -utt build.py" to
"./build.py" and I lost the -utt functionality which I could live
with.
Can't you just put the
On Tue, Oct 18, 2011 at 11:23 PM, Éric Araujo wrote:
>
> Looks like your entry went into the Interpreter Core section instead of
> Library.
That should be corrected.
>
> BTW, I don’t understand “3.x version will come as a separate patch” in
I think, he meant in a separate commit. :)
Senthil
_
Hi,
> diff --git a/Misc/NEWS b/Misc/NEWS
> --- a/Misc/NEWS
> +++ b/Misc/NEWS
> @@ -54,6 +54,9 @@
>the following case: sys.stdin.read() stopped with CTRL+d (end of file),
>raw_input() interrupted by CTRL+c.
>
> +- Issue #10860: httplib now correctly handles an empty port after port
> + d
On 18 October 2011 08:10, Vinay Sajip wrote:
>> Is very unexpected. And to do so silently, without warning will cause
>
> It's only unexpected if you don't read the PEP. From there:
>
> "The launcher may offer some conveniences for Python developers working
> interactively - for example, starting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
...
>> If you are only measuring json encoding of a few select pieces of
>> data then it's a microbenchmark. If you are measuring the whole
>> application (or a significant part of it) then I'm not sure
>> timeit is the right tool for that.
>>
>> Reg
>> From a desire to keep the launcher as simple as possible, and to minimise
> the
>> need to synchronise the launcher with command line parameter changes in
> future
>> versions of Python.
>
> As simple as possible yes... but no simpler. I think having
> pylauncher behave so differently in
