[issue36986] tarfile: unexpected IsADirectoryError on extraction

[alter-bug-tracer]

New submission from alter-bug-tracer :

The following code creates a new directory 'output' and extracts the tar 
archive given as argv in it. When a malformed archive (attached) is given as 
argv, a IsADirectoryError is thrown, as opposed to extracting the file 
contained in the archive to the 'output' directory.

Code:
import tarfile
import sys
import os

def extract(archive_path, destination_path):
  if not tarfile.is_tarfile(archive_path):
print ('Not a tar file')
return
  tar = tarfile.open(archive_path, 'r')
  for info in tar.getmembers():
tar.extractall(destination_path, members=[tar.getmember(info.name)])

destination_path = 'output'
os.mkdir(destination_path)
extract(sys.argv[1], destination_path)

Result:
Traceback (most recent call last):
  File "code.py", line 15, in 
extract(sys.argv[1], destination_path)
  File "code.py", line 11, in extract
tar.extractall(destination_path, members=[tar.getmember(info.name)])
  File "/usr/lib/python3.6/tarfile.py", line 2010, in extractall
numeric_owner=numeric_owner)
  File "/usr/lib/python3.6/tarfile.py", line 2052, in extract
numeric_owner=numeric_owner)
  File "/usr/lib/python3.6/tarfile.py", line 2122, in _extract_member
self.makefile(tarinfo, targetpath)
  File "/usr/lib/python3.6/tarfile.py", line 2163, in makefile
with bltn_open(targetpath, "wb") as target:
IsADirectoryError: [Errno 21] Is a directory: 'output'

--
files: input0.tar
messages: 342983
nosy: alter-bug-tracer
priority: normal
severity: normal
status: open
title: tarfile: unexpected IsADirectoryError on extraction
type: behavior
versions: Python 3.6, Python 3.7, Python 3.8
Added file: https://bugs.python.org/file48341/input0.tar

___
Python tracker 

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

[issue36987] Dictionary: why is the value not used up?

[Aprila Hijriyan]

New submission from Aprila Hijriyan :

Python 2.7.15rc1 (default, Nov 12 2018, 14:31:15) [GCC 7.3.0] on linux2 Type 
"help", "copyright", "credits" or "license" for more information.

>>> d = {"a": 1, "b": 2}
>>> d ["c"] = d
>>> d ["c"] {'a': 1, 'c': {...}, 'b': 2}
>>> d ["c"] ["c"] {'a': 1, 'c': {...}, 'b': 2}

why does the key value 'c' have a 'c' key in it?

--
messages: 342984
nosy: Aprila Hijriyan
priority: normal
severity: normal
status: open
title: Dictionary: why is the value not used up?
versions: Python 2.7, Python 3.6

___
Python tracker 

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

[issue36987] Dictionary: why is the value not used up?

[Stéphane Wirtel]

Stéphane Wirtel  added the comment:

Hi Aprila,

I think you should use the mailing list for the Python users.

Have a nice day,

--
nosy: +matrixise
resolution:  -> not a bug
stage:  -> 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

[issue36987] Dictionary: why is the value not used up?

[Stéphane Wirtel]

Stéphane Wirtel  added the comment:

Here is the mailing list for the python users.


https://mail.python.org/mailman/listinfo/python-list

--

___
Python tracker 

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

[issue36970] Rename _PyObject_FastCall functions

[Jeroen Demeyer]

Jeroen Demeyer  added the comment:

The consensus on PEP 590 now seems to be to keep the name 
`_PyObject_FastCallDict` and rename only `_PyObject_FastCallKeywords` -> 
`_PyObject_Vectorcall`.

For the record: I don't agree with this decision but I'll implement it.

--

___
Python tracker 

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

[issue36816] self-signed.pythontest.net TLS certificate key is too weak

[Michael Felt]

Michael Felt  added the comment:

I am not an OpenSSL expert - and I am conscious of OpenSSL changes with regard 
to 'acceptance' of anything self-signed.

And, what it looks like you are trying to do with an updated 'signing" .pem is 
to remove the 'self-signed' charasteric.

On AIX - atm - I get, as did Chih-Hsuan Yen (yan12125),

==
ERROR: test_networked_good_cert (test.test_httplib.HTTPSTest)
--
Traceback (most recent call last):
  File "/home/buildbot/python-master/Lib/test/test_httplib.py", line 1632, in 
test_networked_good_cert
h.request('GET', '/')
  File "/home/buildbot/python-master/Lib/http/client.py", line 1221, in request
self._send_request(method, url, body, headers, encode_chunked)
  File "/home/buildbot/python-master/Lib/http/client.py", line 1267, in 
_send_request
self.endheaders(body, encode_chunked=encode_chunked)
  File "/home/buildbot/python-master/Lib/http/client.py", line 1216, in 
endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
  File "/home/buildbot/python-master/Lib/http/client.py", line 1004, in 
_send_output
self.send(msg)
  File "/home/buildbot/python-master/Lib/http/client.py", line 944, in send
self.connect()
  File "/home/buildbot/python-master/Lib/http/client.py", line 1383, in connect
