[issue24509] Undocumented features of asyncio: call_at, call_later

Changes by Марк Коренберг socketp...@gmail.com: -- assignee: - docs@python components: +Documentation, asyncio nosy: +docs@python, gvanrossum, haypo, yselivanov type: - enhancement ___ Python tracker rep...@bugs.python.org

[issue24509] Undocumented features of asyncio: call_at, call_later

New submission from Марк Коренберг: These function returns handle, so, registered callback can be cancelled. -- messages: 245803 nosy: mmarkk priority: normal severity: normal status: open title: Undocumented features of asyncio: call_at, call_later versions: Python 3.6

[issue24509] Undocumented features of asyncio: call_at, call_later

STINNER Victor added the comment: Documentatin of call_soon() and call_later() contain the sentence An instance of asyncio.Handle is returned. with a link to Handle which shows the cancel() method: https://docs.python.org/dev/library/asyncio-eventloop.html#asyncio.BaseEventLoop.call_soon

[issue23684] urlparse() documentation does not account for default scheme

Berker Peksag added the comment: Thanks Martin. -- resolution: - fixed stage: commit review - resolved status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23684 ___

[issue24496] Non-idiomatic examples in gzip docs

Roundup Robot added the comment: New changeset 10eea15880db by Berker Peksag in branch '2.7': Issue #24496: Backport gzip examples to Python 2. https://hg.python.org/cpython/rev/10eea15880db -- nosy: +python-dev ___ Python tracker

[issue19065] sqlite3 timestamp adapter chokes on timezones

Jacques-D. Piguet added the comment: I just hit the problem in Python 2.7. The patch given here is not applicable due to missing class datetime.timezone in Python before 3.2. Question 1: when will the patch be applied in Python 3? Question 2: any chance to get a solution in Python 2?

[issue24508] Backport 3.5's Windows build project files to 2.7

Steve Dower added the comment: I'll try out the changes when I get a bit of time today or tomorrow and decide then what I'll do. msi.py doesn't actually build the projects AFAIK, so it's probably okay. It might try to read them to get paths though. --

[issue24503] csv.writer fails when within csv.reader

Skip Montanaro added the comment: @ezzieyguywuf - Can you provide an example of a non-empty input.csv which fails for you? Otherwise, I'd have to agree with @josh.r and @vadmium that it's working as it should. -- nosy: +skip.montanaro ___ Python

[issue19111] 2to3 should remove from future_builtins import *

Josh Rosenberg added the comment: Ah, my mistake. Apologies. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19111 ___ ___ Python-bugs-list

[issue18857] urlencode of a None value uses the string 'None'

R. David Murray added the comment: I see no reason for this issue to be open. As suggested on the linked bug, the value should be passed as an empty string (which will produce, eg foo=a='1', which is the correct format for such a parameter. Unless someone can point to a real web server that

[issue9377] socket, PEP 383: Mishandling of non-ASCII bytes in host/domain names

David Watson added the comment: I've updated the ASCII/surrogateescape patches in line with various changes to Python since I posted them. return-ascii-surrogateescape-2015-06-25.diff incorporates the ascii-surrogateescape and uname-surrogateescape patches, and

[issue23684] urlparse() documentation does not account for default scheme

Roundup Robot added the comment: New changeset 368db4b1ced9 by Berker Peksag in branch '3.4': Issue #23684: Clarify the return value of the scheme attribute of ParseResult and SplitResult objects. https://hg.python.org/cpython/rev/368db4b1ced9 New changeset 68629ebe0fee by Berker Peksag in

[issue23684] urlparse() documentation does not account for default scheme

Roundup Robot added the comment: New changeset 7bf9e10fc32f by Berker Peksag in branch '2.7': Issue #23684: Clarify the return value of the scheme attribute of ParseResult and SplitResult objects. https://hg.python.org/cpython/rev/7bf9e10fc32f --

[issue24496] Non-idiomatic examples in gzip docs

Berker Peksag added the comment: Thanks for the patch, Jakub. I've updated the patch to match ae1528beae67 (thanks Martin) and commit it. -- nosy: +berker.peksag resolution: - fixed stage: - resolved status: open - closed ___ Python tracker

[issue24511] Add methods for async protocols

Changes by Arc Riley arcri...@gmail.com: -- nosy: +ArcRiley ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24511 ___ ___ Python-bugs-list mailing

[issue24483] Avoid repeated hash calculation in C implementation of functools.lru_cache()

Meador Inge added the comment: I did some regression testing and reviewed the code; LGTM. As for the code structure issues, I agree that the duplication is undesirable (the readability argument is not that convincing), but Serhiy's patch is consistent with the existing design. As such, I

[issue24439] Feedback for awaitable coroutine documentation

Yury Selivanov added the comment: Martin, it's now updated. (As for why it wasn't applied in the first place, I guess standard MacOS `patch` command fails to apply git binary diffs) -- ___ Python tracker rep...@bugs.python.org

[issue24484] multiprocessing cleanup occasionally throws exception

Jorge Herskovic added the comment: Ok, I *think* I tracked it down to Connections getting cleaned up in a non-orderly fashion, sometimes while _run_finalizers is executing. The following patch to lib/python3.4/multiprocessing/connection.py cures the problem on my machine. @@ -124,10 +124,10

[issue24510] Make _PyCoro_GetAwaitableIter a public API

