[issue46347] memory leak in PyEval_EvalCodeEx
Elvis Pranskevichus added the comment: The leak was introduced in 3.10a5 (https://github.com/python/cpython/commit/0332e569c12d3dc97171546c6dc10e42c27de34b) -- ___ Python tracker <https://bugs.python.org/issue46347> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46347] memory leak in PyEval_EvalCodeEx
Elvis Pranskevichus added the comment: I can confirm that removing the kwargs allocation prevents the leak described in the asyncpg issue from happening. -- ___ Python tracker <https://bugs.python.org/issue46347> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue44883] configure --with-openssl-rpath=DIR too eager about existence of DIR
New submission from Elvis Pranskevichus : https://bugs.python.org/issue43466 added a way to set OpenSSL rpath explicitly via --with-openssl-rpath=DIR, which is cool! However, the current configuration code checks for the presence of the specified directory eagerly, which breaks setups where both OpenSSL and Python are being built at the same time, but not necessarily installed to the runtime location (think omnibus debs). Unless there's a good reason why an eager check is needed, I think it should be dropped to ease packaging. -- assignee: christian.heimes components: Installation, SSL messages: 399368 nosy: Elvis.Pranskevichus, christian.heimes priority: normal severity: normal status: open title: configure --with-openssl-rpath=DIR too eager about existence of DIR versions: Python 3.10 ___ Python tracker <https://bugs.python.org/issue44883> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37658] In some cases asyncio.wait_for can lead to socket leak.
Change by Elvis Pranskevichus : -- pull_requests: +21078 pull_request: https://github.com/python/cpython/pull/21969 ___ Python tracker <https://bugs.python.org/issue37658> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32751] wait_for(future, ...) should wait for the future (even if a timeout occurs)
Change by Elvis Pranskevichus : -- pull_requests: +21077 pull_request: https://github.com/python/cpython/pull/21968 ___ Python tracker <https://bugs.python.org/issue32751> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32751] wait_for(future, ...) should wait for the future (even if a timeout occurs)
Change by Elvis Pranskevichus : -- pull_requests: +21076 pull_request: https://github.com/python/cpython/pull/21967 ___ Python tracker <https://bugs.python.org/issue32751> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32751] wait_for(future, ...) should wait for the future (even if a timeout occurs)
Change by Elvis Pranskevichus : -- nosy: +Elvis.Pranskevichus nosy_count: 6.0 -> 7.0 pull_requests: +21014 pull_request: https://github.com/python/cpython/pull/21895 ___ Python tracker <https://bugs.python.org/issue32751> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37658] In some cases asyncio.wait_for can lead to socket leak.
Change by Elvis Pranskevichus : -- keywords: +patch nosy: +Elvis.Pranskevichus nosy_count: 3.0 -> 4.0 pull_requests: +21013 stage: -> patch review pull_request: https://github.com/python/cpython/pull/21894 ___ Python tracker <https://bugs.python.org/issue37658> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38400] Python segfaults when configured with --with-pydebug --with-trace-refs
Elvis Pranskevichus added the comment: Thanks for the lightning-fast turnaround, Pablo! -- ___ Python tracker <https://bugs.python.org/issue38400> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38400] Python segfaults when configured with --with-pydebug --with-trace-refs
Elvis Pranskevichus added the comment: Since https://bugs.python.org/issue38070 was backported to 3.8, shouldn't this as well? 3.8 is currently broken otherwise. -- nosy: +Elvis.Pranskevichus ___ Python tracker <https://bugs.python.org/issue38400> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23734] zipimport should not check pyc timestamps against zipped py files
Elvis Pranskevichus added the comment: I don't think that breaking the .pyc contract by assumption is a good thing. The desired behavior of never checking the .pyc freshness can be achieved by using unchecked hash-based compilation, or using hash-based compilation and --check-hash-based-pycs=never. Perhaps we can go further and add a --check-timestamp-based-pycs=never, but IMO, this should be explicit in all cases, including zipimport. -- nosy: +Elvis.Pranskevichus ___ Python tracker <https://bugs.python.org/issue23734> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23734] zipimport should not check pyc timestamps against zipped py files
Change by Elvis Pranskevichus : -- keywords: +patch pull_requests: +9638 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue23734> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34726] Add support of checked hash-based pycs in zipimport
Change by Elvis Pranskevichus : -- pull_requests: +9637 stage: needs patch -> patch review ___ Python tracker <https://bugs.python.org/issue34726> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34022] 6 tests fail using SOURCE_DATE_EPOCH env var
Elvis Pranskevichus added the comment: https://github.com/python/cpython/pull/10327 fixes the remaining test failures. -- ___ Python tracker <https://bugs.python.org/issue34022> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34022] 6 tests fail using SOURCE_DATE_EPOCH env var
Change by Elvis Pranskevichus : -- pull_requests: +9630 ___ Python tracker <https://bugs.python.org/issue34022> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34872] investigate task/future cancellation in asynciomodule.c
Change by Elvis Pranskevichus : -- pull_requests: +9078 ___ Python tracker <https://bugs.python.org/issue34872> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34872] investigate task/future cancellation in asynciomodule.c
Change by Elvis Pranskevichus : -- pull_requests: +9077 ___ Python tracker <https://bugs.python.org/issue34872> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34872] investigate task/future cancellation in asynciomodule.c
Change by Elvis Pranskevichus : -- keywords: +patch pull_requests: +9068 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue34872> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34022] 6 tests fail using SOURCE_DATE_EPOCH env var
Elvis Pranskevichus added the comment: https://github.com/python/cpython/pull/9607 turns SOURCE_DATE_EPOCH into a *default* rather than absolute override. test_cmd_line_script and test_runpy fail due to the lack of support for hash-based .pycs in zipimport, which needs fixing also. -- ___ Python tracker <https://bugs.python.org/issue34022> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29708] support reproducible Python builds
Change by Elvis Pranskevichus : -- pull_requests: +9005 ___ Python tracker <https://bugs.python.org/issue29708> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34022] 6 tests fail using SOURCE_DATE_EPOCH env var
Change by Elvis Pranskevichus : -- pull_requests: +9004 ___ Python tracker <https://bugs.python.org/issue34022> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34022] 6 tests fail using SOURCE_DATE_EPOCH env var
Elvis Pranskevichus added the comment: Perhaps SOURCE_DATE_EPOCH should only be consulted to determine the default behavior if invalidation_mode was not passed explicitly to py_compile.compile(). -- ___ Python tracker <https://bugs.python.org/issue34022> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34022] 6 tests fail using SOURCE_DATE_EPOCH env var
Elvis Pranskevichus added the comment: > In particular, if a build system sets SOURCE_DATE_EPOCH without specifying a pyc format for py_compile or compileall, Python 3.7 will give you checked hashes by default Actually, py_compile will _force_ the CHECKED_HASH mode if SOURCE_DATE_EPOCH is set, regardless of what you specified for py_compile or compileall. I'm not sure if that's actually intended or a bug. The fix for the tests is to actually be aware of py_compile behavior and control for SOURCE_DATE_EPOCH. I submitted a PR with a fix. -- nosy: +Elvis.Pranskevichus ___ Python tracker <https://bugs.python.org/issue34022> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34022] 6 tests fail using SOURCE_DATE_EPOCH env var
Change by Elvis Pranskevichus : -- keywords: +patch pull_requests: +8894 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue34022> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34537] test_gdb fails with LC_ALL=C
Change by Elvis Pranskevichus : -- keywords: +patch pull_requests: +8893 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue34537> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33649] asyncio docs overhaul
Change by Elvis Pranskevichus : -- pull_requests: +8800 ___ Python tracker <https://bugs.python.org/issue33649> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34075] asyncio: We should prohibit setting a ProcessPoolExecutor in with set_default_executor
Change by Elvis Pranskevichus : -- keywords: +patch pull_requests: +8050 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue34075> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32996] Improve What's New in 3.7
Change by Elvis Pranskevichus : -- pull_requests: +7599 ___ Python tracker <https://bugs.python.org/issue32996> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33736] Improve the documentation of asyncio stream API
Change by Elvis Pranskevichus : -- keywords: +patch pull_requests: +6955 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue33736> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33736] Improve the documentation of asyncio stream API
Change by Elvis Pranskevichus : -- assignee: docs@python components: Documentation nosy: Elvis.Pranskevichus, docs@python priority: normal severity: normal status: open title: Improve the documentation of asyncio stream API type: enhancement versions: Python 3.7, Python 3.8 ___ Python tracker <https://bugs.python.org/issue33736> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23859] asyncio: document behaviour of wait() cancellation
Change by Elvis Pranskevichus : -- pull_requests: +6862 ___ Python tracker <https://bugs.python.org/issue23859> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23859] asyncio: document behaviour of wait() cancellation
Change by Elvis Pranskevichus : -- keywords: +patch pull_requests: +6850 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue23859> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33638] condition lock not re-acquired
Change by Elvis Pranskevichus : -- keywords: +patch pull_requests: +6849 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue33638> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32751] wait_for(future, ...) should wait for the future (even if a timeout occurs)
Change by Elvis Pranskevichus : -- keywords: +patch pull_requests: +6848 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue32751> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33592] Document contextvars C API
Change by Elvis Pranskevichus : -- keywords: +patch pull_requests: +6679 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue33592> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33592] Document contextvars C API
New submission from Elvis Pranskevichus : The C API for PEP 567 is currently missing. -- assignee: docs@python components: Documentation messages: 317244 nosy: Elvis.Pranskevichus, docs@python, yselivanov priority: normal severity: normal status: open title: Document contextvars C API type: enhancement versions: Python 3.7 ___ Python tracker <https://bugs.python.org/issue33592> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32996] Improve What's New in 3.7
Change by Elvis Pranskevichus : -- pull_requests: +6651 ___ Python tracker <https://bugs.python.org/issue32996> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32996] Improve What's New in 3.7
Elvis Pranskevichus added the comment: Thanks for the feedback Serhiy! I'll make an editorial pass to address the comments shortly. In general, I prefer thoroughness in the initial What's New edit to make sure we don't miss something important. -- ___ Python tracker <https://bugs.python.org/issue32996> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32996] Improve What's New in 3.7
Change by Elvis Pranskevichus : -- pull_requests: +6633 ___ Python tracker <https://bugs.python.org/issue32996> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32622] Implement loop.sendfile
Change by Elvis Pranskevichus : -- pull_requests: +5211 ___ Python tracker <https://bugs.python.org/issue32622> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32630] Migrate decimal to use PEP 567 context variables
Elvis Pranskevichus added the comment: Likewise, on the same builds, running _decimal/tests/bench.py does not show a significant difference: https://gist.github.com/elprans/fb31510ee28a3aa091aee3f42fe65e00 -- ___ Python tracker <https://bugs.python.org/issue32630> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32630] Migrate decimal to use PEP 567 context variables
Elvis Pranskevichus added the comment: FWIW, I ran bm_telco with pyperformance on a benchmark-tuned system and did not observe the slowdown. Benchmarks were done on a release build (--enable-optimizations) $ sudo (which python3) -m perf system tune MASTER: $ pyperformance run --python=envs/3.7-master-pgo-lto/prefix/bin/python3.7m --affinity=2,3 --rigorous --benchmarks=telco -o json/3.7-master.json Python benchmark suite 0.6.1 [1/1] telco... INFO:root:Running `/home/elvis/dev/python/performance/venv/cpython3.7-8cfe759dd297/bin/python -u /home/elvis/dev/python/performance/performance/benchmarks/bm_telco.py --rigorous --affinity=2,3 --output /tmp/tmpgszxc792` . telco: Mean +- std dev: 9.17 ms +- 0.32 ms MASTER + contextvars patch: $ pyperformance run --python=envs/3.7-master-pgo+lto+decimal-contextvars/prefix/bin/python3.7m --affinity=2,3 --rigorous --benchmarks=telco -o json/3.7-contextvars.json Python benchmark suite 0.6.1 [1/1] telco... INFO:root:Running `/home/elvis/dev/python/performance/venv/cpython3.7-8a6fbdee5a5b/bin/python -u /home/elvis/dev/python/performance/performance/benchmarks/bm_telco.py --rigorous --affinity=2,3 --output /tmp/tmp8y4mivnp` . telco: Mean +- std dev: 9.29 ms +- 0.19 ms COMPARISON: ### telco ### Mean +- std dev: 9.17 ms +- 0.32 ms -> 9.29 ms +- 0.19 ms: 1.01x slower Not significant -- nosy: +Elvis.Pranskevichus ___ Python tracker <https://bugs.python.org/issue32630> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15873] datetime: add ability to parse RFC 3339 dates and times
Elvis Pranskevichus added the comment: I think that both the pyiso8601 and boxed/iso8601 implementations parse ISO 8601 strings incorrectly. The standard explicitly says that all truncated datetime strings are *reduced accuracy timestamps*. In other words, "2017-10" is *not* equal to "2017-10-01". Instead, "2017-10" represents the whole month of October 2017. Same thing with hours. Earlier versions of ISO 8601 even allowed dropping the year: "--10-01", which meant October 1st of _any year_. They dropped this from more recent revisions of the standard. The only place where the truncated representation means "default to zero" is the timezone offset, so "10:10:00+4" and "10:10:00+04:00" mean the same thing. -- nosy: +Elvis.Pranskevichus ___ Python tracker <https://bugs.python.org/issue15873> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue31681] pkgutil.get_data() leaks open files in Python 2.7
Change by Elvis Pranskevichus : -- keywords: +patch pull_requests: +3854 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue31681> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue31681] pkgutil.get_data() leaks open files in Python 2.7
New submission from Elvis Pranskevichus : pkgutil.get_data() does this: def get_data(self, pathname): return open(pathname, "rb").read() which very obviously leaks open file descriptors. This has been fixed in 3.x by https://github.com/python/cpython/commit/1ab58dfb12dedb7, but never backported to 2.7. -- components: Library (Lib) messages: 303642 nosy: Elvis.Pranskevichus priority: normal severity: normal status: open title: pkgutil.get_data() leaks open files in Python 2.7 type: resource usage versions: Python 2.7 ___ Python tracker <https://bugs.python.org/issue31681> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30972] Event loop incorrectly inherited in child processes.
New submission from Elvis Pranskevichus:
The attached example shows that `asyncio.get_event_loop` still returns parent
process' event loop in some cases. It appears that the fix in issue #29703 was
incomplete:
PARENT PID: 21947, LOOP: <_UnixSelectorEventLoop running=True closed=False
debug=False> at 0x7f0fbe7cfd68
WORKER PID: 21948, LOOP: <_UnixSelectorEventLoop running=True closed=False
debug=False> at 0x7f0fbe7cfd68
concurrent.futures.process._RemoteTraceback:
"""
Traceback (most recent call last):
File "/usr/lib64/python3.6/concurrent/futures/process.py", line 175, in
_process_worker
r = call_item.fn(*call_item.args, **call_item.kwargs)
File "test.py", line 13, in worker
return loop.run_until_complete(worker_coro())
File "/usr/lib64/python3.6/asyncio/base_events.py", line 454, in
run_until_complete
self.run_forever()
File "/usr/lib64/python3.6/asyncio/base_events.py", line 408, in run_forever
raise RuntimeError('This event loop is already running')
RuntimeError: This event loop is already running
"""
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "test.py", line 25, in
loop.run_until_complete(main())
File "/usr/lib64/python3.6/asyncio/base_events.py", line 466, in
run_until_complete
return future.result()
File "test.py", line 21, in main
return await loop.run_in_executor(executor, worker)
RuntimeError: This event loop is already running
--
components: asyncio
files: test.py
messages: 298693
nosy: Elvis.Pranskevichus, yselivanov
priority: normal
severity: normal
status: open
title: Event loop incorrectly inherited in child processes.
type: behavior
versions: Python 3.6
Added file: http://bugs.python.org/file47024/test.py
___
Python tracker
<http://bugs.python.org/issue30972>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28635] Update What's New for 3.6
Elvis Pranskevichus added the comment: I'm pretty sure we're done with What's New for 3.6.0, so, unless it's worth keeping this open for any 3.6.x edits, I'm for closing this. -- ___ Python tracker <http://bugs.python.org/issue28635> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28635] Update What's New for 3.6
Elvis Pranskevichus added the comment: Here's a patch to add opcode changes to the What's New document. Thanks for pointing this out Serhiy. -- Added file: http://bugs.python.org/file45657/0001-Issue-28635-Document-Python-3.6-opcode-changes.patch ___ Python tracker <http://bugs.python.org/issue28635> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28635] Update What's New for 3.6
Elvis Pranskevichus added the comment: On second thought `-VV` isn't really a porting change, so probably a new section under "Build and C API Changes". Something like "Other Improvements". -- ___ Python tracker <http://bugs.python.org/issue28635> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28635] Update What's New for 3.6
Elvis Pranskevichus added the comment: https://docs.python.org/3.6/whatsnew/3.6.html#changes-in-python-command-behavior seems appropriate. -- ___ Python tracker <http://bugs.python.org/issue28635> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28635] Update What's New for 3.6
Elvis Pranskevichus added the comment: Patch with updates attached. Thanks for the feedback guys! -- Added file: http://bugs.python.org/file45474/0001-Issue-28635-what-s-new-in-3.6-add-a-few-more-notes-o.patch ___ Python tracker <http://bugs.python.org/issue28635> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28635] Update What's New for 3.6
Elvis Pranskevichus added the comment: Thanks Serhiy. I removed mentions of things that were indeed fixes backported to 3.5. Other issue references are valid news, including new features to provisional modules backported to 3.5. It is customary to include these in the news for the major release. -- Added file: http://bugs.python.org/file45430/0001-Issue-28635-what-s-new-in-3.6-remove-mentions-of-bac.patch ___ Python tracker <http://bugs.python.org/issue28635> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28635] Update What's New for 3.6
Elvis Pranskevichus added the comment: Attached patch for another pass on what's new. -- ___ Python tracker <http://bugs.python.org/issue28635> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28635] Update What's New for 3.6
Changes by Elvis Pranskevichus : Added file: http://bugs.python.org/file45428/0001-Issue-28635-Fix-a-couple-of-missing-incorrect-versio.patch ___ Python tracker <http://bugs.python.org/issue28635> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28641] Describe PEP 495 features in "What's New in Python 3.6" document
Elvis Pranskevichus added the comment: This should now be covered in #28635. -- ___ Python tracker <http://bugs.python.org/issue28641> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28635] Update What's New for 3.6
Changes by Elvis Pranskevichus : Added file: http://bugs.python.org/file45429/0002-Issue-28635-What-s-New-in-Python-3.6-updates.patch ___ Python tracker <http://bugs.python.org/issue28635> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28635] Update What's New for 3.6
Elvis Pranskevichus added the comment: I'm actually working on a tool that parses Misc/NEWS, cpython and peps repos, and roundup to gather and organize the changes to make the news editor's job easier. -- ___ Python tracker <http://bugs.python.org/issue28635> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28635] Update What's New for 3.6
Elvis Pranskevichus added the comment: The page is a work-in-progress. We'll surely capture all notable changes. -- ___ Python tracker <http://bugs.python.org/issue28635> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28635] Update What's New for 3.6
New submission from Elvis Pranskevichus: Issue to track edits to "What's New in Python 3.6" -- assignee: docs@python components: Documentation files: 0001-Inital-pass-on-What-s-New-in-Python-3.6.patch keywords: patch messages: 280244 nosy: Elvis.Pranskevichus, docs@python, yselivanov priority: normal severity: normal status: open title: Update What's New for 3.6 type: enhancement versions: Python 3.6 Added file: http://bugs.python.org/file45384/0001-Inital-pass-on-What-s-New-in-Python-3.6.patch ___ Python tracker <http://bugs.python.org/issue28635> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28544] Implement asyncio.Task in C
Changes by Elvis Pranskevichus : -- nosy: +Elvis.Pranskevichus ___ Python tracker <http://bugs.python.org/issue28544> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue25082] Editing What's New In Python 3.5
Elvis Pranskevichus added the comment: Larry, it looks like the "Detailed Release Information" link on the release page still points to rc3, which is a 404 now. Also, there doesn't seem to be a link to the "What's new" document, only a Misc/NEWS link. -- ___ Python tracker <http://bugs.python.org/issue25082> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue25082] Editing What's New In Python 3.5
Changes by Elvis Pranskevichus : -- nosy: +Elvis.Pranskevichus ___ Python tracker <http://bugs.python.org/issue25082> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16431] CDecimal disregards subclass passed into __new__ when value argument is an instance of Decimal
New submission from Elvis Pranskevichus:
Consider the following:
import decimal
class MyDecimal(decimal.Decimal):
def __new__(cls, value):
return super().__new__(cls, value)
a = decimal.Decimal('1.0')
b = MyDecimal(a)
c = MyDecimal('1.0')
print(type(a), type(b), isinstance(b, MyDecimal), type(c), isinstance(c,
MyDecimal))
Running the above in 3.3 produces:
False True
Which shows that Decimal.__new__(cls, Decimal()) will always return its
argument regardless of cls.
--
messages: 175121
nosy: Elvis.Pranskevichus, skrah
priority: normal
severity: normal
status: open
title: CDecimal disregards subclass passed into __new__ when value argument is
an instance of Decimal
type: behavior
versions: Python 3.3, Python 3.4
___
Python tracker
<http://bugs.python.org/issue16431>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11674] list(obj), tuple(obj) swallow TypeError (in _PyObject_LengthHint)
Elvis Pranskevichus added the comment: I guess, the best workaround would then be to use a decorator (or a metaclass) and wrap __len__ so that TypeError is caught and wrapped into some other exception. On April 1, 2011 07:10:21 PM Benjamin Peterson wrote: > What?? I certainly hope not. I thought it was supposed to be a performance > hack. __length_hint__ does indeed look like a hack and not a well-defined API. It is also undocumented. -- ___ Python tracker <http://bugs.python.org/issue11674> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11674] list(obj), tuple(obj) swallow TypeError (in _PyObject_LengthHint)
Changes by Elvis Pranskevichus : -- versions: +Python 3.3 ___ Python tracker <http://bugs.python.org/issue11674> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11674] list(obj), tuple(obj) swallow TypeError (in _PyObject_LengthHint)
Changes by Elvis Pranskevichus : -- versions: -Python 2.5, Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3 ___ Python tracker <http://bugs.python.org/issue11674> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11674] list(obj), tuple(obj) swallow TypeError (in _PyObject_LengthHint)
Elvis Pranskevichus added the comment: I think that explicitly raising TypeError in __len__() is wrong in any case. I would argue something like NotImplementedError is a better choice to signal the absence of length. Which also makes me think that Python's exceptions are, maybe, too coarse sometimes. -- versions: +Python 2.5, Python 2.6, Python 2.7, Python 3.1, Python 3.2 ___ Python tracker <http://bugs.python.org/issue11674> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11674] list(obj), tuple(obj) swallow TypeError (in _PyObject_LengthHint)
Elvis Pranskevichus added the comment: The problem is that the call to __len__ is implicit. The Exception is simply swallowed by a list/tuple constructor. The main issue is that the original error is masked which makes it very hard to pinpoint the actual cause of the failure. Here's an example of how it would fail if Test had a rather naive implementation of __getitem__(): >>> class Test: ... def __init__(self): ... self.items = [] ... def __len__(self): ... if not self.items: ... self.items = list(self.calc_items()) ... return len(self.items) ... def __iter__(self): ... return iter(self.items) ... def calc_items(self, number): ... return range(1, number) ... def __getitem__(self, m): ... return list(self)[m] ... >>> t = Test() >>> print(t[0]) Traceback (most recent call last): File "", line 1, in File "", line 13, in __getitem__ IndexError: list index out of range It's not obvious in a trivial synthetic example like that, but in a complex case like ORM abstraction this can cause a lot of pain. Again, I'm not talking about the __len__ and TypeError protocol, it's the implicit exception swallowing by what is essentially an optional optimization hint. Calling len(Test()) directly would bring up the correct trace just fine. -- ___ Python tracker <http://bugs.python.org/issue11674> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11674] list(obj), tuple(obj) swallow TypeError (in _PyObject_LengthHint)
New submission from Elvis Pranskevichus : Consider the following: >>> class Test: ... def __init__(self): ... self.items = [] ... def __len__(self): ... if not self.items: ... self.items = list(self.calc_items()) ... return len(self.items) ... def __iter__(self): ... return iter(self.items) ... def calc_items(self, number): ... return range(1, number) ... >>> l = list(Test()) >>> print(l) [] >>> t = tuple(Test()) >>> print(t) () In the above example calc_items() method is called with a missing argument, which raises TypeError. That TypeError is being wrongly interpreted as "object of type 'Test' has no len()" and is swallowed by _PyObject_LengthHint(). The result is entirely unpredictable as the bug is masked, which is especially annoying for objects that can have a complex call graph under __len__(). Possible solution would be to adjust _PyObject_LengthHint() to rely on some other exception rather than straight TypeError. Swallowing a generic exception like that is bad. -- components: Interpreter Core messages: 132150 nosy: Elvis.Pranskevichus priority: normal severity: normal status: open title: list(obj), tuple(obj) swallow TypeError (in _PyObject_LengthHint) type: behavior versions: Python 2.5, Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3 ___ Python tracker <http://bugs.python.org/issue11674> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5672] Implement a way to change the python process name
Elvis Pranskevichus added the comment: > Please don't provide a wrapper around ptrctrl prctl is not portable. I always thought that the premise of stdlib is to provide portable interfaces. BSD, for example, uses setprocname instead of prctl. Also, prctl does not modify the process name shown in "ps uxww". Here's how PostgreSQL does this: http://tinyurl.com/mhjuqc. -- nosy: +elprans ___ Python tracker <http://bugs.python.org/issue5672> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
