[issue23601] use small object allocator for dict key storage

[Julian Taylor]

Julian Taylor added the comment:

Your benchmarks are not affected by this change see the other issue. They are 
also not representative of every workload out there.

I can at least see the argument why you didn't want to put the other variant of 
this change in as it made the code a tiny bit more complicated, but I do not 
understand the reluctance for this variant. It doesn't change the complexity of 
the code one bit.
If you doubt the performance of pythons own small object allocator, python 
should maybe stop using it alltogether?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18291] codecs.open interprets FS, RS, GS as line ends

[Martin Panter]

Changes by Martin Panter :


--
title: codecs.open interprets space as line ends -> codecs.open interprets FS, 
RS, GS as line ends

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22232] str.splitlines splitting on non-\r\n characters

[Martin Panter]

Martin Panter added the comment:

The main documentation has been updated and Issue 12855 has been closed. What 
is left to do here, considering this is marked as a documenation bug? Just 
modify the doc strings, as Terry suggested in 
?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24567] random.choice IndexError due to double-rounding

[Antoine Pitrou]

Antoine Pitrou added the comment:

> I propose to rewrite Random.randint() in random.py.

If that would give a different sequence of random numbers, I'm not sure that's 
acceptable in a bugfix release. Raymond can shed a light.

--
stage:  -> needs patch
versions:  -Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24601] bytes and unicode splitlines() methods differ on what is a line break

[Martin Panter]

Martin Panter added the comment:

* Issue 7643: Originally a complaint about the difference, but was closed after 
adding more differences!
* Issue 22232: Documentation bug, but with some discussion on changing the API. 
Maybe a duplicate?
* Issue 22233: Email and HTTP message parsing bug related to incorrectly using 
splitlines()
* Issue 18291: codecs.StreamReader uses splitlines(), but io.TextIOWrapper uses 
universal newlines

--
nosy: +vadmium

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24567] random.choice IndexError due to double-rounding

[STINNER Victor]

STINNER Victor added the comment:

As I wrote, glib switch from floats to integers to generate random
numbers. To provide reproductible "random" numbers, an environment
variable was added to select the old PRNG.

Anyway, if we modify random.py, the generated numbers should be different, no?

To me, it's always a strange concept of having reproductible "random"
numbers :-) But I understand the use case. For example, to run a test
suite, we want randomization and to be able to replay a test suite in
the same order.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24567] random.choice IndexError due to double-rounding

[Antoine Pitrou]

Antoine Pitrou added the comment:

> As I wrote, glib switch from floats to integers to generate random
> numbers.

And as I wrote, this would be accepted in a feature release. Not necessarily a 
bugfix release.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24603] New update of OpenSSL

[Friedrich Spee von Langenfeld]

New submission from Friedrich Spee von Langenfeld:

The developers of OpenSSL have published a new update. It fixes a bug marked as 
severe (https://www.openssl.org/news/secadv_20150709.txt). It seems that we are 
using a vulnerable version. Could someone who knows the relevant files' 
locations update our repository? Many thanks in advance.

--
components: Build
messages: 246552
nosy: Friedrich.Spee.von.Langenfeld
priority: normal
severity: normal
status: open
title: New update of OpenSSL
type: security

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24603] New update of OpenSSL

[STINNER Victor]

STINNER Victor added the comment:

Yes, read the discussion on python-dev:
https://mail.python.org/pipermail/python-dev/2015-July/140706.html

Christian Heimes wrote:

"1.0.2c is only used in 3.5b3. The production builds are either using
1.0.2a or 1.0.1j."

Should I understand that only Windows installers of the beta version of Python 
3.5 are vulnerable?

--
components: +Windows
nosy: +haypo, paul.moore, steve.dower, tim.golden, zach.ware
versions: +Python 3.5

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24599] urllib URLopener().open https url returns 501 Not Implemented when https_proxy env var is http://

[Stefano Mazzucco]

Stefano Mazzucco added the comment:

Martin, thanks for elaborating my thoughts!

I have dug I bit deeper in Python2's urllib code with pdb, and I think I have 
narrowed the issue down to what open_http does.

In my example code, replacing opener.open(url) with opener.open_http(url) gives 
the same problem.

I realize I did not provide you with the output of the script, so here it is:

* Python 2.7.10

python urllib_error.py
('Trying to open', 'https://www.python.org')
Traceback (most recent call last):
  File "urllib_error.py", line 30, in 
opener.open_http((host, selector))
  File "/home/mazzucco/.pyenv/versions/2.7.10/lib/python2.7/urllib.py", line 
364, in open_http
return self.http_error(url, fp, errcode, errmsg, headers)
  File "/home/mazzucco/.pyenv/versions/2.7.10/lib/python2.7/urllib.py", line 
381, in http_error
return self.http_error_default(url, fp, errcode, errmsg, headers)
  File "/home/mazzucco/.pyenv/versions/2.7.10/lib/python2.7/urllib.py", line 
386, in http_error_default
raise IOError, ('http error', errcode, errmsg, headers)
IOError: ('http error', 501, 'Not Implemented', )

* Python 3.4.3

python urllib_error.py
Trying to open https://www.python.org
Traceback (most recent call last):
  File "urllib_error.py", line 30, in 
opener.open_http((host, selector))
  File "/home/mazzucco/.pyenv/versions/3.4.3/lib/python3.4/urllib/request.py", 
line 1805, in open_http
return self._open_generic_http(http.client.HTTPConnection, url, data)
  File "/home/mazzucco/.pyenv/versions/3.4.3/lib/python3.4/urllib/request.py", 
