[issue32861] urllib.robotparser: incomplete __str__ methods

Serhiy Storchaka added the comment: New changeset bd08a0af2d88c590ede762102bd42da3437e9980 by Serhiy Storchaka (Michael Lazar) in branch 'master': bpo-32861: urllib.robotparser fix incomplete __str__ methods. (GH-5711)

[issue20104] expose posix_spawn(p)

Change by Pablo Galindo Salgado : -- pull_requests: +6479 ___ Python tracker ___ ___

[issue32601] PosixPathTest.test_expanduser fails in NixOS build sandbox

Serhiy Storchaka added the comment: New changeset 5c0d462689e1a69537eaeba6ab94e3ff3524fc31 by Serhiy Storchaka (Anders Kaseorg) in branch 'master': bpo-32601: Let test_expanduser use the same user if no others found. (GH-5246)

[issue32601] PosixPathTest.test_expanduser fails in NixOS build sandbox

Change by miss-islington : -- pull_requests: +6478 ___ Python tracker ___

[issue32601] PosixPathTest.test_expanduser fails in NixOS build sandbox

Change by miss-islington : -- keywords: +patch pull_requests: +6477 stage: -> patch review ___ Python tracker

[issue20104] expose posix_spawn(p)

Pablo Galindo Salgado added the comment: I think that is the biggest argument towards using a tuple: that just setting the priority is not enough (and also is decontextualized as different policies have different priorities). On the other hand one could say that the API

[issue33495] dataclasses: repr of Field objects should use repr of each member

New submission from Eric V. Smith : This is especially true for the "type" member, since it might be a string that looks like a type name (depending on how #33453 is resolved). But repr should be used for all Field members. -- assignee: eric.smith components:

[issue33494] random.choices ought to check that cumulative weights are in ascending order

Steven D'Aprano added the comment: On Mon, May 14, 2018 at 11:54:32AM +, Paul Moore wrote: > Requiring a pre-check on cum_weights (for example, the obvious check > that the sequence is nondecreasing) would add an O(n) step, and so > significantly impact

[issue33494] random.choices ought to check that cumulative weights are in ascending order

Paul Moore added the comment: Supplying cum_weights allows the code to use bisection to locate the correct value to return. This is O(log n), and is significantly faster for large populations than supplying weights (which need to be totalled for the calculation).

[issue33494] random.choices ought to check that cumulative weights are in ascending order

New submission from Steven D'Aprano : As mentioned on the Python-List: https://mail.python.org/pipermail/python-list/2018-May/733061.html random.choices() silently returns the wrong values when cumulative weights are not given, i.e. if the user misreads the

[issue33493] dataclasses: allow keyword-only arguments

New submission from Eric V. Smith : I've had several requests for keyword-only arguments. This is a placeholder to remind me to work on it. I have not decided if it's a good idea or not. I propose adding a keyword_only argument to field(), defaulting to False. I'm thinking

[issue5755] "-Wstrict-prototypes" is valid for Ada/C/ObjC but not for C++"

Change by Jeroen Demeyer : -- pull_requests: +6476 stage: -> patch review ___ Python tracker ___

[issue33481] configparser.write() does not save comments.

Martin Panter added the comment: Looks like Issue 1410680 has a new function to merge comments with new config values (among other things). -- nosy: +martin.panter ___ Python tracker

[issue32393] nav menu jitter in old documentation

Martin Panter added the comment: Maybe related to Issue 24712? -- nosy: +martin.panter ___ Python tracker ___

[issue20104] expose posix_spawn(p)

Martin Panter added the comment: I suggested the “scheduler” tuple to bring the two related parameters (scheduling policy and sched_param) together, similar to how they are paired as the second and third parameters to “os.sched_setscheduler”, and because I thought it

[issue33492] Updating the Evaluation order section to cover *expression in calls

New submission from Martijn Pieters : Can the *Evaluation order* (_evalorder) section in reference/expressions.rst please be updated to cover this exception in a *call* primary (quoting from the _calls section): A consequence of this is that although the ``*expression``

[issue5755] "-Wstrict-prototypes" is valid for Ada/C/ObjC but not for C++"

Change by Jeroen Demeyer : -- nosy: +jdemeyer ___ Python tracker ___ ___ Python-bugs-list

[issue33491] mistype of method's name

New submission from Ivan Gushchin : This link https://docs.python.org/2/library/unittest.html#unittest.SkipTest names method from Capital letter. At the same time method name (according to help(unittest) ) is skipTest (starting lowercase). For those who reads

<    1   2   3