New submission from Yury Selivanov: We should consider making _PyCoro_GetAwaitableIter(o) a public API. Its implementation isn't trivial because it's not around simply accessing 'tp_as_async-am_await'. You also need to check is 'o' is a generator with a CO_ITERABLE_COROUTINE or a CoroObject,

[issue18857] urlencode of a None value uses the string 'None'

Piotr Dobrogost added the comment: This problem came out in the bug Cannot make URL query string with a parameter without a value (https://github.com/kennethreitz/requests/issues/2651) raised in urllib3 project (which itself is being used by Requests library mentioned in this bug).

[issue24439] Feedback for awaitable coroutine documentation

Roundup Robot added the comment: New changeset e9c34e16f445 by Yury Selivanov in branch '3.5': Issue #24439: Update tulip_coro.dia https://hg.python.org/cpython/rev/e9c34e16f445 New changeset 15b8a62da6ff by Yury Selivanov in branch 'default': Merge 3.5 (Issue #24439)

[issue24511] Add methods for async protocols

Changes by Yury Selivanov yseliva...@gmail.com: -- type: - enhancement ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24511 ___ ___

[issue24511] Add methods for async protocols

New submission from Yury Selivanov: Let's consider adding C API functions for working with new tp_as_async: PyAwait_Check for checking tp_as_async-am_await || PyCoro_Check || PyGen CO_ITERABLE_COROUTINE PyAwait_AsyncIterCheck for checking tp_as_async-am_iter PyAwait_GetAsyncIter for calling

[issue24510] Make _PyCoro_GetAwaitableIter a public API

STINNER Victor added the comment: It looks like the code is currently moving fast. I suggest to wait until Python 3.6 to stabilize the Python C API for async/await. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24510

[issue24425] Installer Vender Issue

John Laurence Poole added the comment: I attempted to install on Windows Server 2008 R2 Service Pack 1 and had the same problems. I thought it might be proxy since I'm behind a firewall, but setting the usual values did not allow the program to overcome whatever it is that PIP is having

[issue24510] Make _PyCoro_GetAwaitableIter a public API

Yury Selivanov added the comment: It looks like the code is currently moving fast. [..] Yeah, that's my feeling too, I don't want to rush things too much. Unless Guido, Nick and you are in complete agreement that we need this, we should postpone till 3.6. --

[issue16379] SQLite error code not exposed to python

Cal Leeming added the comment: Any update on this? Still seems to be a problem as of 3.4.0. -- nosy: +sleepycal ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16379 ___

[issue24507] CRLF issues

Eric V. Smith added the comment: At least for the files in decimaltestdata, I'd be wary about changing them. My understanding is that these files are from the IBM decimal test library. I don't think we should stray from upstream here, even for something as simple as line endings.

[issue16379] SQLite error code not exposed to python

Changes by Ivan Levkivskyi levkivs...@gmail.com: -- nosy: +levkivskyi ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16379 ___ ___ Python-bugs-list

[issue24509] Undocumented features of asyncio: call_at, call_later

Roundup Robot added the comment: New changeset 3199ec504dbe by Yury Selivanov in branch '3.4': Issue #24509: Clarify Handle.cancel() and loop.call_* methods. https://hg.python.org/cpython/rev/3199ec504dbe New changeset fc69dd6aea55 by Yury Selivanov in branch '3.5': Merge 3.4 (issue #24509)

[issue24512] multiprocessing should log a warning when forking multithreaded process

New submission from Timothy Cardenas: We were tracking down a bug the other day that was rather hard to find involving a forking a process that had both a primary thread and a logging thread. The docs clearly state that forking a multithreaded process is problematic

[issue24507] CRLF issues

Rusi added the comment: The newest (at least newer) version seems to be http://speleotrove.com/decimal/ Top of page says: Welcome to the General Decimal Arithmetic website, which is now hosted at speleotrove.com. The page and file names here have not been changed from the names used on the

[issue24509] Undocumented features of asyncio: call_at, call_later

Yury Selivanov added the comment: Thanks for reporting this Mark! -- resolution: - fixed stage: - commit review status: open - closed versions: +Python 3.4, Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24509

[issue20387] tokenize/untokenize roundtrip fails with tabs

Jason R. Coombs added the comment: @gumblex, I've applied your updated patch (though I couldn't figure out why it wouldn't apply mechanically; I had to paste it). I also corrected the test. Thanks for the advice on that. I don't understand the second half of your message. Are you stating

[issue24513] decimal test version mismatch

New submission from Rusi: In http://bugs.python.org/issue24507 there was an apprehension about changing the decimal test versions. Poking around I find that the versions in headers of files in Lib/test/decimaltestdata refer to version 2.59 and the IBM link http://www2.hursley.ibm.com/decimal

[issue23883] __all__ lists are incomplete

Martin Panter added the comment: Jacek: If we used the ModuleType check, and somebody adds a module-level constant (like logging.CRITICAL = 50), the test will automatically detect if they forget to update __all__. That is what I meant by the test being stricter. But it looks like you went for

[issue24294] DeprecationWarnings should be visible by default in the interactive REPL

Nathaniel Smith added the comment: Ping. I know this is pretty trivial and everyone's focused on 3.5-related stuff, but it would be nice to get this finalized soon b/c the sooner CPython commits to some standard behavior here, the sooner all the other (faster-moving) python REPLs will

[issue24509] Undocumented features of asyncio: call_at, call_later

Марк Коренберг added the comment: For delayed execution methods: Returned handle is actually timer object. That timer can be deactivated using asyncio.Handle.cancel() method, so registered callback won't be called. For other callback registration methods: Returned handle may be used to