line 1801, in _open_generic_http
response.status, response.reason, response.msg, data)
  File "/home/mazzucco/.pyenv/versions/3.4.3/lib/python3.4/urllib/request.py", 
line 1821, in http_error
return self.http_error_default(url, fp, errcode, errmsg, headers)
  File "/home/mazzucco/.pyenv/versions/3.4.3/lib/python3.4/urllib/request.py", 
line 1826, in http_error_default
raise HTTPError(url, errcode, errmsg, headers, None)
urllib.error.HTTPError: HTTP Error 501: Not Implemented

When I unwrap the contents of httplib.HTTPMessage, the error page returned by 
the squid proxy says:

---
ERROR
The requested URL could not be retrieved

The following error was encountered while trying to retrieve the URL: 
https://www.python.org

Unsupported Request Method and Protocol

Squid does not support all request methods for all access protocols. For 
example, you can not POST a Gopher request.
---

Looking at Python2's implementation of URLopener's open_http, I can get an even 
more minimal failing example limited to httplib:


import httplib

host = 'proxy.corp.com:8181'  # this is not the actual proxy

selector = 'https://www.python.org'

print("Trying to open", selector)

h = httplib.HTTP(host)
h.putrequest('GET', selector)
h.putheader('User-Agent', 'Python-urllib/1.17')
h.endheaders(None)
errcode, errmsg, headers = h.getreply()

print(errcode, errmsg)
print(headers.items())


Running the script on Python 2.7.10 prints:

('Trying to open', 'https://www.python.org')
(501, 'Not Implemented')
[('content-length', '3069'), ('via', '1.0 proxy.corp.com (squid/3.1.6)'), 
('x-cache', 'MISS from proxy.corp.com'), ('content-language', 'en'), 
('x-squid-error', 'ERR_UNSUP_REQ 0'), ('x-cache-lookup', 'NONE from 
proxy.corp.com:8181'), ('vary', 'Accept-Language'), ('server', 'squid/3.1.6'), 
('proxy-connection', 'close'), ('date', 'Fri, 10 Jul 2015 09:27:14 GMT'), 
('content-type', 'text/html'), ('mime-version', '1.0')]


As I said, I found out about this when using buildout to download files over 
HTTPS.

Buildout uses urllib.urlretrieve on Python2 and urllib.request.urlretrieve on 
Python3. I guess that the latter has been fixed in issue 1424152, so that's why 
I can download with buildout on Python3.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue16487] Allow ssl certificates to be specified from memory rather than files.

[Martin Richard]

Martin Richard added the comment:

I'm not sure I know how to do this correctly: I lack of experience both
with openssl C API and writing python modules in C.

It may be more flexible, but unless the key is protected/crypted somehow,
one would need a string or bytes buffer to hold the key when creating the
private key object: not much secure. Don't you think that it should be
addressed in a separate issue?

2015-07-09 15:48 GMT+02:00 Christian Heimes :

>
> Christian Heimes added the comment:
>
> I'd rather introduce new types and have the function accept either a
> string (for path to fiel) or a X509 object and a PKey object. It's more
> flexible and secure. With a private key type we can properly support crypto
> ENGINEs and wipe memory when the object gets deallocated.
>
> --
>
> ___
> Python tracker 
> 
> ___
>

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24599] urllib URLopener().open https url returns 501 Not Implemented when https_proxy env var is http://

[Martin Panter]

Martin Panter added the comment:

Perhaps you might be able to test out the patch 
 to see if that fixes your problem? Though 
there is a good chance the patch needs updating, since it is fairly old.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24599] urllib URLopener().open https url returns 501 Not Implemented when https_proxy env var is http://

[Stefano Mazzucco]

Stefano Mazzucco added the comment:

Martin,

I have applied the patch  to my Python2.7.10 
installation and seem to work OK.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24604] problem to install scipy manually on Centos 6

[cbaud]

New submission from cbaud:

I'm working with the entreprise distribution Centos 6, unfortunatly the package 
pyhton3 proposed by the package manager yum isn't working. That why I had to 
install python manually, for that purpose I used pip3. Once again I had a 
problem with pip tool to install scipy, pip couldn't find blas and lapack.
The error message proposed to specify the location blas and lapack package, but 
even with that it didn't work. I found the answer on stackoverflow 
(http://stackoverflow.com/questions/4225/installing-scipy-and-numpy-using-pip)
 : you have to install blas-devel and lapack-devel to install scipy with pip3. 
Nothing was scepified on the document, it could help if some comment would be 
added.

--
components: Installation
messages: 246558
nosy: cbaud
priority: normal
severity: normal
status: open
title: problem to install scipy manually on Centos 6
versions: Python 3.3

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24605] segmentation fault at asciilib_split_char.lto_priv

[josch]

New submission from josch:

Hi,

sometimes (but not reliably reproducibly, one has to run it a few times) I get 
a segmentation fault when running the following networkx based Python code on 
large input graphs: 
https://gitlab.mister-muffin.de/debian-bootstrap/botch/blob/master/tools/graph-difference.py

I'm running Debian unstable with the python3.4 package of version 3.4.3-7 on 
architecture amd64.

The core dump is 1GB large so I'm just attaching the traceback from gdb.

The string "hscolour:amd64 (= 1.20.3-2)" that you see in the traceback is one 
of the vertex attributes in the input graph.

What else do you need to debug the problem?

