[issue31808] tarfile.extractall fails to overwrite symlinks

Dong-hee Na added the comment: I 've submitted the patch please take a look. -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue32044] pip3 install 3.6.3 crashes on startup; 3.5.4 works; on OS X 10.13.1

Berker Peksag added the comment: 1) Don't reopen a closed issue. 2) Please use python-list or StackOverflow for usage questions. You need to replace 'pip' with 'pip3' in your case. If you get a similar error with 'pip3', try 'sudo pip3 install -U ...' or 'pip3 install --user -U ...'.

[issue32046] 2to3 fix for operator.isCallable()

New submission from Serhiy Storchaka : Currently 2to3 converts `operator.isCallable(obj)` to `hasattr(obj, '__call__')`. This looks cumbersome, and can be deceived by instance attribute __call__. The more correct way is to use `isinstance(obj, collections.abc.Callable)`. Starting from Python 3

[issue32045] Does json.dumps have a memory leak?

Serhiy Storchaka added the comment: indent=True just makes json to use Python implementation instead of C implementation. Python implementation uses closures which reference one other. Simple example not involving json is: import gc def f(): def g(): return h def h():

[issue31808] tarfile.extractall fails to overwrite symlinks

Change by Dong-hee Na : -- nosy: +corona10 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue31808] tarfile.extractall fails to overwrite symlinks

Change by Dong-hee Na : -- keywords: +patch pull_requests: +4364 stage: needs patch -> patch review ___ Python tracker ___ ___ Python

[issue32045] Does json.dumps have a memory leak?

New submission from Rohan D'Sa : import gc, json class leak(object): def __init__(self): pass gc.set_debug(gc.DEBUG_LEAK) while True: leak_ = leak() json.dumps(leak_.__dict__, indent=True) gc.collect() print(f"garbage count: {len(gc.garbage)}") Using the following c

[issue32027] argparse allow_abbrev option also controls short flag combinations

Berker Peksag added the comment: Thank you for the report and for the PR. I think this is a duplicate of issue 26967. > This issue is either a doc issue only or an unintended combination of > long option shortening and (the way more common) flag combinations. This is indeed a bug so it would

<    1   2