Re: [Python-Dev] Request for pronouncement on PEP 493 (HTTPS verification backport guidance)

On 17 November 2015 at 20:33, Victor Stinner wrote: > 2015-11-17 1:00 GMT+01:00 Guido van Rossum : >> Hm, making Christian the BDFL-delegate would mean two out of three >> authors *and* the BDFL-delegate all working for Red Hat, which clearly >> has a

Re: [Python-Dev] Reading Python source file

On 17.11.15 17:22, Guido van Rossum wrote: But more important is the interactive REPL, which parses your input fully each time you hit ENTER. Interactive REPL runs different code. It is simpler that the code for reading from file, because it have no care about BOM or coding cookie.

Re: [Python-Dev] Reading Python source file

On 17.11.15 18:06, Guido van Rossum wrote: OK, but what are you going to do about the interactive REPL? Nothing (except some simplification). This is a separate branch of the code. ___ Python-Dev mailing list Python-Dev@python.org

Re: [Python-Dev] Reading Python source file

OK, but what are you going to do about the interactive REPL? On Tue, Nov 17, 2015 at 7:40 AM, Serhiy Storchaka wrote: > On 17.11.15 05:00, Guido van Rossum wrote: >> >> If you free the memory used for the source buffer before starting code >> generation you should be good. >

Re: [Python-Dev] Reading Python source file

On 17.11.15 05:05, MRAB wrote: As I understand it, *nix expects the shebang to be b'#!', which means that the first line should be ASCII-compatible (it's possible that the UTF-8 BOM might be present). This kind of suggests that encodings like UTF-16 would cause a problem on such systems. The

Re: [Python-Dev] Reading Python source file

On 17.11.15 11:59, M.-A. Lemburg wrote: I don't think these situations are all that common, though, so reading in the full source code before compiling it sounds like a reasonable approach. We use the same simplification in eGenix PyRun's emulation of the Python command line interface and it

Re: [Python-Dev] Reading Python source file

On Tue, Nov 17, 2015 at 1:59 AM, M.-A. Lemburg wrote: > On 17.11.2015 02:53, Serhiy Storchaka wrote: >> I'm working on rewriting Python tokenizer (in particular the part that reads >> and decodes Python >> source file). The code is complicated. For now there are such cases: >>

Re: [Python-Dev] Reading Python source file

On 17.11.15 05:00, Guido van Rossum wrote: If you free the memory used for the source buffer before starting code generation you should be good. Thank you. The buffer is freed just after the end of generating AST. On Mon, Nov 16, 2015 at 5:53 PM, Serhiy Storchaka wrote:

Re: [Python-Dev] Reading Python source file

On Tue, Nov 17, 2015 at 8:20 AM, Serhiy Storchaka wrote: > On 17.11.15 11:59, M.-A. Lemburg wrote: >> >> I don't think these situations are all that common, though, >> so reading in the full source code before compiling it >> sounds like a reasonable approach. >> >> We use

Re: [Python-Dev] Reading Python source file

Oh, cool! Sorry for the disturbance. On Tue, Nov 17, 2015 at 8:27 AM, Serhiy Storchaka wrote: > On 17.11.15 18:06, Guido van Rossum wrote: >> >> OK, but what are you going to do about the interactive REPL? > > > Nothing (except some simplification). This is a separate branch

Re: [Python-Dev] Request for pronouncement on PEP 493 (HTTPS verification backport guidance)

2015-11-17 1:00 GMT+01:00 Guido van Rossum : > Hm, making Christian the BDFL-delegate would mean two out of three > authors *and* the BDFL-delegate all working for Red Hat, which clearly > has a stake (and IIUC has already committed to this approach ahead of > PEP approval). SO

Re: [Python-Dev] Benchmark results across all major Python implementations

On Mon, 16 Nov 2015 23:37:06 +, "Stewart, David C" wrote: > Last June we started publishing a daily performance report of the latest > Python tip against the previous day's run and some established synch point. > We mail these to the community to act as a "canary

Re: [Python-Dev] Benchmark results across all major Python implementations

+Stefan (owner of the 0-day lab) On 11/17/15, 10:40 AM, "Python-Dev on behalf of R. David Murray" wrote: >On Mon, 16 Nov 2015 23:37:06 +, "Stewart, David C" > wrote:

Re: [Python-Dev] Reading Python source file

Aha, so the only code path that's being replaced is the code that reads the script file when invoking "python FILE" or "python

Re: [Python-Dev] Reading Python source file

On 18 November 2015 at 02:50, Guido van Rossum wrote: > On Tue, Nov 17, 2015 at 8:20 AM, Serhiy Storchaka wrote: >> On 17.11.15 11:59, M.-A. Lemburg wrote: >>> >>> I don't think these situations are all that common, though, >>> so reading in the full source

Re: [Python-Dev] Reading Python source file

On 17.11.2015 02:53, Serhiy Storchaka wrote: > I'm working on rewriting Python tokenizer (in particular the part that reads > and decodes Python > source file). The code is complicated. For now there are such cases: > > * Reading from the string in memory. > * Interactive reading from the file.

Re: [Python-Dev] [Python-checkins] Daily reference leaks (97e2a6810f7f): sum=10

Hi, I opened the http://bugs.python.org/issue25645 It looks like a simple regression in _pickle. I wrote a patch. Victor 2015-11-16 19:49 GMT+01:00 Brett Cannon : > Just an FYI there seems to be a consistent, minor refcount leak found by > test_capi that has been there for

Re: [Python-Dev] Benchmark results across all major Python implementations

Hi Python community, Thank you for your feedback! We will look into this and come up with an e-mail format proposal in the following days. Best regards, -- Stefan A. POPA Software Engineering Manager System Technologies and Optimization Division Software Services Group, Intel Romania > On 17

Re: [Python-Dev] Benchmark results across all major Python implementations

Stewart, David C writes: > Note: PGO is not the default way to build Python because it is > relatively slow to compile it that way. (I think it should be the > default). +1 Slow-build-fast-run should be the default if you're sure the optimization works. Only developers are likely to run a