#0  asciilib_split_char.lto_priv () at ../Objects/stringlib/split.h:126
#1  0x0058e65a in asciilib_split (maxcount=, sep_len=1, 
sep=0x7f1b3088dfb0 ",", str_len=27, 
str=0x7f1b230abfb0 "hscolour:amd64 (= 1.20.3-2)", str_obj='hscolour:amd64 
(= 1.20.3-2)') at ../Objects/stringlib/split.h:158
#2  split (maxcount=, substring=',', self='hscolour:amd64 (= 
1.20.3-2)') at ../Objects/unicodeobject.c:10099
#3  unicode_split.lto_priv () at ../Objects/unicodeobject.c:12639
#4  0x0050d8fe in call_function (oparg=, 
pp_stack=0x7ffdf1a8ed80) at ../Python/ceval.c:4237
#5  PyEval_EvalFrameEx () at ../Python/ceval.c:2838
#6  0x005ab095 in PyEval_EvalCodeEx () at ../Python/ceval.c:3588
#7  0x0051163d in fast_function (nk=, na=, n=, pp_stack=0x7ffdf1a8ef60, 
func=) at ../Python/ceval.c:4344
#8  call_function (oparg=, pp_stack=0x7ffdf1a8ef60) at 
../Python/ceval.c:4262
#9  PyEval_EvalFrameEx () at ../Python/ceval.c:2838
#10 0x005ab095 in PyEval_EvalCodeEx () at ../Python/ceval.c:3588
#11 0x0051163d in fast_function (nk=, na=, n=, pp_stack=0x7ffdf1a8f140, 
func=) at ../Python/ceval.c:4344
#12 call_function (oparg=, pp_stack=0x7ffdf1a8f140) at 
../Python/ceval.c:4262
#13 PyEval_EvalFrameEx () at ../Python/ceval.c:2838
#14 0x005ab095 in PyEval_EvalCodeEx () at ../Python/ceval.c:3588
#15 0x0051163d in fast_function (nk=, na=, n=, pp_stack=0x7ffdf1a8f320, 
func=) at ../Python/ceval.c:4344
#16 call_function (oparg=, pp_stack=0x7ffdf1a8f320) at 
../Python/ceval.c:4262
#17 PyEval_EvalFrameEx () at ../Python/ceval.c:2838
#18 0x005ab095 in PyEval_EvalCodeEx () at ../Python/ceval.c:3588
#19 0x005e16a5 in PyEval_EvalCode (
locals={'__package__': None, '__doc__': None, '__spec__': None, 'sys': 
, 'graph_difference': , '__file__': './tools/graph-difference.py', '__builtins__': 
, 'parser': 
, _registries={'action': {'append': , 
'store_true': , 'store_false': , 'help': , 'count': , 'append_const': , 'store': , None: , 'store_const': , 'version': , 'parsers': }, 'type': {None: }}, _group_actions=[<_StoreAction(d...(truncated), 
globals={'__package__': None, '__doc__': None, '__spec__': None, 'sys': 
, 'graph_difference': , '__file__': './tools/graph-difference.py', '__builtins__': 
, 'parser': 
, _registries={'action': {'append': , 
'store_true': , 'store_false': , 'help': , 'count': , 'append_const': , 'store': , None: , 'store_const': , 'version': , 'parsers': }, 'type': {None: }}, _group_actions=[<_StoreAction(d...(truncated), co=) at ../Python/ceval.c:775
#20 run_mod () at ../Python/pythonrun.c:2180
#21 0x005e176a in PyRun_FileExFlags () at ../Python/pythonrun.c:2133
#22 0x005e237a in PyRun_SimpleFileExFlags () at 
../Python/pythonrun.c:1606
#23 0x005fdb60 in run_file (p_cf=, filename=, fp=) at ../Modules/main.c:319
#24 Py_Main () at ../Modules/main.c:751
#25 0x004c234f in main () at ../Modules/python.c:69
#26 0x7f1b30972b45 in __libc_start_main () from 
/lib/x86_64-linux-gnu/libc.so.6
#27 0x005ba765 in _start ()

--
messages: 246559
nosy: josch
priority: normal
severity: normal
status: open
title: segmentation fault at asciilib_split_char.lto_priv
versions: Python 3.4

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24604] problem to install scipy manually on Centos 6

[STINNER Victor]

STINNER Victor added the comment:

Sorry, this is the bug tracker of the Python language. See the 
http://www.scipy.org/ website to report bugs on scipy, thank you.

--
nosy: +haypo
resolution:  -> not a bug
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24605] segmentation fault at asciilib_split_char.lto_priv

[STINNER Victor]

STINNER Victor added the comment:

It looks more like a bug in networkx, than a bug in Python itself. networkx has 
probably issues with reference counter, concurrency (threads), or things like 
that.

I'm unable to reproduce the crash on Python 3.4 (system binary from Fedora 22) 
or Python 3.6 (compiled manually).


haypo@smithers$ ./python
Python 3.6.0a0 (default:bb9fc884a838, Jul  6 2015, 15:27:15) 
[GCC 5.1.1 20150618 (Red Hat 5.1.1-4)] on linux
>>> "hscolour:amd64 (= 1.20.3-2)".split()
['hscolour:amd64', '(=', '1.20.3-2)']
>>> "hscolour:amd64 (= 1.20.3-2)".split(",")
['hscolour:amd64 (= 1.20.3-2)']
>>> len("hscolour:amd64 (= 1.20.3-2)")
27


haypo@smithers$ python3
Python 3.4.2 (default, Jan 12 2015, 12:13:20) 
[GCC 4.9.2 20150107 (Red Hat 4.9.2-5)] on linux
>>> "hscolour:amd64 (= 1.20.3-2)".split()
['hscolour:amd64', '(=', '1.20.3-2)']
>>> "hscolour:amd64 (= 1.20.3-2)".split(",")
['hscolour:amd64 (= 1.20.3-2)']
>>> len("hscolour:amd64 (= 1.20.3-2)")
27

--
nosy: +haypo

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24605] segmentation fault at asciilib_split_char.lto_priv

[STINNER Victor]

STINNER Victor added the comment:

Oh, networkx looks to be written in pure Python. You should search for a module 
implemented in C.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24599] urllib URLopener().open https url returns 501 Not Implemented when https_proxy env var is http://

[Lukas Wunner]

Lukas Wunner added the comment:

Thank you Martin for referencing my patch. It still applies cleanly with 
--fuzz=0 to 2.7.10. Would be awesome if this fix would finally get merged.

--
nosy: +l

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24603] Update OpenSSL to 1.0.2d in Windows and OS X installer