self.sock = self._context.wrap_socket(self.sock,
  File "/home/buildbot/python-master/Lib/ssl.py", line 405, in wrap_socket
return self.sslsocket_class._create(
  File "/home/buildbot/python-master/Lib/ssl.py", line 853, in _create
self.do_handshake()
  File "/home/buildbot/python-master/Lib/ssl.py", line 1117, in do_handshake
self._sslobj.do_handshake()
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate 
verify failed: self signed certificate (_ssl.c:1055)

And I see why now:
test_networked_good_cert (test.test_httplib.HTTPSTest) ... skipped "Use of the 
'network' resource not enabled"

Digging a bit:

buildbot@x064:[/home/buildbot/python-master]openssl s_client -connect 
self-signed.pythontest.net:443
CONNECTED(0003)
depth=0 C = XY, ST = Castle Anthrax, L = Argument Clinic, O = Python Software 
Foundation, CN = self-signed.pythontest.net
verify error:num=18:self signed certificate
verify return:1
depth=0 C = XY, ST = Castle Anthrax, L = Argument Clinic, O = Python Software 
Foundation, CN = self-signed.pythontest.net
verify return:1
---
Certificate chain
 0 s:/C=XY/ST=Castle Anthrax/L=Argument Clinic/O=Python Software 
Foundation/CN=self-signed.pythontest.net

   i:/C=XY/ST=Castle Anthrax/L=Argument Clinic/O=Python Software 
Foundation/CN=self-signed.pythontest.net

And while this:
How to know if it has been fixed?  Monitor the test_networked_good_cert test on 
any "Debian buster" builtbot(s) such as 
https://buildbot.python.org/all/#/workers/23 to make sure it is not skipped.  
(the test _currently_ fails, I am going to have it be _skipped_ on this 
specific key too small error for the time being to get that stable buildbot 
green again)

is nice for some, it is not nice for all!

Perhaps the test should be switched to 'warn' on failure, rather than error on 
failure, until fixed!

--
nosy: +Michael.Felt

___
Python tracker 

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

[issue36937] New _PyObject_MakeTpCall() function

[Petr Viktorin]

Petr Viktorin  added the comment:

Avoiding the duplication makes sense, but without the rest of PEP 590 it could 
just be a static function in call.c.

--

___
Python tracker 

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

[issue36969] pdb: do_args: display/handle keyword-only arguments

[Pablo Galindo Salgado]

Pablo Galindo Salgado  added the comment:

> Of course, should I open a new PR or post a patch to be added to a current PR?

Make another PR against master.

--

___
Python tracker 

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

[issue36937] New _PyObject_MakeTpCall() function

[Jeroen Demeyer]

Jeroen Demeyer  added the comment:

So what are you trying to say? That it *should* be a static function? It most 
likely won't be a static function after PEP 590 is fully implemented.

--

___
Python tracker 

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

[issue36937] New _PyObject_MakeTpCall() function

[Petr Viktorin]

Petr Viktorin  added the comment:

Ah, sorry, I didn't get the message through.

I'll merge it with the rest of PEP 590. Adding the symbol doesn't make sense 
*right* now.

--

___
Python tracker 

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

[issue22865] Document how to make pty.spawn not copy data

[STINNER Victor]

STINNER Victor  added the comment:


New changeset cdb2dbfe92b95dcd19ccab1a1e9b8c39263c54b0 by Victor Stinner (Geoff 
Shannon) in branch '3.7':
[3.7] bpo-22865: Expand on documentation for the pty.spawn function (GH-11980) 
(GH-13455)
https://github.com/python/cpython/commit/cdb2dbfe92b95dcd19ccab1a1e9b8c39263c54b0


--

___
Python tracker 

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

[issue22865] Document how to make pty.spawn not copy data

[STINNER Victor]

STINNER Victor  added the comment:

Thanks Geoff Shannon for the doc enhancement!

--
resolution:  -> fixed
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

[issue36937] New _PyObject_MakeTpCall() function

[Jeroen Demeyer]

Jeroen Demeyer  added the comment:

In that case, there is no point a making a separate issue or PR.

--
resolution:  -> duplicate
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

[issue33485] autoconf target does not behave correctly

[STINNER Victor]

STINNER Victor  added the comment:

> it uses autoheader and autoconf instead of autoreconf

How is this an issue?

Is autoreconf also available when autoheader and autoconf are available?

--
nosy: +vstinner

___
Python tracker 

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

[issue36974] Implement PEP 590

[Jeroen Demeyer]

Change by Jeroen Demeyer :


--
pull_requests: +13367

___
Python tracker 

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

[issue36816] self-signed.pythontest.net TLS certificate key is too weak

[Michael Felt]

Michael Felt  added the comment:

p.s. On Centos I could not even get a python3 (at least not easily).

On debian (on POWER) I get the same error (message) as on AIX - although the 
line number did change.

ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate 
verify failed: self signed certificate (_ssl.c:1056)

so, not a message about "key too small error" - pure, this is self-signed, so 
error.

--

___
Python tracker 

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

[issue36965] use of STATUS_CONTROL_C_EXIT in Modules/main.c breaks compilation with non MSC compilers

[STINNER Victor]

STINNER Victor  added the comment:


New changeset 925af1d99b69bf3e229411022ad840c5a0cfdcf8 by Victor Stinner (Erik 
Janssens) in branch 'master':
bpo-36965: Fix includes in main.c on Windows with non-MSC compilers (GH-13421)
https://github.com/python/cpython/commit/925af1d99b69bf3e229411022ad840c5a0cfdcf8


--

___
Python tracker 

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

[issue36975] csv: undocumented UnicodeDecodeError on malformed file

[Rémi Lapeyre]

Change by Rémi Lapeyre :


Added file: https://bugs.python.org/file48343/file0.txt

___
Python tracker 

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

[issue36975] csv: undocumented UnicodeDecodeError on malformed file

[Rémi Lapeyre]

Change by Rémi Lapeyre :


Added file: https://bugs.python.org/file48342/csv_parser.py

___
Python tracker 

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

[issue36975] csv: undocumented UnicodeDecodeError on malformed file

[Rémi Lapeyre]

Change by Rémi Lapeyre :


Added file: https://bugs.python.org/file48344/file1.txt

___
Python tracker 

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

[issue36975] csv: undocumented UnicodeDecodeError on malformed file

[Rémi Lapeyre]

Rémi Lapeyre  added the comment:

I don't understand the issue here, csv can raise many errors when an issue 
happens:

>>> import csv
>>> csv.reader(None)
Traceback (most recent call last):
  File "", line 1, in 
TypeError: argument 1 must be an iterator

Why would UnicodeDecodeError not be appropriate here?

--
nosy: +remi.lapeyre

___
Python tracker 

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

[issue36084] Threading: add builtin TID attribute to Thread objects

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests: +13368
stage: resolved -> patch review

___
Python tracker 

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

[issue36084] Threading: add builtin TID attribute to Thread objects

[STINNER Victor]

STINNER Victor  added the comment:

I wrote PR 13458 to revert the change which broke the CI for longer than one 
week, see the rationale there:
https://github.com/python/cpython/pull/13458#issuecomment-494334241

Email thread about the regression:
https://mail.python.org/pipermail/python-buildbots/2019-May/000280.html

--

___
Python tracker 

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

[issue36969] pdb: do_args: display/handle keyword-only arguments

[Rémi Lapeyre]

Change by Rémi Lapeyre :


--
pull_requests: +13369

___
Python tracker 

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

[issue36969] pdb.do_args: display keyword-only and positional only arguments

[Rémi Lapeyre]

Change by Rémi Lapeyre :


--
title: pdb: do_args: display/handle keyword-only arguments -> pdb.do_args: 
display keyword-only and positional only arguments

___
Python tracker 

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

[issue36084] Threading: add builtin TID attribute to Thread objects

[STINNER Victor]

STINNER Victor  added the comment:

Jake Tesler: In the meanwhile, can you please try to rewrite your change to 
make the attribute optional?

C PyThread_get_thread_native_id() function and Python _thread.get_native_id() 
should not be defined if it's not supported by 
the platform.

I suggest to add the following #define in Include/pythread.h:

#if (... list of supported platforms ...
#  define PY_HAVE_THREAD_NATIVE_ID 1
#endif

It would be great if you can come up with a solution before the end of the 
month, otherwise we will miss Python 3.8 deadline for new feature :-(

Tell me if you need help to rework your PR. IMHO it's a nice feature. There is 
just an issue in your first implementation.

--

___
Python tracker 

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

[issue36974] Implement PEP 590

[Jeroen Demeyer]

Change by Jeroen Demeyer :


--
pull_requests: +13370

___
Python tracker 

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

[issue36084] Threading: add builtin TID attribute to Thread objects

[STINNER Victor]

STINNER Victor  added the comment:


New changeset d12e75734d46ecde588c5de65e6d64146911d20c by Victor Stinner in 
branch 'master':
Revert "bpo-36084: Add native thread ID to threading.Thread objects (GH-11993)" 
(GH-13458)
https://github.com/python/cpython/commit/d12e75734d46ecde588c5de65e6d64146911d20c


--

___
Python tracker 

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

[issue36084] Threading: add builtin TID attribute to Thread objects

[Antoine Pitrou]

Antoine Pitrou  added the comment:

Jake, would you like to submit a new PR that implements Victor's suggestion 
(i.e. only define and test the attribute on supported systems)?

--

___
Python tracker 

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

[issue31904] Python should support VxWorks RTOS

[STINNER Victor]

STINNER Victor  added the comment:


New changeset f2d7ac7e5bd821e29e0fcb78a760a282059ae000 by Victor Stinner 
(pxinwr) in branch 'master':
bpo-31904: Add posix module support for VxWorks (GH-12118)
https://github.com/python/cpython/commit/f2d7ac7e5bd821e29e0fcb78a760a282059ae000


--

___
Python tracker 

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

[issue36986] tarfile: unexpected IsADirectoryError on extraction

[Michele Angrisano]

Michele Angrisano  added the comment:

It looks like it has the same behavior of issue8958.

--
nosy: +mangrisano

___
Python tracker 

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

[issue36988] zipfile: string IndexError on extract

[alter-bug-tracer]

New submission from alter-bug-tracer :

The following code throws an IndexError when attempting to extract a malformed 
archive (attached):

import zipfile
import sys

zf = zipfile.ZipFile(sys.argv[1])
for info in zf.infolist():
  zf.extract(info.filename)

Result:
Traceback (most recent call last):
  File "code.py", line 6, in 
zf.extract(info.filename)
  File "/usr/lib/python3.6/zipfile.py", line 1507, in extract
return self._extract_member(member, path, pwd)
  File "/usr/lib/python3.6/zipfile.py", line 1572, in _extract_member
if member.is_dir():
  File "/usr/lib/python3.6/zipfile.py", line 531, in is_dir
return self.filename[-1] == '/'
IndexError: string index out of range

--
files: file0.zip
messages: 343006
nosy: alter-bug-tracer
priority: normal
severity: normal
status: open
title: zipfile: string IndexError on extract
type: behavior
versions: Python 3.6, Python 3.7, Python 3.8
Added file: https://bugs.python.org/file48345/file0.zip

___
Python tracker 

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

[issue36648] MAP_SHARED isn't proper for anonymous mappings for VxWorks

[STINNER Victor]

STINNER Victor  added the comment:


New changeset 4fb15021890d327023aefd95f5a84ac33b037d19 by Victor Stinner (Lihua 
Zhao) in branch 'master':
bpo-36648: fix mmap issue for VxWorks (GH-12394)
https://github.com/python/cpython/commit/4fb15021890d327023aefd95f5a84ac33b037d19


--

___
Python tracker 

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

[issue31904] Python should support VxWorks RTOS

[STINNER Victor]

STINNER Victor  added the comment:

Please update PR 12670: see my comment there.

--

___
Python tracker 

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

[issue36965] use of STATUS_CONTROL_C_EXIT in Modules/main.c breaks compilation with non MSC compilers

[STINNER Victor]

STINNER Victor  added the comment:

eryksun commented there, but I prefer to discuss here:
https://github.com/python/cpython/commit/925af1d99b69bf3e229411022ad840c5a0cfdcf8#commitcomment-33617265

""Windows.h" was already being included, as I mentioned on the issue tracker, 
because we certainly were not getting STATUS_CONTROL_C_EXIT from "crtdbg.h", a 
header that was left in this file accidentally about 12 years ago. If it's 
included explicitly here, also define WIN32_LEAN_AND_MEAN to cut the number of 
included headers by about a half."

I prefer to explicitly include windows.h, it doesn't hurt :-)

WIN32_LEAN_AND_MEAN is defined by Include/internal/pycore_condvar.h which is 
indirectly included by pycore_pystate.h:

#include "pycore_gil.h"   /* _gil_runtime_state  */

pycore_gil.h:

#include "pycore_condvar.h"


By the way, WIN32_LEAN_AND_MEAN caused me issues while working on bpo-36728:
https://twitter.com/VictorStinner/status/1127884878027079680

I managed to workaround the issue: commit 
d5d9e81ce9a7efc5bc14a5c21398d1ef6f626884

Extract of (fixed) posixmodule.c:
---
...
#include "Python.h"
#ifdef MS_WINDOWS
   /* include  early to avoid conflict with pycore_condvar.h:

#define WIN32_LEAN_AND_MEAN
#include 

  FSCTL_GET_REPARSE_POINT is not exported with WIN32_LEAN_AND_MEAN. */
#  include 
#endif

#include "pycore_ceval.h" /* _PyEval_ReInitThreads() */
#include "pycore_pystate.h"   /* _PyRuntime */
...
---

--

___
Python tracker 

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

[issue36981] asyncio transport.write() memory out

[viocal]

viocal  added the comment:

I use rotocol.pause_writing() / Protocol.resume_writing()
but results is no change(memory out Or killed by OS)

--

___
Python tracker 

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

[issue36752] test multiprocessing: test_rapid_restart() crash on AIX

[Michael Felt]

Michael Felt  added the comment:

I believe (or hope) this is related to issue35828.

This is, as far as I can tell, a compiler issue.

It appears "always" in the bot situation (not building as root) when using 
xlc-v11, but not when using gcc-4.7.4.

So, when the test failure "disappears" on the bot - it is because I have 
switched CC=clr_r to CC=gcc

I am quite willing to continue searching (I just removed over three GBytes of 
core dumps I had collected previously).

As to analysis: it appears the "server" side core-dumps, and the the 
client-side is refused a connection (obviously).

--
nosy: +Michael.Felt

___
Python tracker 

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

[issue36273] test_thread leaks a core dump on PPC64 AIX 3.x

[Michael Felt]

Michael Felt  added the comment:

Again - how can I get the core (dump) mentioned in the error message. When I 
force this situation I have several core dumps - not "the one".

--

___
Python tracker 

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

[issue36981] asyncio transport.write() memory out

[Andrew Svetlov]

Andrew Svetlov  added the comment:

I'm sorry but I cannot tell why you are using `pause_writing` incorrectly 
without looking on the code.

--

___
Python tracker 

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

[issue36965] use of STATUS_CONTROL_C_EXIT in Modules/main.c breaks compilation with non MSC compilers

[STINNER Victor]

STINNER Victor  added the comment:

> WIN32_LEAN_AND_MEAN is defined by Include/internal/pycore_condvar.h (...)

It would be nice to get ride of #include  in Python headers. The 
 was introduced by this commit:

commit 2ebc5ce42a8a9e047e790aefbf9a94811569b2b6
Author: Eric Snow 
Date:   Thu Sep 7 23:51:28 2017 -0600

bpo-30860: Consolidate stateful runtime globals. (#3397)

* group the (stateful) runtime globals into various topical structs
* consolidate the topical structs under a single top-level _PyRuntimeState 
struct
* add a check-c-globals.py script that helps identify runtime globals

Other globals are excluded (see globals.txt and check-c-globals.py).

The current problem is that we need the HANDLE type which comes from 
 to get the full structure:

typedef struct _PyCOND_T
{
HANDLE sem;
int waiting; /* to allow PyCOND_SIGNAL to be a no-op */
} PyCOND_T;

I tried to avoid "HANDLE" using:

typedef struct _PyCOND_T
{
void* sem;
int waiting; /* to allow PyCOND_SIGNAL to be a no-op */
} PyCOND_T;

... but then pycore_condvar.h compilation fails on "typedef CRITICAL_SECTION 
PyMUTEX_T;": CRITICAL_SECTION type is not defined :-(

By the way, Python still uses _PY_EMULATED_WIN_CV by default, whereas we want 
to drop Vista support: bpo-32592.

--

___
Python tracker 

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

[issue36981] asyncio transport.write() memory out

[viocal]

viocal  added the comment:

for buf in filedata:
asc.resume_writing()
asc.transport.write(buf)
asc.pause_writing()

--

___
Python tracker 

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

[issue36989] test_thread fails because symbol is (no longer) exported

[Michael Felt]

New submission from Michael Felt :

On AIX, with commit 4fb15021890d327023aefd95f5a84ac33b037d19 (HEAD -> master, 
origin/master, origin/HEAD)

test_thread is failing.

The three sub_tests that exit as ERROR are:
ERROR: test_threads_join_2 (test.test_threading.SubinterpThreadingTests)
ERROR: test_frame_tstate_tracing (test.test_threading.ThreadTests)

These two have in common:
Traceback (most recent call last):
...
ImportError:0509-130 Symbol resolution failed for 
/home/buildbot/python-master/build/lib.aix-7.1-3.8-pydebug/_testcapi.so because:
0509-136   Symbol _PyMem_GetAllocatorsName (number 191) is not exported 
from
   dependent module python.
0509-192 Examine .loader section symbols with the
 'dump -Tv' command.

FAIL: test_daemon_threads_fatal_error 
(test.test_threading.SubinterpThreadingTests)

I am guessing that:

==
FAIL: test_daemon_threads_fatal_error 
(test.test_threading.SubinterpThreadingTests)
--
Traceback (most recent call last):
  File "/home/buildbot/python-master/Lib/test/test_threading.py", line 942, in 
test_daemon_threads_fatal_error
self.assertIn("Fatal Python error: Py_EndInterpreter: "
AssertionError: 'Fatal Python error: Py_EndInterpreter: not the last thread' 
not found in 'Traceback (most recent call last):\n  File "", line 2, in 
\nImportError: \t0509-130 Symbol resolution failed for 
/home/buildbot/python-master/build/lib.aix-7.1-3.8-pydebug/_testcapi.so 
because:\n\t0509-136   Symbol _PyMem_GetAllocatorsName (number 191) is not 
exported from\n\t\t   dependent module python.\n\t0509-192 Examine .loader 
section symbols with the\n\t\t \'dump -Tv\' command.'

--
is caused by the earlier failures.

--
components: Build, Tests
messages: 343016
nosy: Michael.Felt
priority: normal
severity: normal
status: open
title: test_thread fails because symbol is (no longer) exported
versions: Python 3.8

___
Python tracker 

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

[issue36981] asyncio transport.write() memory out

[Andrew Svetlov]

Andrew Svetlov  added the comment:

No. It doesn't work this way.
pause_writing is a protocol callback called from transport when the internal 
buffer is full.
In reaction to this callback the producer should stop calling transport.write() 
and resume writing after getting `resume_writing()`.

Flow control is hard. As I wrote you can take a look at asyncio streams for 
example how to do it.

--

___
Python tracker 

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

[issue36965] use of STATUS_CONTROL_C_EXIT in Modules/main.c breaks compilation with non MSC compilers

[Eryk Sun]

Eryk Sun  added the comment:

>  FSCTL_GET_REPARSE_POINT is not exported with WIN32_LEAN_AND_MEAN

You can explicitly include "winioctl.h" after "windows.h". Getting it from 
"windows.h" is indirect via "winscard.h" (smart card services), which will be 
skipped if either WIN32_LEAN_AND_MEAN or NOCRYPT is defined.

--

___
Python tracker 

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

[issue36990] test_asyncio.test_create_connection_ipv6_scope fails(in mock test?)

[Michael Felt]

New submission from Michael Felt :

==
test_create_connection_ipv6_scope 
(test.test_asyncio.test_base_events.BaseEventLoopWithSelectorTests)
--
Traceback (most recent call last):
  File "/home/buildbot/python-master/Lib/unittest/mock.py", line 1226, in 
patched
return func(*args, **keywargs)
  File 
"/home/buildbot/python-master/Lib/test/test_asyncio/test_base_events.py", line 
1316, in test_create_connection_ipv6_scope
sock.connect.assert_called_with(('fe80::1', 80, 0, 1))
  File "/home/buildbot/python-master/Lib/unittest/mock.py", line 838, in 
assert_called_with
raise AssertionError(_error_message()) from cause
AssertionError: expected call not found.
Expected: connect(('fe80::1', 80, 0, 1))
Actual: connect(('fe80::1', 80, 0, 0))


More details:
buildbot@x064:[/home/buildbot/python-master]nohup ./python -m test -v 
test_asyncio | egrep -v "ok$" | grep -v " ... skipped "
== CPython 3.8.0a4+ (heads/master:4fb1502189, May 21 2019, 11:08:13) [GCC 4.7.4]
== AIX-1-00C291F54C00-powerpc-32bit big-endian
== cwd: /home/buildbot/python-master/build/test_python_17694732
== CPU count: 4
== encodings: locale=ISO8859-1, FS=iso8859-1
Run tests sequentially
0:00:00 [1/1] test_asyncio
test_create_connection_ipv6_scope 
(test.test_asyncio.test_base_events.BaseEventLoopWithSelectorTests) ... FAIL
test_communicate_ignore_broken_pipe 
(test.test_asyncio.test_subprocess.SubprocessFastWatcherTests) ... 
/home/buildbot/python-master/Lib/inspect.py:2819: RuntimeWarning: coroutine 
'AsyncMockMixin._mock_call' was never awaited
  params = OrderedDict(((param.name, param)
RuntimeWarning: Enable tracemalloc to get the object allocation traceback
Future exception was never retrieved
future: 
Traceback (most recent call last):
  File "/home/buildbot/python-master/Lib/asyncio/subprocess.py", line 162, in 
_feed_stdin
await self.stdin.drain()
  File "/home/buildbot/python-master/Lib/asyncio/streams.py", line 443, in drain
await self._protocol._drain_helper()
  File "/home/buildbot/python-master/Lib/asyncio/streams.py", line 200, in 
_drain_helper
await waiter
  File "/home/buildbot/python-master/Lib/asyncio/unix_events.py", line 661, in 
_write_ready
n = os.write(self._fileno, self._buffer)
BrokenPipeError: [Errno 32] Broken pipe
test_communicate_ignore_broken_pipe 
(test.test_asyncio.test_subprocess.SubprocessSafeWatcherTests) ... Future 
exception was never retrieved
future: 
Traceback (most recent call last):
  File "/home/buildbot/python-master/Lib/asyncio/subprocess.py", line 162, in 
_feed_stdin
await self.stdin.drain()
  File "/home/buildbot/python-master/Lib/asyncio/streams.py", line 443, in drain
await self._protocol._drain_helper()
  File "/home/buildbot/python-master/Lib/asyncio/streams.py", line 200, in 
_drain_helper
await waiter
  File "/home/buildbot/python-master/Lib/asyncio/unix_events.py", line 661, in 
_write_ready
n = os.write(self._fileno, self._buffer)
BrokenPipeError: [Errno 32] Broken pipe
test_cancel_at_end (test.test_asyncio.test_tasks.CTaskSubclass_PyFuture_Tests)
test_cancel_gather_1 (test.test_asyncio.test_tasks.CTaskSubclass_PyFuture_Tests)
test_return_coroutine_from_coroutine 
(test.test_asyncio.test_tasks.CTaskSubclass_PyFuture_Tests)
test_cancel_at_end (test.test_asyncio.test_tasks.CTask_CFuture_SubclassTests)
test_cancel_gather_1 (test.test_asyncio.test_tasks.CTask_CFuture_SubclassTests)
test_return_coroutine_from_coroutine 
(test.test_asyncio.test_tasks.CTask_CFuture_SubclassTests)
test_cancel_at_end (test.test_asyncio.test_tasks.CTask_CFuture_Tests)
test_cancel_gather_1 (test.test_asyncio.test_tasks.CTask_CFuture_Tests)
test_return_coroutine_from_coroutine 
(test.test_asyncio.test_tasks.CTask_CFuture_Tests)
test_cancel_at_end (test.test_asyncio.test_tasks.CTask_PyFuture_Tests)
test_cancel_gather_1 (test.test_asyncio.test_tasks.CTask_PyFuture_Tests)
test_return_coroutine_from_coroutine 
(test.test_asyncio.test_tasks.CTask_PyFuture_Tests)
test_cancel_at_end (test.test_asyncio.test_tasks.PyTask_CFutureSubclass_Tests)
test_cancel_gather_1 (test.test_asyncio.test_tasks.PyTask_CFutureSubclass_Tests)
test_return_coroutine_from_coroutine 
(test.test_asyncio.test_tasks.PyTask_CFutureSubclass_Tests)
test_cancel_at_end (test.test_asyncio.test_tasks.PyTask_CFuture_Tests)
test_cancel_gather_1 (test.test_asyncio.test_tasks.PyTask_CFuture_Tests)
test_return_coroutine_from_coroutine 
(test.test_asyncio.test_tasks.PyTask_CFuture_Tests)
test_cancel_at_end (test.test_asyncio.test_tasks.PyTask_PyFuture_SubclassTests)
test_cancel_gather_1 
(test.test_asyncio.test_tasks.PyTask_PyFuture_SubclassTests)
test_return_coroutine_from_coroutine 
(test.test_asyncio.test_tasks.PyTask_PyFuture_SubclassTests)
test_cancel_at_end (test.test_asyncio.test_tasks.PyTask_PyFuture_Tests)
test_cancel_gather_1 (test.test_asyncio.test_tasks.PyTask_PyFuture_Tests)
te

[issue36648] MAP_SHARED isn't proper for anonymous mappings for VxWorks

[STINNER Victor]

Change by STINNER Victor :


--
resolution:  -> fixed
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

[issue36816] self-signed.pythontest.net TLS certificate key is too weak

[Michael Felt]

Michael Felt  added the comment:

On 21/05/2019 12:08, Michael Felt wrote:
> Michael Felt  added the comment:
>
> p.s. On Centos I could not even get a python3 (at least not easily).
>
> On debian (on POWER) I get the same error (message) as on AIX - although the 
> line number did change.
>
> ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate 
> verify failed: self signed certificate (_ssl.c:1056)
>
> so, not a message about "key too small error" - pure, this is self-signed, so 
> error.
>
> --
p.s. blush: seems I was testing against the wrong fork - seems to be
cleared in 'master'. My apologies for the noise.
> ___
> Python tracker 
> 
> ___
>

--

___
Python tracker 

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

[issue36511] Add Windows ARM32 buildbot

[STINNER Victor]

Change by STINNER Victor :


--
nosy:  -vstinner

___
Python tracker 

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

[issue31850] test_nntplib failed with "nntplib.NNTPDataError: line too long"

[Matej Cepl]

Matej Cepl  added the comment:

Was this ever reproduced anywhere?

--
nosy: +mcepl

___
Python tracker 

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

[issue36973] test_json.test_recursion.TestPyRecursion.test_endless_recursion stack overflow in AMD64 Windows8.1 Non-Debug 3.x

[STINNER Victor]

STINNER Victor  added the comment:

> Buildbot error : https://buildbot.python.org/all/#/builders/12/builds/2497

It's AMD64 Windows8.1 Non-Debug 3.x:

test_endless_recursion (test.test_json.test_recursion.TestPyRecursion) ... ok
Fatal Python error: Cannot recover from stack overflow.

Current thread 0x0820 (most recent call first):
  File 
"D:\buildarea\3.x.ware-win81-release.nondebug\build\lib\json\decoder.py", line 
83 in py_scanstring
  File 
"D:\buildarea\3.x.ware-win81-release.nondebug\build\lib\json\decoder.py", line 
167 in JSONObject
  File 
"D:\buildarea\3.x.ware-win81-release.nondebug\build\lib\json\scanner.py", line 
37 in _scan_once
  (...)
  File 
"D:\buildarea\3.x.ware-win81-release.nondebug\build\lib\json\scanner.py", line 
37 in _scan_once
  File 
"D:\buildarea\3.x.ware-win81-release.nondebug\build\lib\json\decoder.py", line 
186 in JSONObject
  File 
"D:\buildarea\3.x.ware-win81-release.nondebug\build\lib\json\scanner.py", line 
37 in _scan_once
  File 
"D:\buildarea\3.x.ware-win81-release.nondebug\build\lib\json\decoder.py", line 
186 in JSONObject
  File 
"D:\buildarea\3.x.ware-win81-release.nondebug\build\lib\json\scanner.py", line 
37 in _scan_once
  File 
"D:\buildarea\3.x.ware-win81-release.nondebug\build\lib\json\decoder.py", line 
186 in JSONObject
  ...
test_highly_nested_objects_decoding 
(test.test_json.test_recursion.TestPyRecursion) ... 
D:\buildarea\3.x.ware-win81-release.nondebug\build>exit /b 0 

command timed out: 1200 seconds without output running 
[b'Tools\\buildbot\\test.bat', b'-x64', b'-j2', b'+d', b'-j4', b'--timeout', 
b'900'], attempting to kill
SIGKILL failed to kill process


> https://ci.appveyor.com/project/python/cpython/builds/24631185#L1547

test_endless_recursion (test.test_json.test_recursion.TestPyRecursion) ... ok
test_highly_nested_objects_decoding 
(test.test_json.test_recursion.TestPyRecursion) ... Fatal Python error: Cannot 
recover from stack overflow.
Current thread 0x0e2c (most recent call first):
  File "C:\projects\cpython\lib\json\decoder.py", line 83 in py_scanstring
  File "C:\projects\cpython\lib\json\decoder.py", line 167 in JSONObject
  File "C:\projects\cpython\lib\json\scanner.py", line 37 in _scan_once
  File "C:\projects\cpython\lib\json\decoder.py", line 186 in JSONObject
  File "C:\projects\cpython\lib\json\scanner.py", line 37 in _scan_once
  File "C:\projects\cpython\lib\json\decoder.py", line 186 in JSONObject
  File "C:\projects\cpython\lib\json\scanner.py", line 37 in _scan_once
  File "C:\projects\cpython\lib\json\decoder.py", line 186 in JSONObject
  File "C:\projects\cpython\lib\json\scanner.py", line 37 in _scan_once
  File "C:\projects\cpython\lib\json\decoder.py", line 186 in JSONObject
  File "C:\projects\cpython\lib\json\scanner.py", line 37 in _scan_once
  File "C:\projects\cpython\lib\json\decoder.py", line 186 in JSONObject
  File "C:\projects\cpython\lib\json\scanner.py", line 37 in _scan_once
  File "C:\projects\cpython\lib\json\decoder.py", line 186 in JSONObject
  File "C:\projects\cpython\lib\json\scanner.py", line 37 in _scan_once
  File "C:\projects\cpython\lib\json\decoder.py", line 186 in JSONObject
  (...)
  File "C:\projects\cpython\lib\json\scanner.py", line 37 in _scan_once
  File "C:\projects\cpython\lib\json\decoder.py", line 186 in JSONObject
  File "C:\projects\cpython\lib\json\scanner.py", line 37 in _scan_once
  File "C:\projects\cpython\lib\json\decoder.py", line 186 in JSONObject
  File "C:\projects\cpython\lib\json\scanner.py", line 37 in _scan_once
  File "C:\projects\cpython\lib\json\decoder.py", line 186 in JSONObject
  File "C:\projects\cpython\lib\json\scanner.py", line 37 in _scan_once
  File "C:\projects\cpython\lib\json\decoder.py", line 186 in JSONObject
  ...
C:\projects\cpython>set lastexitcode=-1073740791 
C:\projects\cpython>set  1>C:\Users\appveyor\AppData\Local\Temp\1\tmp4CD0.tmp 
C:\projects\cpython>echo C:\projects\cpython  
1>C:\Users\appveyor\AppData\Local\Temp\1\tmp4CD1.tmp 
C:\projects\cpython>exit /b -1073740791

--

___
Python tracker 

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

[issue36975] csv: undocumented UnicodeDecodeError on malformed file

[alter-bug-tracer]

alter-bug-tracer  added the comment:

Shouldn't all of them be documented? Either that, or converted to csv.Error? 
Take, for example, the C++ std.

--

___
Python tracker 

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

[issue36981] asyncio transport.write() memory out

[viocal]

viocal  added the comment:

thanks you 
but I think protocol.resume_writing() / protocol.pause_writing() is auto called 
  by Protocol
because set transport.set_write_buffer_limits(high=65536*2, low=16384*2) 
#default (high=65536, low=16384)

--

___
Python tracker 

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

[issue36973] test_json.test_recursion.TestPyRecursion.test_endless_recursion stack overflow in AMD64 Windows8.1 Non-Debug 3.x

[STINNER Victor]

STINNER Victor  added the comment:

The mashal also caused similar issues with stack overflow in the past:

commit f6c69e6cc9aac35564a2a2a7ecc43fa8db6da975
Author: Steve Dower 
Date:   Sat Nov 1 15:15:16 2014 -0700

#22734 marshal needs a lower stack depth for debug builds on Windows

commit 24e33acf8c422f6b8f84387242ff7874012f7291
Author: Victor Stinner 
Date:   Sun Jul 7 02:49:07 2013 +0200

Issue #17206: On Windows, increase the stack size from 2 MB to 4.2 MB to fix
a stack overflow in the marshal module (fix a crash in test_marshal).
Patch written by Jeremy Kloth.


History of PyOS_CheckStack:

commit 5299935be5acefae819bcc08a888a9466747d7cb
Author: Kristján Valur Jónsson 
Date:   Mon Feb 18 17:40:47 2008 +

Perform correct handling of stack overflow for windows: Catch the correct 
exception code and reset the overflow condition when handled.

commit dc61901dd2b1bcb5467ebc36ef35a51106d9b103
Author: Amaury Forgeot d'Arc 
Date:   Sat Nov 22 20:01:18 2008 +

#3996: On Windows, PyOS_CheckStack is supposed to protect the interpreter 
from
stack overflow. But doing this, it always crashes when the stack is nearly 
full.

Reviewed by Martin von Loewis. Will backport to 2.6.

commit 92e4dd865709f4a4be2b11453ef4de954b8d7b14
Author: Tim Peters 
Date:   Sat Oct 5 01:47:34 2002 +

s/_alloca/alloca/g; Windows doesn't need the former, at least not unless
__STDC__ is defined (or something like that ...).

commit 399739f79f1d6cef6bc8a8ec63f9a81255464f15
Author: Fred Drake 
Date:   Thu Aug 31 05:52:44 2000 +

PyOS_CheckStack():  Better ANSI'fy this while we're at it.

commit 2f15b25da2060ab723e0bb82a8f4f713d547b2b8
Author: Fredrik Lundh 
Date:   Sun Aug 27 19:15:31 2000 +

implements PyOS_CheckStack for Windows and MSVC.  this fixes a
couple of potential stack overflows, including bug #110615.

closes patch #101238

--

___
Python tracker 

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

[issue36816] self-signed.pythontest.net TLS certificate key is too weak

[Chih-Hsuan Yen]

Chih-Hsuan Yen  added the comment:

Hi Michael Felt,

> And, what it looks like you are trying to do with an updated 'signing" .pem 
> is to remove the 'self-signed' charasteric.

If I understand it correctly, the new certificate is indeed still self-signed. 
It's updated to match the certificate deployed at 
https://self-signed.pythontest.net/. Under the hood load_verify_locations() at 
line 1628 is used to make the test accept any valid certificate signed with the 
given certificate.

As a record, with CPython e7cb23bf2079087068a08502f96fdf20b317d69c and OpenSSL 
1.1.1b on Arch Linux x86_64, the test is green:

test_networked_good_cert (test.test_httplib.HTTPSTest) ... ok

By the way, I believe the "key too weak" workaround can be removed now and then 
this issue can be closed.

--

___
Python tracker 

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

[issue25329] test_json crashes with stack overflow on Windows

[STINNER Victor]

STINNER Victor  added the comment:

No activity for 4 years. I close the issue. See bpo-36973 for a similar issue 
in 2019.

--
resolution:  -> out of date
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

[issue36973] test_json.test_recursion.TestPyRecursion.test_endless_recursion stack overflow in AMD64 Windows8.1 Non-Debug 3.x

[STINNER Victor]

STINNER Victor  added the comment:

bpo-25329 was a similar json crash with stack overflow in 2015. The issue gives 
pointers to:

* bpo-25222: 3.5.0 regression - Fatal Python error: Cannot recover from stack 
overflow
* bpo-25342: test_json segfault on OpenBSD

--

___
Python tracker 

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

[issue36973] test_json.test_recursion.TestPyRecursion.test_endless_recursion stack overflow in AMD64 Windows8.1 Non-Debug 3.x

[STINNER Victor]

Change by STINNER Victor :


--
nosy: +serhiy.storchaka

___
Python tracker 

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

[issue36973] test_json.test_recursion.TestPyRecursion.test_endless_recursion stack overflow in AMD64 Windows8.1 Non-Debug 3.x

[STINNER Victor]

STINNER Victor  added the comment:

See also:

* bpo-25240: Stack overflow in reprlib causes a core dump
* bpo-28913: "Fatal Python error: Cannot recover from stack overflow." from 
RecursionError in Python 3.5
* bpo-22583: C stack overflow in the Python 2.7 compiler

--

___
Python tracker 

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

[issue31850] test_nntplib failed with "nntplib.NNTPDataError: line too long"

[STINNER Victor]

STINNER Victor  added the comment:

I didn't see this issue recently, so I just close it.

--
resolution:  -> out of date
stage:  -> 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

[issue35828] test_multiprocessing_fork: segmentation error in PyDict_GetItem on AIX

[STINNER Victor]

STINNER Victor  added the comment:

See also bpo-36752.

--
nosy: +vstinner
title: test_multiprocessing_fork - crashes in PyDict_GetItem - segmentation 
error -> test_multiprocessing_fork: segmentation error in PyDict_GetItem on AIX

___
Python tracker 

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

[issue36981] asyncio transport.write() memory out

[Andrew Svetlov]

Andrew Svetlov  added the comment:

No. pause_writing/resume_writing are protocol callbacks called by transport.
User code should respond to these callbacks by stopping sending data to 
transport (transport.write()).

The logic is a little complicated but it is ok for very low-level asyncio API.
Convenient user-facing wrappers like asyncio streams hide this logic by 
providing high-level primitives that support flow-control out of the box

I'm closing the issue, nothing to do here on asyncio low-level side.

--
resolution:  -> not a bug

___
Python tracker 

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

[issue36973] test_json.test_recursion.TestPyRecursion.test_endless_recursion stack overflow in AMD64 Windows8.1 Non-Debug 3.x

[Karthikeyan Singaravelan]

Karthikeyan Singaravelan  added the comment:

I have seen it occurring consistently in my PR 10307 in Travis and AppVeyor. It 
seems to be reproducible by importing ast at the top in inspect module which 
seems to have an effect as libregrtest is used to run the test_json. Using 
unittest module to run test_json doesn't seem to crash the last time I have 
checked.

--

___
Python tracker 

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

[issue35828] test_multiprocessing_fork: segmentation error in PyDict_GetItem on AIX

[STINNER Victor]

STINNER Victor  added the comment:

"""
...

_PyObject_FastCallDict(callable = (nil), args = 0x2008bf70, nargs = 540036208, 
kwargs = 0x014d), line 100 in "call.c"

object_vacall(callable = 0x100de658, vargs = warning: Unable to access address 
0xdbdbdbdb from core
(invalid char ptr (0xdbdbdbdb))), line 1200 in "call.c"

_PyObject_CallMethodIdObjArgs(obj = 0x30061db0, name = 0x20039710, ... = 
0x304e9fa8, 0x3003a7a0, 0x0, 0x4deb7, 0xcb, 0x306aee88), line 1250 in "call.c"

import_find_and_load(abs_name = 0x3097abf8), line 1652 in "import.c"

...
"""

Extract of _PyObject_CallMethodIdObjArgs:

PyObject *
_PyObject_CallMethodIdObjArgs(PyObject *obj,
  struct _Py_Identifier *name, ...)
{
va_list vargs;
PyObject *callable, *result;

if (obj == NULL || name == NULL) {
return null_error();
}

callable = _PyObject_GetAttrId(obj, name);
if (callable == NULL) {
return NULL;
}

va_start(vargs, name);
result = object_vacall(callable, vargs);
va_end(vargs);

Py_DECREF(callable);
return result;
}

I don't know how va_list and va_start are implemented in XLC, but 0xDBDBDBDB 
looks like the byte pattern for released memory in Python: you can now use 
_PyMem_IsPtrFreed() function from pycore_pymem.h to check if a pointer looks 
like "freed":

static inline int _PyMem_IsPtrFreed(void *ptr)
{
uintptr_t value = (uintptr_t)ptr;
#if SIZEOF_VOID_P == 8
return (value == (uintptr_t)0xCDCDCDCDCDCDCDCD
|| value == (uintptr_t)0x
|| value == (uintptr_t)0xFDFDFDFDFDFDFDFD);
#elif SIZEOF_VOID_P == 4
return (value == (uintptr_t)0xCDCDCDCD
|| value == (uintptr_t)0x
|| value == (uintptr_t)0xFDFDFDFD);
#else
#  error "unknown pointer size"
#endif
}

Maybe modify object_vacall() to add "assert(!_PyMem_IsPtrFreed(vargs));". You 
may need #include "pycore_pymem.h".

Good luck with debug :-(

--

___
Python tracker 

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

[issue36991] zipfile: AttributeError on extract

[alter-bug-tracer]

New submission from alter-bug-tracer :

The following code throws an AttributeError when attempting to extract a 
malformed archive (attached):

import zipfile
import sys

zf = zipfile.ZipFile(sys.argv[1])
for info in zf.infolist():
  zf.extract(info.filename)

Result:
Traceback (most recent call last):
  File "code.py", line 6, in 
zf.extract(info.filename)
  File "/usr/local/lib/python3.8/zipfile.py", line 1607, in extract
return self._extract_member(member, path, pwd)
  File "/usr/local/lib/python3.8/zipfile.py", line 1677, in _extract_member
with self.open(member, pwd=pwd) as source, \
  File "/usr/local/lib/python3.8/zipfile.py", line 1548, in open
return ZipExtFile(zef_file, mode, zinfo, zd, True)
  File "/usr/local/lib/python3.8/zipfile.py", line 801, in __init__
self._decompressor = _get_decompressor(self._compress_type)
  File "/usr/local/lib/python3.8/zipfile.py", line 708, in _get_decompressor
return bz2.BZ2Decompressor()
AttributeError: 'NoneType' object has no attribute 'BZ2Decompressor'

--
files: attr0.zip
messages: 343035
nosy: alter-bug-tracer
priority: normal
severity: normal
status: open
title: zipfile: AttributeError on extract
type: behavior
versions: Python 3.8
Added file: https://bugs.python.org/file48346/attr0.zip

___
Python tracker 

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

[issue36992] zipfile: AttributeError on extract (LZMA)

[alter-bug-tracer]

New submission from alter-bug-tracer :

The following code throws an AttributeError when attempting to extract a 
malformed archive (attached):

import zipfile
import sys

zf = zipfile.ZipFile(sys.argv[1])
for info in zf.infolist():
  zf.extract(info.filename)

Result:
Traceback (most recent call last):
  File "code.py", line 6, in 
zf.extract(info.filename)
  File "/usr/local/lib/python3.8/zipfile.py", line 1607, in extract
return self._extract_member(member, path, pwd)
  File "/usr/local/lib/python3.8/zipfile.py", line 1679, in _extract_member
shutil.copyfileobj(source, target)
  File "/usr/local/lib/python3.8/shutil.py", line 198, in copyfileobj
buf = fsrc_read(length)
  File "/usr/local/lib/python3.8/zipfile.py", line 903, in read
data = self._read1(n)
  File "/usr/local/lib/python3.8/zipfile.py", line 986, in _read1
data = self._decompressor.decompress(data)
  File "/usr/local/lib/python3.8/zipfile.py", line 635, in decompress
self._decomp = lzma.LZMADecompressor(lzma.FORMAT_RAW, filters=[
AttributeError: 'NoneType' object has no attribute 'LZMADecompressor'

--
files: attr1.zip
messages: 343036
nosy: alter-bug-tracer
priority: normal
severity: normal
status: open
title: zipfile: AttributeError on extract (LZMA)
type: behavior
versions: Python 3.8
Added file: https://bugs.python.org/file48347/attr1.zip

___
Python tracker 

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

[issue19613] test_nntplib: sporadic failures, test_article_head_body()

[Matej Cepl]

Matej Cepl  added the comment:

Could anybody make a PR from these patches? @vstinner, would you make me a 
review if I do it?

--
nosy: +mcepl

___
Python tracker 

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

[issue28971] nntplib is broken when responses are longer than _MAXLINE

[Matej Cepl]

Matej Cepl  added the comment:

Could @xdegaye make a PR for this?

--
nosy: +mcepl

___
Python tracker 

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

[issue36993] zipfile: tuple IndexError on extract

[alter-bug-tracer]

New submission from alter-bug-tracer :

The following code throws an IndexError when attempting to extract a malformed 
archive (attached):

import zipfile
import sys

zf = zipfile.ZipFile(sys.argv[1])
for info in zf.infolist():
  zf.extract(info.filename)

Result:
Traceback (most recent call last):
  File "code.py", line 4, in 
zf = zipfile.ZipFile(sys.argv[1])
  File "/usr/local/lib/python3.8/zipfile.py", line 1230, in __init__
self._RealGetContents()
  File "/usr/local/lib/python3.8/zipfile.py", line 1353, in _RealGetContents
x._decodeExtra()
  File "/usr/local/lib/python3.8/zipfile.py", line 480, in _decodeExtra
self.file_size = counts[idx]
IndexError: tuple index out of range

--
files: index_tuple.zip
messages: 343038
nosy: alter-bug-tracer
priority: normal
severity: normal
status: open
title: zipfile: tuple IndexError on extract
versions: Python 3.6, Python 3.7, Python 3.8
Added file: https://bugs.python.org/file48348/index_tuple.zip

___
Python tracker 

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

[issue36975] csv: undocumented UnicodeDecodeError on malformed file

[Rémi Lapeyre]

Rémi Lapeyre  added the comment:

I don't think all errors can be documented, csv iterate over the object but has 
no idea what it is. When writing for example, anything could happen, from a 
socket timing out, permissions errors, the underlying media being removed not 
properly, the media having no more space, etc...

ISTM that catching all those exceptions and hiding them behind csv.Error is bad 
practice and not recommended. In C++, uncaught exceptions are part of the 
function signature so it easier to do this but in Python we have no idea what 
the object you gave can raise when iterating over it.

--

___
Python tracker 

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

[issue36970] Rename _PyObject_FastCallKeywords

[Jeroen Demeyer]

Jeroen Demeyer  added the comment:

What's your opinion on renaming also

_PyCFunction_FastCallKeywords -> _PyCFunction_Vectorcall
_PyFunction_FastCallKeywords -> _PyFunction_Vectorcall

If you agree, I will add it to the PR.

--

___
Python tracker 

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

[issue36970] Rename _PyObject_FastCallKeywords

[STINNER Victor]

Change by STINNER Victor :


--
nosy:  -vstinner

___
Python tracker 

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

[issue36970] Rename _PyObject_FastCallKeywords

[Jeroen Demeyer]

Change by Jeroen Demeyer :


--
title: Rename _PyObject_FastCall functions -> Rename _PyObject_FastCallKeywords

___
Python tracker 

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

[issue36981] asyncio transport.write() memory out

[viocal]

viocal  added the comment:

for example 
the system free memory size is 512m
and filedata size is 500m
will transport Success
but filedata than 512m will be failed

--
resolution: not a bug -> 

___
Python tracker 

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

[issue36994] Missing tests for CALL_FUNCTION_EX opcode profiling method_descriptor

[Jeroen Demeyer]

New submission from Jeroen Demeyer :

The branch for profiling a method_descriptor inside do_call_core is not tested 
by the test suite.

--
components: Tests
messages: 343044
nosy: jdemeyer
priority: normal
severity: normal
status: open
title: Missing tests for CALL_FUNCTION_EX opcode profiling method_descriptor
versions: Python 3.8

___
Python tracker 

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

[issue36981] asyncio transport.write() memory out

[Andrew Svetlov]

Andrew Svetlov  added the comment:

Please re-read my previous comment.
If you use asyncio incorrectly -- yes, you can run out of memory.
The proper usage of pause_readind()/resume_reading() resolves the issue.

--

___
Python tracker 

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

[issue30458] [security][CVE-2019-9740][CVE-2019-9947] HTTP Header Injection (follow-up of CVE-2016-5699)

[STINNER Victor]

STINNER Victor  added the comment:


New changeset bb8071a4cae5ab3fe321481dd3d73662ffb26052 by Victor Stinner in 
branch '2.7':
bpo-30458: Disallow control chars in http URLs (GH-12755) (GH-13154) (GH-13315)
https://github.com/python/cpython/commit/bb8071a4cae5ab3fe321481dd3d73662ffb26052


--

___
Python tracker 

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

[issue36084] Threading: add builtin TID attribute to Thread objects

[Jake Tesler]

Jake Tesler  added the comment:

I will implement these changes - let’s try to hit that end-of-month target!

--

___
Python tracker 

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

[issue36994] Missing tests for CALL_FUNCTION_EX opcode profiling method_descriptor

[Jeroen Demeyer]

Change by Jeroen Demeyer :


--
keywords: +patch
pull_requests: +13371
stage:  -> patch review

___
Python tracker 

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

[issue36988] zipfile: string IndexError on extract

[JUN-WEI SONG]

JUN-WEI SONG  added the comment:

The following output throws error when using unzip -t 

$ unzip -t file0.zip

Output:

Archive:  file0.zip
:  mismatching "local" filename (zipfile_extract.pyUT^I),
 continuing with "central" filename version
testing: 
  error:  invalid compressed data to inflate
At least one error was detected in file0.zip.

It looks like the zip file is corrupted. Maybe we could add some detection 
mechanisms before extract it like unzip, for example, unsupported characters or 
file corrupted check.

--
nosy: +krnick

___
Python tracker 

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

[issue36797] Cull more oudated distutils information

[Nick Coghlan]

Change by Nick Coghlan :


--
pull_requests: +13372

___
Python tracker 

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

[issue36797] Cull more oudated distutils information

[Nick Coghlan]

Nick Coghlan  added the comment:

While I do have a second PR open with some additional smaller cleanups, the 
first PR removed the outdated information that seemed most problematic.

--
resolution:  -> fixed
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

[issue36978] `python3 -m pip install` has no `--requirement` option on Windows

[Eric V. Smith]

Change by Eric V. Smith :


--
stage:  -> test needed
status: open -> pending
type:  -> behavior

___
Python tracker 

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

[issue33071] Document that PyPI no longer requires 'register'

[Nick Coghlan]

Nick Coghlan  added the comment:

This has been merged for 3.8 and 3.7, but not for 2.7, since the docs have 
diverged far enough that the automatic backport didn't work: 
https://github.com/python/cpython/pull/13087#issuecomment-494402704

Given the proximity to the general end of life of the Python 2.7 documentation 
anyway, I'm inclined to just close this based on the 3.x changes, and not worry 
about the 2.7 version of the docs.

Thoughts?

--
stage: patch review -> backport needed
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

[issue36980] pass-by-reference clues

[stefan]

stefan  added the comment:

Thank you for your reply and the lucid explanation.

On Monday, May 20, 2019, 9:17:34 PM EDT, Josh Rosenberg 
 wrote:  

Josh Rosenberg  added the comment:

1. This is a bug tracker for bugs in the Python language spec and the CPython 
interpreter, not a general problem solving site.

2. The ids will differ for changeValue2 if you actually call it (kernel = 
kernel + 2 requires the the old id of kernel differ from the new id, because 
they both exist simultaneously, and are different objects); I'm guessing you're 
calling the wrong function or printing the ids of the wrong variables.

3. "Would it possible for the python interpreter/compiler to let me know when a 
function is going to clobber a variable that is not used in the function or 
passed to the function or returned by the function" Every bit of clobbering 
you're seeing involves a variable passed to the function (and sometimes 
returned by it). CVkernel=myKernel just made two names that bind to the same 
underlying object, so passing either name as an argument to a function that 
modifies its arguments will modify what is seen from both names. That's how 
mutable objects work. This is briefly addressed in the tutorial here: 
https://docs.python.org/3/tutorial/classes.html#a-word-about-names-and-objects 
. As a general rule, Python built-ins *either* modify their arguments in place 
and return nothing (None) *or* return new values leaving the arguments 
unmodified. It's a matter of programmer discipline to adhere to this practice 
in your own code (numpy does make it harder, since it uses views extensively, 
making sli
 cing not an effective way to copy inputs).

All that said, this isn't a bug. It's a longstanding feature of Python alias 
arguments to avoid expensive deep copies by default; the onus is on the 
function writer to copy if needed, or to document the behavior if mutation of 
the arguments is to occur.

--
nosy: +josh.r

___
Python tracker 

___

--

___
Python tracker 

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

[issue36980] pass-by-reference clues

[stefan]

stefan  added the comment:

Thank you for your reply and the lucid explanation. 
On Monday, May 20, 2019, 9:15:42 PM EDT, Steven D'Aprano 
 wrote:  

Steven D'Aprano  added the comment:

Hi Stefan, and welcome. 

This is not a help desk, you really should ask elsewhere for explanations of 
how Python works. There are no bugs here: what you are seeing is standard 
pass-by-object behaviour.

You are misinterpreting what you are seeing. Python is never pass by reference 
or pass by value.

https://en.wikipedia.org/wiki/Evaluation_strategy

https://www.effbot.org/zone/call-by-object.htm

*All* function objects, whether strings, ints, lists or numpy arrays, are 
passed as objects. If you want to make a copy, you have to explicitly make a 
copy. If you don't, and you mutate the object in place, you will see the 
mutation in both places.

> Shouldn't the id of each variable be different if they are different 
> instances?

Not necessarily: IDs can be reused. Without seeing the actual running code, I 
can't tell if the IDs have been used or if they are the same ID because they 
are the same object.

> Would it possible for the python interpreter/compiler to let me know when a 
> function is going to clobber a variable that is not used in the function or 
> passed to the function or returned by the function

Python never clobbers a variable not used in the function. It may however 
mutate an object which is accessible from both inside and outside a function.

--
nosy: +steven.daprano
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

___
Python tracker 

___

--

___
Python tracker 

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

[issue36988] zipfile: string IndexError on extract

[alter-bug-tracer]

alter-bug-tracer  added the comment:

Hi,

The zip is corrupted on purpose.
I agree, every input should be checked before doing stuff with it.

--

___
Python tracker 

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

[issue28971] nntplib is broken when responses are longer than _MAXLINE

[Xavier de Gaye]

Xavier de Gaye  added the comment:

What do you mean ?
What is "this" ?

--

___
Python tracker 

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

[issue36230] Please sort assertSetEqual's output

[Rémi Lapeyre]

Rémi Lapeyre  added the comment:

Hi Jess, are you still working on this?

--

___
Python tracker 

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

[issue28971] nntplib is broken when responses are longer than _MAXLINE

[Matthias Bussonnier]

Matthias Bussonnier  added the comment:

Would that be anyway closed by pep 594 
(https://www.python.org/dev/peps/pep-0594/#nntplib) which suggest the removal 
nntp ?

--
nosy: +mbussonn

___
Python tracker 

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

[issue36084] Threading: add builtin TID attribute to Thread objects

[Jake Tesler]

Change by Jake Tesler :


--
pull_requests: +13373

___
Python tracker 

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

[issue28971] nntplib is broken when responses are longer than _MAXLINE

[Matej Cepl]

Matej Cepl  added the comment:

@mbussonn That's exactly the point: I completely disagree with removal of 
nntplib from the standard library, so I went through all bugs here related to 
it.

--

___
Python tracker 

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

[issue28971] nntplib is broken when responses are longer than _MAXLINE

[Christian Heimes]

Christian Heimes  added the comment:

No, the module is still supported until EOL of Python 3.9. I expect 3.9 to go 
into security fix-only mode in 2024.

--
versions: +Python 3.8, Python 3.9 -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

[issue36084] Threading: add builtin TID attribute to Thread objects

[Jake Tesler]

Jake Tesler  added the comment:

New PR created with requested edits. :)

--

___
Python tracker 

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

[issue36084] Threading: add builtin TID attribute to Thread objects

[Jake Tesler]

Jake Tesler  added the comment:

Victor Stinner: would you mind taking a look at the new PR? Is this more along 
the lines of what you had in mind?

--

___
Python tracker 

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

[issue36995] tp_print -> tp_vectorcall_offset

[Jeroen Demeyer]

New submission from Jeroen Demeyer :

If PEP 590 is accepted: in code comments, replace tp_print by 
tp_vectorcall_offset and (while we're at it) tp_reserved by tp_as_async.

--
components: Interpreter Core
messages: 343061
nosy: Mark.Shannon, jdemeyer, petr.viktorin
priority: normal
severity: normal
status: open
title: tp_print -> tp_vectorcall_offset
versions: Python 3.8

___
Python tracker 

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

[issue28971] nntplib is broken when responses are longer than _MAXLINE

[Christian Heimes]

Christian Heimes  added the comment:

Matej, would you be interested to fork nntplib and take over maintenance and 
responsibility?

--

___
Python tracker 

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

[issue36970] Rename _PyObject_FastCallKeywords

[Petr Viktorin]

Petr Viktorin  added the comment:

If and when a function uses the vectorcall protocol (including the argument 
offset flag), it makes sense to rename it to vectorcall. Doing it before is 
misleading, IMO.

Splitting fixes to unrelated issues (like bpo-36907) from PEP 590 is great, but 
this one needs to be merged together with PEP 590.

--

___
Python tracker 

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

[issue28971] nntplib is broken when responses are longer than _MAXLINE

[Matej Cepl]

Matej Cepl  added the comment:

If that was the price of keeping nntplib inside of the Python standard library, 
yes.

--

___
Python tracker 

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

[issue36995] tp_print -> tp_vectorcall_offset

[Petr Viktorin]

Petr Viktorin  added the comment:

All these issues are quite confusing. If PEP 590 is accepted, all of it will 
need to be implemented. Why open separate issues for all the parts?

--

___
Python tracker 

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

[issue33563] fileinput input's and Fileinput's bufsize=0 do not remit deprecationWarnings

[Matthias Bussonnier]

Matthias Bussonnier  added the comment:

bufsize has now been removed.

--
resolution:  -> fixed
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