[issue28809] mention asyncio.gather non-deterministic task starting order
New submission from Soren Solari: https://github.com/python/asyncio/issues/432 asyncio.gather documentation states: "the returned future’s result is the list of results (in the order of the original sequence, not necessarily the order of results arrival)" An additional statement like "tasks are not guaranteed to be started in a predicable order" would aid users and slove the discussion in issue 432 above. -- assignee: docs@python components: Documentation messages: 281787 nosy: Soren Solari, docs@python priority: normal severity: normal status: open title: mention asyncio.gather non-deterministic task starting order type: enhancement versions: Python 3.5 ___ Python tracker <http://bugs.python.org/issue28809> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue25913] base64.a85decode adobe flag incorrectly utilizes <~ as a marker causing error
New submission from Soren Solari: According to the PDF Spec http://www.adobe.com/devnet/pdf/pdf_reference.html section 7.4.3, The ascii85decode function only utilizes ~> as an EOD 2byte character, there is no mention of leading <~. Therefore using the base64.a85decode(data, adobe=True) does not work on valid data coming from a pdf because that data may not have a leading <~. Solution: do not require leading <~ for adobe=True. -- messages: 256745 nosy: Soren Solari priority: normal severity: normal status: open title: base64.a85decode adobe flag incorrectly utilizes <~ as a marker causing error type: behavior versions: Python 3.5 ___ Python tracker <http://bugs.python.org/issue25913> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com