[Ned Deily]

Ned Deily added the comment:

The Windows installer and the 32-bit-only OS X installer both have local copies 
of OpenSSL.  At the moment, only the 3.5.0 betas have been released with 1.0.2. 
 Setting to release blocker priority for 3.5.0b4.

--
nosy: +benjamin.peterson, larry, ned.deily
priority: normal -> release blocker
title: New update of OpenSSL -> Update OpenSSL to 1.0.2d in Windows and OS X 
installer
versions: +Python 2.7, Python 3.4, Python 3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24603] Update OpenSSL to 1.0.2d in Windows and OS X installer

[STINNER Victor]

Changes by STINNER Victor :


--
components: +Macintosh
nosy: +ronaldoussoren

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24567] random.choice IndexError due to double-rounding

[Tim Peters]

Tim Peters added the comment:

> Anyway, if we modify random.py, the generated
> numbers should be different, no?

Not in a bugfix release.  The `min()` trick changes no results whatsoever on a 
box that doesn't do double-rounding.

On a box that does do double-rounding, the only difference in results is that 
the `min()` trick stops a nasty exception in a relative handful of cases (& 
makes no difference to any case in which that exception isn't raised).

The sequence of results may be different on platforms with double-rounding and 
without double-rounding, but that's always been true.  The `min()` trick 
changes nothing about that either, except to prevent unintended exceptions on 
double-rounding boxes.

Note that switching to use SSE2 instead also changes nothing on boxes that 
don't do double-rounding.  It would change some results (beyond _just_ stopping 
bogus exceptions) on boxes that do double-rounding.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24567] random.choice IndexError due to double-rounding

[STINNER Victor]

STINNER Victor added the comment:

Ok, it looks like most people are in favor of min(). Can anyone propose a patch?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24606] segfault caused by nested calls to map()

[David Lukeš]

New submission from David Lukeš:

The following program makes Python 3.4.3 crash with a segmentation fault:

```
#!/usr/bin/env python3

import operator

N = 50
l = [0]

for i in range(N):
l = map(operator.add, l, [1])

print(list(l))
```

I suppose the problem is that there are too many nested lazy calls to map, 
which cause a segfault when evaluated. I've played with N and surprisingly, the 
threshold to cause the crash varied slightly (between 130900 and 131000 on my 
machine).

I know that a list-comprehension, which is evaluated straight away, would be 
much more idiomatic for repeated element-wise addition (or numpy arrays for 
that matter, if available). I'm **not advocating this piece of code**, just 
wondering whether there couldn't be a more informative way to make Python bail 
out instead of the segfault? (In my real application, it took me a while to 
figure where the problem was without a stack trace.)

--
messages: 246567
nosy: David Lukeš
priority: normal
severity: normal
status: open
title: segfault caused by nested calls to map()
type: crash
versions: Python 3.4

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24601] bytes and unicode splitlines() methods differ on what is a line break

[Gregory P. Smith]

Gregory P. Smith added the comment:

hah, i should've searched the tracker first.  looks like the other open issues 
cover this.

--
resolution:  -> duplicate
status: open -> closed
superseder:  -> str.splitlines splitting on non-\r\n characters
versions: +Python 2.7, Python 3.4, Python 3.5, Python 3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22233] http.client splits headers on non-\r\n characters

[Gregory P. Smith]

Gregory P. Smith added the comment:

The obvious fix seems to be to not use splitlines but explicitly split on the 
allowed characters for ASCII based protocols and formats that only want \r and 
\n to be considered.

I don't think we can rightfully change the unicode splitlines behavior.

--
nosy: +gregory.p.smith
title: http.client splits headers on none-\r\n characters -> http.client splits 
headers on non-\r\n characters

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22232] str.splitlines splitting on non-\r\n characters

[Gregory P. Smith]

Gregory P. Smith added the comment:

If this isn't already mentioned in 2 to 3 porting notes it is worth 
highlighting there.  code which uses a str in python 2 and still uses a str in 
python 3 is now splitting on many more characters.

That seems to be the source of bugs like issue22233.  splitlines() used to work 
for the strict \r\n splitting task.  now that code needs to made explicit about 
its splitting desires.

--
nosy: +gregory.p.smith

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue23601] use small object allocator for dict key storage

[Stefan Behnel]

Stefan Behnel added the comment:

> Your benchmarks are not affected by this change see the other issue.

Then you ran them, I assume? Could you show the output here that you got?

> They are also not representative of every workload out there.

Certainly not, but they do provide a certain variety of workloads that
reduce the likelihood of not spotting a regression that this change might
introduce.

