[issue36121] csv: Non global alternative to csv.field_size_limit

New submission from Carlos Ramos : The function csv.field_size_limit gets and sets a global variable. It would be useful to change this limit in a per-reader or per-thread basis, so that a library can change it without affecting global state. -- components: Extension Modules

[issue36120] Regression - Concurrent Futures

Jonathan added the comment: There's also this error too: Traceback (most recent call last): File "c:\_libs\Python37\lib\multiprocessing\process.py", line 297, in _bootstrap self.run() File "c:\_libs\Python37\lib\multiprocessing\process.py", line 99, in run

[issue36120] Regression - Concurrent Futures

New submission from Jonathan : I'm using Concurrent Futures to run some work in parallel (futures.ProcessPoolExecutor) on windows 7 x64. The code works fine in 3.6.3, and 3.5.x before that. I've just upgraded to 3.7.2 and it's giving me these errors: Process SpawnProcess-6: Traceback (most

[issue36103] Increase shutil.COPY_BUFSIZE

Inada Naoki added the comment: > Also on Linux "echo 3 | sudo tee /proc/sys/vm/drop_caches" is supposed to > disable the cache. As I said already, shutil is not used only with cold cache. If cache is cold, disk speed will be upper bound in most cases. But when cache is hot, or using very

[issue35459] Use PyDict_GetItemWithError() instead of PyDict_GetItem()

STINNER Victor added the comment: > It seems like the change introduced a regression: bpo-36110. While the test has been fixed, IMHO we need to better document this subtle behavior change since it can be surprising. The test failed because PyObject_GetAttr() no longer ignores exceptions

[issue34624] -W option and PYTHONWARNINGS env variable does not accept module regexes

Nick Coghlan added the comment: I think the only reason I didn't mention this discrepancy in my doc updates is because I wasn't aware there *was* a discrepancy. The weird syntax was then just an incorrect amalgamation of "optional argument" notation with an improperly escaped regex suffix.

[issue35652] Add use_srcentry parameter to shutil.copytree() II

Giampaolo Rodola' added the comment: New changeset c606a9cbd48f69d3f4a09204c781dda9864218b7 by Giampaolo Rodola in branch 'master': bpo-35652: shutil.copytree(copy_function=...) erroneously pass DirEntry instead of path str (GH-11997)

[issue36119] Can't add/append in set/list inside shared dict

Karthikeyan Singaravelan added the comment: https://docs.python.org/3/library/multiprocessing.html#proxy-objects > If standard (non-proxy) list or dict objects are contained in a referent, > modifications to those mutable values will not be propagated through the > manager because the proxy

[issue36103] Increase shutil.COPY_BUFSIZE

Giampaolo Rodola' added the comment: @Inada: having played with this in the past I seem to remember that on Linux the bigger bufsize doesn't make a reasonable difference (but I may be wrong), that's why I suggest to try some benchmarks. In issue33671 I pasted some one-liners you can use

[issue36109] test_descr: test_vicious_descriptor_nonsense() fails randomly

Change by STINNER Victor : -- title: test_descr fails on AMD64 Windows8 3.x buildbots -> test_descr: test_vicious_descriptor_nonsense() fails randomly ___ Python tracker ___

[issue36119] Can't add/append in set/list inside shared dict

New submission from Andrei Stefan : I'm creating a shared dict for multiprocessing purposes: from multiprocessing import Manager manager = Manager() shared_dict = manager.dict() If I add a set or a list as a value in the dict: shared_dict['test'] = set() or shared_dict['test'] = list() I

[issue36106] resolve sinpi() name clash with libm

Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue36106] resolve sinpi() name clash with libm

Serhiy Storchaka added the comment: New changeset b545ba0a508a5980ab147ed2641a42be3b31a2db by Serhiy Storchaka (Dima Pasechnik) in branch '2.7': [2.7] bpo-36106: resolve sinpi name clash with libm (IEEE-754 violation). (GH-12027) (GH-12050)

[issue36030] add internal API function to create tuple without items array initialization

Sergey Fedoseev added the comment: This optimization also can be used for BUILD_TUPLE opcode and in pickle module, if it's OK to add _PyTuple_StealFromArray() function :-) -- ___ Python tracker

