Mailman 3 July 2016 - docs

ePUB Python 3 docs
by Haug Hogne 08 Jul '16

08 Jul '16

Hi! Just for your information. I'm sorry I have misunderstood anything, but it seems the Python 3.5.2 ePUB documentation linked to from https://docs.python.org/3/download.html is a zip containing the HTML documentation? Yours sincerely, Hogne Haug

1 0

[issue27269] ipaddress: Wrong behavior with ::ffff:1.2.3.4 style IPs
by Марк Коренберг 08 Jul '16

08 Jul '16

Марк Коренберг added the comment: Also, it should be marked explicitly, if cross-type lookup is safe. I mean code like that: some_net = ipaddress.ip_network(some_input1) some_addr = ipaddress.ip_address(some_input2) return some_addr in some_net Is it safe to write such code? Docs say: 21.28.2.3. Operators Address objects support some operators. Unless stated otherwise, operators can only be applied between compatible objects (i.e. IPv4 with IPv4, IPv6 with IPv6). 1. It is not said if exception will be raised if incompatible objects are used, and not said if result is defined. 2. "Unless stated otherwise" - Seem it is stated nowhere. ---------- assignee: -> docs@python components: +Documentation nosy: +docs@python _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue27269> _______________________________________

1 0

[issue27464] Document that SplitResult & friends are namedtuples
by SilentGhost 08 Jul '16

08 Jul '16

Changes by SilentGhost <ghost.adh(a)runbox.com>: ---------- assignee: -> docs@python components: +Documentation nosy: +docs@python stage: -> needs patch versions: +Python 3.5, Python 3.6 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue27464> _______________________________________

1 0

[issue27467] distutils.config API different between <=3.5.1 and 3.5.2
by Berker Peksag 08 Jul '16

08 Jul '16

Berker Peksag added the comment: I was thinking to document issue 20120 in Misc/NEWS. It turns out I was looking at the wrong commit and it was already documented in eae59b6bf133. ---------- resolution: -> not a bug stage: needs patch -> resolved status: open -> closed _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue27467> _______________________________________

1 0

[issue27467] distutils.config API different between <=3.5.1 and 3.5.2
by Xiang Zhang 08 Jul '16

08 Jul '16

Xiang Zhang added the comment: Berker, what doc needs to be changed? Although RawConfigParser is legacy but that does not mean it's deprecated, right? We can still use it although the doc suggests us use ConfigParser. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue27467> _______________________________________

1 0

[issue27467] distutils.config API different between <=3.5.1 and 3.5.2
by Berker Peksag 08 Jul '16

08 Jul '16

Berker Peksag added the comment: Thanks for the report. Yes, the RawConfigParser change was intentional and it was discussed in issue 20120. I'm marking this as a documentation issue. ---------- assignee: -> docs@python components: +Documentation nosy: +berker.peksag, docs@python stage: -> needs patch versions: +Python 3.6 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue27467> _______________________________________

1 0

[issue27422] Deadlock when mixing threading and multiprocessing
by R. David Murray 05 Jul '16

05 Jul '16

R. David Murray added the comment: Heh, yeah. What I was really trying to do by that comment was clarify for any *other* readers that stumble on this issue later it is just the python code that *has* to be constrained by the GIL. I have no idea how much of the scipy stack drops the gil at strategic spots. I do seem to remember that the the Jupyter uses multiple processes for its parallelism, though. Anyway, this is pretty off topic now :) ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue27422> _______________________________________

1 0

NAMEING python
by Suresh Babu 05 Jul '16

05 Jul '16

Hi Guido Cpython is good easy to understand. Please change the names of other pythons like. JPython for java python NPython for .net python Python for original python without classes with regards, sureshbk.

1 0

[issue27422] Deadlock when mixing threading and multiprocessing
by Davin Potts 04 Jul '16

04 Jul '16

Changes by Davin Potts <python(a)discontinuity.net>: ---------- stage: -> resolved status: open -> closed _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue27422> _______________________________________

1 0

[issue27422] Deadlock when mixing threading and multiprocessing
by Davin Potts 04 Jul '16

04 Jul '16

Davin Potts added the comment: @r.david.murray: Oh man, I was not going to go as far as advocate dropping the GIL. :) At least not in situations like this where the exploitable parallelism is meant to be at the Python level and not inside the Fortran code (or that was my understanding of the setup). Martin had already mentioned the motivation to fork to avoid side effects possibly arising somewhere in that code. In practice, after dropping the GIL the threads will likely use multiple of the cores -- though that's up to the OS kernel scheduler, that's what I've observed happening after temporarily dropping the GIL on both Windows and Linux systems. As to the benefit of CPU affinity, it depends -- it depends upon what my code was and what the OS and other system processes were busily doing at the time my code ran -- but I've never seen it hurt performance (even if the help was diminishingly small at times). For certain situations, it has been worth doing. Correction: I have seen cpu affinity hurt performance when I make a bone-headed mistake and constrain too many things onto too few cores. But that's a PEBCAK root cause. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue27422> _______________________________________

1 0