Note that people seem to be rather in favour of your proposed change. If
you can show that there are no visible drawbacks, one of them will most
likely apply it for you.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24583] set.update(): Crash when source set is changed during merging

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

intermediary.diff LGTM.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue14373] C implementation of functools.lru_cache

[Stefan Behnel]

Stefan Behnel added the comment:

I'm witnessing a crash in the C implementation during garbage collection. 
Interestingly, it only shows in the Py3.6 branch, not in Py3.5 (both latest). 
Here's the gdb session:

Program received signal SIGSEGV, Segmentation fault.
lru_cache_tp_traverse (self=0x72a80ae8, visit=0x43c528 , 
arg=0x0) at ./Modules/_functoolsmodule.c:1040
1040lru_list_elem *next = link->next;
(gdb) list
1035static int
1036lru_cache_tp_traverse(lru_cache_object *self, visitproc visit, void 
*arg)
1037{
1038lru_list_elem *link = self->root.next;
1039while (link != &self->root) {
1040lru_list_elem *next = link->next;
1041Py_VISIT(link);
1042link = next;
1043}
1044Py_VISIT(self->maxsize_O);
(gdb) print link
$1 = (lru_list_elem *) 0x0
(gdb) print self
$2 = (lru_cache_object *) 0x72a80ae8
(gdb) print self->root.next
$3 = (struct lru_list_elem *) 0x0
(gdb) print self->root
$4 = {ob_base = {_ob_next = 0x72a26458, _ob_prev = 0x90e860 , 
ob_refcnt = 1, ob_type = 0x92c500 }, prev = 0x0, next = 0x0, 
key = 0x0, result = 0x0}

IIUC correctly, there is only one entry and the code doesn't expect that. An 
additional "is empty?" NULL check may or may not be the right fix. It might 
also be the linking itself that's incorrect here. The code seems to expect a 
cyclic data structure which is apparently not maintained that way.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24607] standardize sh module

[Vitali Lovich]

New submission from Vitali Lovich:

The subprocess module provides a good foundation of basic functionality.  
However, anything moderately complex becomes cumbersome to write.  
Additionally, it has pitfalls that people frequently overlook.

People then often either resort to hand-rolling their own abstraction on top of 
it, use the library incorrectly, or just use shell scripts if the predominant 
action is to stitch things together.

I have seen great success at avoiding having to write shell-scripts & using the 
sh package. What once would have been written as shell-scripts now can be 
written very naturally using sh in a more maintainable & reusable manner.

I think sh being part of the standard library would be a great addition & make 
python even more compelling as a replacement for shell scripts.  Having sh be 
part of the python library also ensures that the `with` syntax could be done in 
a comprehensive thread-safe manner.

https://pypi.python.org/pypi/sh
http://amoffat.github.com/sh

--
components: Library (Lib)
messages: 246574
nosy: Vitali Lovich
priority: normal
severity: normal
status: open
title: standardize sh module

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24608] Certain inputs to wave.open() result in readframes returning a str instead of bytes

[Christophe Biocca]

New submission from Christophe Biocca:

Basically, some (malformed or empty?) WAV strings result in the empty string 
being returned when calling readframes.

That string cannot be passed back to writeframes() without causing a crash, 
since it does not implement the buffer interface.

--
components: Library (Lib)
files: python_wave_error.py
messages: 246575
nosy: Christophe Biocca
priority: normal
severity: normal
status: open
title: Certain inputs to wave.open() result in readframes returning a str 
instead of bytes
type: behavior
versions: Python 3.4
Added file: http://bugs.python.org/file39891/python_wave_error.py

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue14373] C implementation of functools.lru_cache

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

self->root.next and self->root.prev should never be NULL. Could you please 
provide minimal example of code that produces a crash?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24608] Certain inputs to wave.open() result in readframes returning a str instead of bytes

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


--
assignee:  -> serhiy.storchaka
nosy: +serhiy.storchaka
stage:  -> needs patch
versions: +Python 3.5, Python 3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24607] standardize sh module

[Skip Montanaro]

Skip Montanaro added the comment:

While it's an interesting library, my fear is that people will start shelling 
out to all sorts of things which Python already has builtin. One of the 
examples on the github site was showing how to call "ls". Another example 
invoked "wc". neither of those is particularly difficult to pull off in Python. 
In addition, you're left with text data you need to parse for further use 
(assuming you even can reliably do so). Finally, I'm not sure masking the 
fork/exec overhead is such a great idea.

--
nosy: +skip.montanaro

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24608] Certain inputs to wave.open() result in readframes returning a str instead of bytes

[Roundup Robot]

Roundup Robot added the comment:

New changeset 9e035639516c by Serhiy Storchaka in branch '3.4':
Issue #24608: chunk.Chunk.read() now always returns bytes, not str.
https://hg.python.org/cpython/rev/9e035639516c

New changeset 64b2d154a5db by Serhiy Storchaka in branch '3.5':
Issue #24608: chunk.Chunk.read() now always returns bytes, not str.
https://hg.python.org/cpython/rev/64b2d154a5db

New changeset 8befb15024b5 by Serhiy Storchaka in branch 'default':
Issue #24608: chunk.Chunk.read() now always returns bytes, not str.
https://hg.python.org/cpython/rev/8befb15024b5

--
nosy: +python-dev

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24608] Certain inputs to wave.open() result in readframes returning a str instead of bytes

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

Thank you for your report Christophe.

--
resolution:  -> fixed
stage: needs patch -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24567] random.choice IndexError due to double-rounding

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