[issue36030] add internal API function to create tuple without items array initialization

Sergey Fedoseev added the comment: I added WIP PR with discussed micro-optimization, here are benchmark results: $ python -m perf compare_to --min-speed 1 -G master.json tuple-untracked.json Slower (1): - sqlite_synth: 5.16 us +- 0.10 us -> 5.22 us +- 0.08 us: 1.01x slower (+1%) Faster (19):

[issue36117] Allow rich comparisons for real-valued complex objects.

Eric V. Smith added the comment: -1. We don't want to have objects that are orderable depending on their values. I can't think of anywhere else we do this. It would be very easy to have a complex == 42+0.001j, after some calculation. This near-zero imaginary part would prevent it from

[issue36030] add internal API function to create tuple without items array initialization

Change by Sergey Fedoseev : -- pull_requests: +12078 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue31904] Python should support VxWorks RTOS

Change by Peixing Xin : -- pull_requests: +12077 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36106] resolve sinpi() name clash with libm

Change by Dmitrii Pasechnik : -- pull_requests: +12076 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue26228] pty.spawn hangs on FreeBSD 9.3, 10.x

Geoff Shannon added the comment: I took a shot at fixing this in a smaller more targeted patch. I think this should still solve the major issue of pty.spawn hanging on platforms that don't raise an error. In addition, pty.spawn should now _ALWAYS_ return the terminal to the previous

[issue26228] pty.spawn hangs on FreeBSD 9.3, 10.x

Change by Geoff Shannon : -- pull_requests: +12074 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36118] Cannot correctly concatenate nested list that contains more than ~45 entries with other nested lists.

Steven D'Aprano added the comment: I cannot reproduce the behaviour you show. First problem: ``...`` is a legal Python object, Ellipsis, so your example code literally means: # x = [["a", "b", ... , "BZ"]] x is a list containing one sublist, which contains exactly four objects. So when I

[issue36118] Cannot correctly concatenate nested list that contains more than ~45 entries with other nested lists.

New submission from Domenico Barbieri : Here is an example of what happens: >>> x = [["a", "b", ... , "BZ"]] >>> y = [[], [1,2,3,4,5, ... , 99]] >>> y[0] = x[0] >>> print(y[0]) >>> ["a", "b", "c", ... , "BZ", [1,2,3,4,5, ... , 99]] -- messages: 336634 nosy: Domenico Barbieri priority:

[issue36106] resolve sinpi() name clash with libm

Kubilay Kocak added the comment: Downstream issue: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232792 -- nosy: +koobs versions: +Python 2.7, Python 3.8 ___ Python tracker

[issue36117] Allow rich comparisons for real-valued complex objects.

Mark Dickinson added the comment: -1 from me. The rules for when things are comparable or not should be kept simple. -- ___ Python tracker ___

[issue36117] Allow rich comparisons for real-valued complex objects.

Brandt Bucher added the comment: I don't really see, though, how comparing complex(42) == float(42) is any less dangerous than complex(42) <= float(42). It seems odd to me, personally, that real-valued complex objects are valid for *some* rich comparisons (but not others) when the math is

[issue36117] Allow rich comparisons for real-valued complex objects.

Serhiy Storchaka added the comment: If you need to order real-valued complex object, convert them to float objects first. -- ___ Python tracker ___

[issue36117] Allow rich comparisons for real-valued complex objects.

Serhiy Storchaka added the comment: I don't think we should do this. In numerical computation we should not depend on exact floating point values, because is affected by computation errors. It would be hard to debug the program when some complex numbers are orderable, but other are not, and

[issue36117] Allow rich comparisons for real-valued complex objects.

Change by Brandt Bucher : -- keywords: +patch pull_requests: +12073 stage: -> patch review ___ Python tracker ___ ___

[issue36117] Allow rich comparisons for real-valued complex objects.

New submission from Brandt Bucher : Currently, it isn't legal to perform <, >, <=, or >= rich comparisons on any complex objects, even though these operations are mathematically well-defined for real numbers. The attached PR addresses this by defining rich comparisons for real-valued

<    1   2