There are other affected methods: randrange(), randint(), shuffle(), sample().

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue14373] C implementation of functools.lru_cache

[Stefan Behnel]

Stefan Behnel added the comment:

It's not actually my own code using the lru_cache here. From a quick grep
over the code tree, the only potentially related usage I found was in
Python's fnmatch module, on the "_compile_pattern()" function. Commenting
that out then made the crash go away, so this was the culprit.

However, I ran test_functools.py of the same installation and it passes, so
not every usage is broken here. Simple manual testing didn't reveal
anything either so far.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue14373] C implementation of functools.lru_cache

[Stefan Behnel]

Stefan Behnel added the comment:

test_fnmatch.py also passes, BTW.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue14373] C implementation of functools.lru_cache

[Tim Graham]

Changes by Tim Graham :


--
nosy:  -Tim.Graham

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24602] SRE_SEARCH Integer Underflow

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

This was fixed in issue18684.

--
resolution:  -> out of date
stage: patch review -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24607] standardize sh module

[R. David Murray]

R. David Murray added the comment:

Indeed.  If you want shell scripting, use a shell script.  The advantage of 
python scripting is exactly that you are using non-shell, with explicit control 
of what gets substituted where rather than the shell's implicit rules.

Regardless our our opinions, though, this is the kind of topic that needs to be 
brought up first on the python-ideas mailing list.

--
nosy: +r.david.murray
stage:  -> resolved
status: open -> closed
type:  -> enhancement

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24609] shutil.copytree fails with symlinks to directories when symlink=False

[Thomas Kluyver]

New submission from Thomas Kluyver:

shutil.copytree behaves differently with symlinks depending on the 'symlinks' 
parameter. If this is True, symlinks are replicated in the destination. If 
False, the contents of the targets are copied to the destination.

With symlinks=False, it currently assumes that all symlinks are pointing to 
regular files. With a symlink to a directory, it tries to copy it using the 
file copy function, which fails with:

[Errno 21] Is a directory: '/tmp/tmpouavxt1u/link_to_dir'"

The attached patch adds an isdir() check to use copytree instead in that case. 
A test is also added.

--
components: Library (Lib)
files: shutil_copytree_symlink_dir.patch
keywords: patch
messages: 246585
nosy: takluyver
priority: normal
severity: normal
status: open
title: shutil.copytree fails with symlinks to directories when symlink=False
versions: Python 3.4, Python 3.5, Python 3.6
Added file: http://bugs.python.org/file39892/shutil_copytree_symlink_dir.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21697] shutil.copytree() handles symbolic directory incorrectly

[Berker Peksag]

Changes by Berker Peksag :


--
assignee:  -> berker.peksag
nosy: +takluyver
versions: +Python 3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24609] shutil.copytree fails with symlinks to directories when symlink=False

[Berker Peksag]

Berker Peksag added the comment:

Thanks for the report and the patch. This is a duplicate of issue 21697. Could 
you please attach the patch in that issue?

--
nosy: +berker.peksag
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> shutil.copytree() handles symbolic directory incorrectly

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21697] shutil.copytree() handles symbolic directory incorrectly

[Thomas Kluyver]

Thomas Kluyver added the comment:

Here's my patch (I submitted the duplicate issue). I think it's functionally 
the same as Eduardo's, but it also adds a test.

--
Added file: http://bugs.python.org/file39893/shutil_copytree_symlink_dir.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24606] segfault caused by nested calls to map()

[Mark Lawrence]

Mark Lawrence added the comment:

FTR I can reproduce this on Windows 8.1 with 3.4.3 and 3.3.5 but not 2.7.10 or 
2.6.6.

--
nosy: +BreamoreBoy

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24570] IDLE Autocomplete and Call Tips Do Not Pop Up on OS X with ActiveTcl 8.5.18

[Terry J. Reedy]

Terry J. Reedy added the comment:

More tests might help pin down the bug. Here is the complete config for 
completions.
[AutoComplete]
enable=True
popupwait=2000
[AutoComplete_cfgBindings]
force-open-completions=
[AutoComplete_bindings]
autocomplete=
try-open-completions=  


Notes: config-extensions.def is initially opened and generically processed in 
various methods of configHandler.IdleConf, and on request, the 
config-extentions section of EditorWindow.py. cfgBindings can be (sensibly) 
reconfigured, the others not. Names that follow, before '=', become 
pseudoevents handles by methods in the

Alessandro, you said  works,  does not.  
How about  and . The latter pair work within 
path strings when the preceding chars begin a path that exist on your system.  
For instance, on Win 7, './ lists options in the current directory.

I have no idea why KeyRelease instead of Key is used above and below.  There is 
no key equivalent of releasing a mouse button in a different location than 
where pressed. Kevin, could there be a bug with KeyRelease on Mac?  Alessandro, 
you could test by making a backup of configextensions.def and removing 
'Release' for 'period'.

The calltip files are
CallTips.py
CallTipWindow.py
and in config-extensions.def,

[CallTips]
enable=True
[CallTips_cfgBindings]
force-open-calltip=
[CallTips_bindings]
try-open-calltip=
refresh-calltip= 

Alessandro, you said  does not work.  How abut 
 (after '(') to open?  Does  
close properly?

I do not know what  (zero) is about.  It does not work for me.

For both boxes, clicking on the box should also close. Does it?
What about Edit -> Show Completions and Edit -> Show calltips for opening?

--
nosy: +terry.reedy

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24572] IDLE Text Output With ASCII Control Codes Not Working

[Terry J. Reedy]

Changes by Terry J. Reedy :


--
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> IDLE does not display \b backspace correctly.

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24572] IDLE Text Output With ASCII Control Codes Not Working

[Terry J. Reedy]

Terry J. Reedy added the comment:

Idle expands tabs to spaces, if asked to do so.  It otherwise passes user code 
generated chars to tkinter, which passes them on to tk, which eventually passes 
them on to the OS gui widgets.  I will say more on the existing issue.

--
nosy: +terry.reedy

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24606] segfault caused by nested calls to map()

[Ned Deily]

Ned Deily added the comment:

Process 51270 launched: './python' (x86_64)
Process 51270 stopped
* thread #1: tid = 0x5c8677, 0x0001000c1af8 
python`_PyObject_Alloc(use_calloc=0, ctx=, nelem=, 
elsize=) + 24 at obmalloc.c:1170, queue = 'com.apple.main-thread', 
stop reason = EXC_BAD_ACCESS (code=2, address=0x7fff5eb8)
frame #0: 0x0001000c1af8 python`_PyObject_Alloc(use_calloc=0, 
ctx=, nelem=, elsize=) + 24 at 
obmalloc.c:1170
   1167
   1168 static void *
   1169 _PyObject_Alloc(int use_calloc, void *ctx, size_t nelem, size_t elsize)
-> 1170 {
   1171 size_t nbytes;
   1172 block *bp;
   1173 poolp pool;
(lldb) bt
* thread #1: tid = 0x5c8677, 0x0001000c1af8 
python`_PyObject_Alloc(use_calloc=0, ctx=, nelem=, 
elsize=) + 24 at obmalloc.c:1170, queue = 'com.apple.main-thread', 
stop reason = EXC_BAD_ACCESS (code=2, address=0x7fff5eb8)
  * frame #0: 0x0001000c1af8 python`_PyObject_Alloc(use_calloc=0, 
ctx=, nelem=, elsize=) + 24 at 
obmalloc.c:1170
frame #1: 0x0001000c0ec8 
python`_PyObject_Malloc(ctx=0x, nbytes=112) + 40 at 
obmalloc.c:1386
frame #2: 0x0001000c03e9 python`_PyMem_DebugAlloc(use_calloc=0, 
ctx=0x000100390898, nbytes=80) + 153 at obmalloc.c:1838
frame #3: 0x0001000be981 
python`_PyMem_DebugMalloc(ctx=0x000100390898, nbytes=80) + 33 at 
obmalloc.c:1861
frame #4: 0x0001000bf3c1 python`PyObject_Malloc(size=80) + 65 at 
obmalloc.c:386
frame #5: 0x00010028c87e python`_PyObject_GC_Alloc(use_calloc=0, 
basicsize=56) + 110 at gcmodule.c:1696
frame #6: 0x00010028c809 python`_PyObject_GC_Malloc(basicsize=56) + 25 
at gcmodule.c:1718
frame #7: 0x00010028ca6d 
python`_PyObject_GC_NewVar(tp=0x000100393990, nitems=2) + 109 at 
gcmodule.c:1747
frame #8: 0x0001000d6c82 python`PyTuple_New(size=2) + 338 at 
tupleobject.c:104
frame #9: 0x0001001d7e26 python`map_next(lz=0x00010cebbae8) + 38 at 
bltinmodule.c:1162
frame #10: 0x00010001072c python`PyIter_Next(iter=0x00010cebbae8) + 
44 at abstract.c:2760
frame #11: 0x0001001d7e71 python`map_next(lz=0x00010ce8) + 113 
at bltinmodule.c:1167
frame #12: 0x00010001072c python`PyIter_Next(iter=0x00010ce8) + 
44 at abstract.c:2760
frame #13: 0x0001001d7e71 python`map_next(lz=0x00010cebbc88) + 113 
at bltinmodule.c:1167
frame #14: 0x00010001072c python`PyIter_Next(iter=0x00010cebbc88) + 
44 at abstract.c:2760
frame #15: 0x0001001d7e71 python`map_next(lz=0x00010cebbd58) + 113 
at bltinmodule.c:1167
frame #16: 0x00010001072c python`PyIter_Next(iter=0x00010cebbd58) + 
44 at abstract.c:2760
frame #17: 0x0001001d7e71 python`map_next(lz=0x00010cebbe28) + 113 
at bltinmodule.c:1167
frame #18: 0x00010001072c python`PyIter_Next(iter=0x00010cebbe28) + 
44 at abstract.c:2760
frame #19: 0x0001001d7e71 python`map_next(lz=0x00010cebbef8) + 113 
at bltinmodule.c:1167
frame #20: 0x00010001072c python`PyIter_Next(iter=0x00010cebbef8) + 
44 at abstract.c:2760
frame #21: 0x0001001d7e71 python`map_next(lz=0x00010cebd058) + 113 
at bltinmodule.c:1167
frame #22: 0x00010001072c python`PyIter_Next(iter=0x00010cebd058) + 
44 at abstract.c:2760
frame #23: 0x0001001d7e71 python`map_next(lz=0x00010cebd128) + 113 
at bltinmodule.c:1167
frame #24: 0x00010001072c python`PyIter_Next(iter=0x00010cebd128) + 
44 at abstract.c:2760
[...]

--
nosy: +ned.deily

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24606] segfault caused by nested calls to map()

[Ned Deily]

Changes by Ned Deily :


--
nosy:  -ned.deily

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue14373] C implementation of functools.lru_cache

[Ned Deily]

Ned Deily added the comment:

I've also seen a crash in lru_cache_tp_traverse but with the 3.5.0b3 release 
build for the OS X 64-bit/32-bit installer.  I just stumbled across the 
segfault by bringing up the interactive interpreter and typing "import ssl".  
After a lot of playing around, I reduced the failing case to: 1. have an 
"import pprint" in a startup file referred to by PYTHONSTARTUP *and* 2. "import 
ssl" must be the very first command entered in the interactive interpreter. 
Odd!  Unfortunately, the release build is a non-debug build and, so far, I have 
not been able to reproduce the segfault with any other build, debug or 
non-debug.  So, whatever the problem is, it's very build dependent.  Here is 
the OS X system traceback from the segfault:  

Path:  
/Library/Frameworks/Python.framework/Versions/3.5.0b3_10_6/Resources/Python.app/Contents/MacOS/Python
Identifier:Python
Version:   ???
Code Type: X86-64 (Native)
Parent Process:bash [51285]
Responsible:   iTerm [754]
User ID:   503

Date/Time: 2015-07-10 19:57:16.086 -0700
OS Version:Mac OS X 10.10.4 (14E46)
Report Version:11
Anonymous UUID:CFED52E3-698C-835B-D61C-F4B1F18D2CB6


Time Awake Since Boot: 80 seconds

Crashed Thread:0  Dispatch queue: com.apple.main-thread

Exception Type:EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:   KERN_INVALID_ADDRESS at 0x0018

VM Regions Near 0x18:
--> 
__TEXT 0001-00011000 [4K] r-x/rwx 
SM=COW  
/Library/Frameworks/Python.framework/Versions/3.5.0b3_10_6/Resources/Python.app/Contents/MacOS/Python

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   org.python.python   0x00010015e5e5 
lru_cache_tp_traverse + 37
1   org.python.python   0x00010013a2d7 collect + 439
2   org.python.python   0x00010013aee5 _PyObject_GC_Alloc + 
357
3   org.python.python   0x00010013afe7 _PyObject_GC_New + 23
4   org.python.python   0x000100059bce PyDict_New + 334
5   org.python.python   0x00010015f029 lru_cache_new + 249
6   org.python.python   0x0001000795a6 type_call + 38
7   org.python.python   0x0001dc93 PyObject_Call + 99
8   org.python.python   0x0001000e9fd8 PyEval_EvalFrameEx + 
7656
9   org.python.python   0x0001000f1d00 
_PyEval_EvalCodeWithName + 2400
10  org.python.python   0x0001000f035d PyEval_EvalFrameEx + 
33133
11  org.python.python   0x0001000f1d00 
_PyEval_EvalCodeWithName + 2400
12  org.python.python   0x0001000f1e07 PyEval_EvalCodeEx + 
71
13  org.python.python   0x0001000e5ff5 
builtin___build_class__ + 485
14  org.python.python   0x000100065549 PyCFunction_Call + 
281
15  org.python.python   0x0001000f0768 PyEval_EvalFrameEx + 
34168
16  org.python.python   0x0001000f1d00 
_PyEval_EvalCodeWithName + 2400
17  org.python.python   0x0001000f1e61 PyEval_EvalCode + 81
18  org.python.python   0x0001000e5683 builtin_exec + 627
19  org.python.python   0x000100065519 PyCFunction_Call + 
233
20  org.python.python   0x0001000f0a9b PyEval_EvalFrameEx + 
34987
21  org.python.python   0x0001000f1d00 
_PyEval_EvalCodeWithName + 2400
22  org.python.python   0x0001000f035d PyEval_EvalFrameEx + 
33133
23  org.python.python   0x0001000f07fd PyEval_EvalFrameEx + 
34317
24  org.python.python   0x0001000f07fd PyEval_EvalFrameEx + 
34317
25  org.python.python   0x0001000f07fd PyEval_EvalFrameEx + 
34317
26  org.python.python   0x0001000f1d00 
_PyEval_EvalCodeWithName + 2400
27  org.python.python   0x0001000f1e07 PyEval_EvalCodeEx + 
71
28  org.python.python   0x00010004017a function_call + 186
29  org.python.python   0x0001dc93 PyObject_Call + 99
30  org.python.python   0x000100010ff6 
_PyObject_CallMethodIdObjArgs + 454
31  org.python.python   0x00010010d6d3 
PyImport_ImportModuleLevelObject + 1171
32  org.python.python   0x0001000e5e03 builtin___import__ + 
131
33  org.python.python   0x000100065549 PyCFunction_Call + 
281
34  org.python.python   0x0001dc93 PyObject_Call + 99
35  org.python.python   0x0001000e64f7 
PyEval_CallObjectWithKeywords + 87
36  org.python.python   0x0001000ea43e PyEval_EvalFrameEx + 
8782
37  org.python.python   0x0001000f1d00 
_PyEval_EvalCod

[issue24606] segfault caused by nested calls to map()

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

This looks as a duplicate of issue14010.

--
nosy: +serhiy.storchaka
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> deeply nested filter segfaults

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue14010] deeply nested filter segfaults

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

See issue24606 for another instance of this in map().

--
versions: +Python 3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24572] IDLE Text Output With ASCII Control Codes Not Working

[Terry J. Reedy]

Terry J. Reedy added the comment:

To modify what I said, Idle only auto-expands literal tabs entered into an 
editor window with the Tab key.  When one is doing such entry, all key 
sequences are subject to interception, so this is nothing special.

Tabs chars put in a string with '\t' or '\x09' are not and should not be 
modified (except by explicit string methods.  The issue here and in #23220 is 
what happens when strings are written to a file object with print or file.write.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com