[issue34505] urllib2 fails for proxy credentials that contains a '/' character

New submission from Balibax : How can solve thishttps://www.pinterest.com/CoreTricks/;>? -- components: Build messages: 324111 nosy: Balibax5445 priority: normal severity: normal status: open title: urllib2 fails for proxy credentials that contains a '/' character type: crash

[issue34443] enum repr should use __qualname__

Michał Radwański added the comment: Serhiy, would it be ok to put '__module__' + '.' + __qualname__ here? -- nosy: +enedil ___ Python tracker ___

[issue34504] PySequence_Check: argument is dereferenced and then checked for NULL

miss-islington added the comment: New changeset d60bdf239e322316c8b5e37679cb8e789028aae2 by Miss Islington (bot) in branch '3.6': closes bpo-34504: Remove the useless NULL check in PySequence_Check(). (GH-8935) https://github.com/python/cpython/commit/d60bdf239e322316c8b5e37679cb8e789028aae2

[issue34504] PySequence_Check: argument is dereferenced and then checked for NULL

miss-islington added the comment: New changeset d6725fcdd54cb3c72201eaa8841dd72d84f5f71d by Miss Islington (bot) in branch '3.7': closes bpo-34504: Remove the useless NULL check in PySequence_Check(). (GH-8935) https://github.com/python/cpython/commit/d6725fcdd54cb3c72201eaa8841dd72d84f5f71d

[issue34504] PySequence_Check: argument is dereferenced and then checked for NULL

Change by miss-islington : -- pull_requests: +8409 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34504] PySequence_Check: argument is dereferenced and then checked for NULL

Change by miss-islington : -- pull_requests: +8408 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34504] PySequence_Check: argument is dereferenced and then checked for NULL

Benjamin Peterson added the comment: New changeset b57b4ac042b977e0b42a2f5ddb30ca7edffacfa9 by Benjamin Peterson (Alexey Izbyshev) in branch 'master': closes bpo-34504: Remove the useless NULL check in PySequence_Check(). (GH-8935)

[issue34306] minidom: wrong processing of xmlns attributes

Victor Porton added the comment: My bug report was wrong: https://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/core.html In the DOM, all namespace declaration attributes are by definition bound to the namespace URI: "http://www.w3.org/2000/xmlns/;. These are the attributes whose

[issue34483] eval() raises NameError: name '...' is not defined

Eric V. Smith added the comment: I'll close this. I'm still reviewing the docs on it, and I might open a documentation issue once I understand it better. -- resolution: -> not a bug stage: -> resolved status: open -> closed type: -> behavior

[issue34483] eval() raises NameError: name '...' is not defined

Alex added the comment: Eric, thank you for the clarification. Do you want me to close the ticket? -- ___ Python tracker ___ ___

[issue34334] QueueHandler logs exc_info twice

Vinay Sajip added the comment: Possibly a test needs to be added for this, as it appears to be a regression that went unnoticed. -- ___ Python tracker ___

[issue34334] QueueHandler logs exc_info twice

Vinay Sajip added the comment: > Patching QueueHandler.prepare() to set exc_text to None seems to fix this. I'm not sure that's the right fix. The change appears to have come from this commit: https://github.com/python/cpython/commit/adfe3440f65dfd6cf4463db6cd02cdc78e77ce17 Specifically,

[issue34504] PySequence_Check: argument is dereferenced and then checked for NULL

Change by Alexey Izbyshev : -- keywords: +patch pull_requests: +8407 stage: -> patch review ___ Python tracker ___ ___

[issue34504] PySequence_Check: argument is dereferenced and then checked for NULL

New submission from Alexey Izbyshev : The argument of PySequence_Check() is dereferenced at https://github.com/python/cpython/blob/5f79b50763d687aeeed8edcb4efcc7ac9f8fa186/Objects/abstract.c#L1511 and then checked for NULL. Reported by Svace static analyzer. Since other PySomething_Check()

[issue34403] test_utf8_mode.test_cmd_line() fails on HP-UX due to false assumptions

Michael Osipov <1983-01...@gmx.net> added the comment: I think you are absoltely right. > In any case, it seems to be broken for any system that does not have UTF-8 as > default. You likely mean ASCII. Python assumes that LANG=C is ASCII which is not the case for AIX and HP-UX. Your patch

[issue34503] Reference leak in PyErr_SetObject()

Change by Alexey Izbyshev : -- keywords: +patch pull_requests: +8406 stage: -> patch review ___ Python tracker ___ ___

[issue34494] simple "sequence" class ignoring __len__

Change by Raymond Hettinger : -- assignee: -> rhettinger nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing

[issue34503] Reference leak in PyErr_SetObject()

New submission from Alexey Izbyshev : 'exc_value' reference is leaked at https://github.com/python/cpython/blob/5f79b50763d687aeeed8edcb4efcc7ac9f8fa186/Python/errors.c#L113 -- components: Interpreter Core messages: 324099 nosy: benjamin.peterson, berker.peksag, izbyshev,

[issue14465] xml.etree.ElementTree: add feature to prettify XML output

Raymond Hettinger added the comment: A few more thoughts for consideration: * We already have a toprettyxml() tool in the minidom package. * Since whitespace is significant in XML, prettifying changes the content and meaning, so it doesn't round-trip and should only be used for debugging

[issue34347] AIX: test_utf8_mode.test_cmd_line fails

Michael Osipov <1983-01...@gmx.net> added the comment: This is a very thorough analysis. Kudos to that. -- nosy: +michael-o ___ Python tracker ___

[issue23325] Turn SIG_DFL and SIG_IGN into functions

Xiang Zhang added the comment: I miss that. So this change seems to be user transparent and make more sense then. -- nosy: +vstinner ___ Python tracker ___

[issue11190] test_locale error on AIX

Michael Felt added the comment: FYI - this test passes on Python3.X and Python3.7 bots, still fails on Python2.7 In short "fixed" for Python3. -- components: +Tests ___ Python tracker

[issue14465] xml.etree.ElementTree: add feature to prettify XML output

Change by Matej Cepl : -- pull_requests: +8405 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34501] PyType_FromSpecWithBases: spec->name is dereferenced before checking for NULL

miss-islington added the comment: New changeset 323a91bb3a2b5639637efc517fe3f30d3bc288e2 by Miss Islington (bot) in branch '3.6': closes bpo-34501: PyType_FromSpecWithBases: Check spec->name before dereferencing it. (GH-8930)

[issue34501] PyType_FromSpecWithBases: spec->name is dereferenced before checking for NULL

miss-islington added the comment: New changeset 15dadacabf6a1c62e9920b6a42ff8936ea1830f8 by Miss Islington (bot) in branch '3.7': closes bpo-34501: PyType_FromSpecWithBases: Check spec->name before dereferencing it. (GH-8930)

[issue34501] PyType_FromSpecWithBases: spec->name is dereferenced before checking for NULL

Change by miss-islington : -- pull_requests: +8404 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34501] PyType_FromSpecWithBases: spec->name is dereferenced before checking for NULL

Change by miss-islington : -- pull_requests: +8403 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34501] PyType_FromSpecWithBases: spec->name is dereferenced before checking for NULL

Benjamin Peterson added the comment: New changeset 5f79b50763d687aeeed8edcb4efcc7ac9f8fa186 by Benjamin Peterson (Alexey Izbyshev) in branch 'master': closes bpo-34501: PyType_FromSpecWithBases: Check spec->name before dereferencing it. (GH-8930)

[issue34501] PyType_FromSpecWithBases: spec->name is dereferenced before checking for NULL

Alexey Izbyshev added the comment: @enedil It seems that all later check either set a message or simply propagate the error set by a called function. Did you mean any specific later check? -- ___ Python tracker

[issue34501] PyType_FromSpecWithBases: spec->name is dereferenced before checking for NULL

Change by Alexey Izbyshev : -- keywords: +patch pull_requests: +8402 stage: -> patch review ___ Python tracker ___ ___

[issue34501] PyType_FromSpecWithBases: spec->name is dereferenced before checking for NULL

Michał Radwański added the comment: But if the error message is set, then for consistency, it should be also the case that the later checks set some kind of error message. -- nosy: +enedil ___ Python tracker

[issue34502] Docs of sys.exit() mention utf8_mode for an unclear reason

miss-islington added the comment: New changeset 42a1ca65d00ba59fe63cc65df0ff297a885e61b8 by Miss Islington (bot) in branch '3.7': closes bpo-34502: Remove a note about utf8_mode from sys.exit() docs. (GH-8928) https://github.com/python/cpython/commit/42a1ca65d00ba59fe63cc65df0ff297a885e61b8

[issue34501] PyType_FromSpecWithBases: spec->name is dereferenced before checking for NULL

Benjamin Peterson added the comment: Your suggested fix seems fine to me. -- nosy: +benjamin.peterson ___ Python tracker ___ ___

[issue34502] Docs of sys.exit() mention utf8_mode for an unclear reason

Change by miss-islington : -- pull_requests: +8401 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34502] Docs of sys.exit() mention utf8_mode for an unclear reason

Benjamin Peterson added the comment: New changeset 44838be9f79870ff3c9e04b7398a1dc3d56d53ed by Benjamin Peterson (Alexey Izbyshev) in branch 'master': closes bpo-34502: Remove a note about utf8_mode from sys.exit() docs. (GH-8928)

[issue34502] Docs of sys.exit() mention utf8_mode for an unclear reason

Change by Alexey Izbyshev : -- keywords: +patch pull_requests: +8400 stage: -> patch review ___ Python tracker ___ ___

[issue34502] Docs of sys.exit() mention utf8_mode for an unclear reason

New submission from Alexey Izbyshev : Docs for sys.exit() contain the following note added in https://github.com/python/cpython/blame/1871a4a35123b278443b960255cb14314ce196f6/Doc/library/sys.rst#L336 Changed in version 3.7: Added utf8_mode attribute for the new -X utf8 flag. Does it belong

[issue33569] dataclasses InitVar does not maintain any type info

Change by Augusto Hack : -- keywords: +patch pull_requests: +8399 stage: -> patch review ___ Python tracker ___ ___

[issue23325] Turn SIG_DFL and SIG_IGN into functions

Serhiy Storchaka added the comment: Numerical values of signal numbers are standardized. signal.signal(15, handler) is valid. SIGTERM is just a handy name for the constant 15. But SIG_DFL and SIG_IGN are not integers in C (they are special pointers), and it is not declared anywhere that

[issue34403] test_utf8_mode.test_cmd_line() fails on HP-UX due to false assumptions

Michael Felt added the comment: As the AIX complaint is (was once the PR merges): AssertionError: "['h\\xc3\\xa9\\xe2\\x82\\xac']" != "['h\\udcc3\\udca9\\udce2\\udc82\\udcac']" - ['h\xc3\xa9\xe2\x82\xac'] + ['h\udcc3\udca9\udce2\udc82\udcac'] And the HP-UX complaint is: File

[issue32968] Fraction modulo infinity should behave consistently with other numbers

Change by Mark Dickinson : -- assignee: -> mark.dickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34494] simple "sequence" class ignoring __len__

Eric Wieser added the comment: What I think I find surprising is that I'd expect the sequence protocol to be defined by `__getitem__` and `__len__`, and for `__iter__` to be inferred as: def __iter__(self): for i in range(len(self)): yield self[i] But in reality it

[issue34498] Python 3.7 breaks on singledispatch_function.register(pseudo_type), which Python 3.6 accepted

Ivan Levkivskyi added the comment: This is why we have 4 months of betas :-) On one hand making objects in `typing` module not classes was intentional, but on another hand this use case looks totally fine. I would say we could update the check in `functools` to accept more things. I am

[issue34498] Python 3.7 breaks on singledispatch_function.register(pseudo_type), which Python 3.6 accepted

Change by Serhiy Storchaka : -- nosy: +gvanrossum, levkivskyi ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34494] simple "sequence" class ignoring __len__

Change by Eric Wieser : -- nosy: +Eric.Wieser ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue32968] Fraction modulo infinity should behave consistently with other numbers

Change by Mark Dickinson : -- versions: -Python 3.6, Python 3.7 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue34498] Python 3.7 breaks on singledispatch_function.register(pseudo_type), which Python 3.6 accepted

Michał Radwański added the comment: The change is not only in the added `isinstance` check: ~ $ python3.6 -q >>> import typing >>> isinstance(typing.Sequence, type) True >>> ~ $ python3.7 -q >>> import typing >>> isinstance(typing.Sequence, type) False >>> -- nosy: +enedil

[issue32968] Fraction modulo infinity should behave consistently with other numbers

Mark Dickinson added the comment: Sorry that I've taken so long to get back to this. I've just updated the PR, and I think it's ready to go. Looks like it does need you to update your GitHub username here in the "Your Details" section of the bugtracker, though; sorry about that. > If we

[issue34492] Python/coreconfig.c: Fix _Py_wstrlist_copy()

STINNER Victor added the comment: New changeset 388bd4bd7622f6781260ed388f7c76b673adb0e1 by Victor Stinner (Alexey Izbyshev) in branch '3.7': [3.7] bpo-34492: Modules/main.c: Fix copy_wstrlist() (GH-8910) (GH-8922)

[issue34492] Python/coreconfig.c: Fix _Py_wstrlist_copy()

STINNER Victor added the comment: Thanks Alexey Izbyshev for the bug report and the fix for 3.7 and master branches! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue32973] Importing the same extension module under multiple names breaks non-reinitialisable extension modules

Stefan Behnel added the comment: FYI, I've updated Cython's module import checks to include an interpreter check. This (multi-file) test shows the new behaviour, which is to raise an ImportError on module creation when it detects a different interpreter than during the initial import:

[issue34453] ipaddress module accepts some strange IPv6 addresses that it shouldn't

Michał Radwański added the comment: The point is that the specification is not complete and thus left for the implementations to decide. Python's version hits the sweet spot between inclusive and correct - as long as a version is unambiguous, it is accepted. --

[issue23325] Turn SIG_DFL and SIG_IGN into functions

Xiang Zhang added the comment: I'm afraid this could break old codes so not sure it's worth or not. I've seen code like `SIGTERM = 15; signal.signal(SIGTERM, handler)`. I won't be surprised to see a handcraft SIG_DFL/IGN. -- nosy: +xiang.zhang versions: +Python 3.8 -Python 3.5

[issue34171] Lib/trace.cover not removed by the clean target

Zachary Ware added the comment: No, there isn't. However, https://github.com/python/buildmaster-config/pull/43 should help; I'll try to get that deployed later today. -- ___ Python tracker

[issue34501] PyType_FromSpecWithBases: spec->name is dereferenced before checking for NULL

New submission from Alexey Izbyshev : In the following snippet from PyType_FromSpecWithBases() in Objects/typeobject.c, spec->name is dereferenced by strrchr() but then is checked for NULL: /* Set the type name and qualname */ s = strrchr(spec->name, '.'); if (s == NULL)

[issue34500] Fix ResourceWarning in difflib.py

Mickaël Schoentgen added the comment: This is a little patch to mostly keep aligned with https://github.com/google/python-fire/pull/135. -- ___ Python tracker ___

[issue34500] Fix ResourceWarning in difflib.py

Change by Mickaël Schoentgen : -- keywords: +patch pull_requests: +8397 stage: -> patch review ___ Python tracker ___ ___

[issue34500] Fix ResourceWarning in difflib.py

New submission from Mickaël Schoentgen : Fix 2 unclosed files in the documentation and the difflib.py script: diff.py:77: ResourceWarning: unclosed file <_io.TextIOWrapper name='/tmp/tmpnby8pemn' mode='U' encoding='UTF-8'> fromlines = open(fromfile, 'U').readlines() diff.py:78:

[issue34403] test_utf8_mode.test_cmd_line() fails on HP-UX due to false assumptions

Michael Felt added the comment: It might be as simple as what I saw for AIX: diff --git a/Lib/test/test_utf8_mode.py b/Lib/test/test_utf8_mode.py index 26e2e13ec5..3e918fd54c 100644 --- a/Lib/test/test_utf8_mode.py +++ b/Lib/test/test_utf8_mode.py @@ -219,6 +219,8 @@ class

[issue32973] Importing the same extension module under multiple names breaks non-reinitialisable extension modules

Stefan Behnel added the comment: Well, first of all, it's better than a crash. :) Secondly, I'm sure NumPy doesn't currently support subinterpreters, just like most other extension modules. If I'm not mistaken, an interpreter switch can be detected through the interpreter state pointer [1]

[issue32973] Importing the same extension module under multiple names breaks non-reinitialisable extension modules

Petr Viktorin added the comment: That's quite problematic, since then you're sharing a mutable object across interpreters. The user can store any attribute on module objects, including e.g. Python functions that reference their original interpreter's global state, but become callable in

[issue34347] AIX: test_utf8_mode.test_cmd_line fails

Michael Felt added the comment: Solution much simpler than I thought: not arg.decode('ascii', 'surrogateescape'), but arg.decode('iso-8859-1') -- ___ Python tracker ___

[issue34347] AIX: test_utf8_mode.test_cmd_line fails

Change by Michael Felt : -- keywords: +patch pull_requests: +8396 stage: -> patch review ___ Python tracker ___ ___

[issue32973] Importing the same extension module under multiple names breaks non-reinitialisable extension modules

Stefan Behnel added the comment: I think the best work-around for now is to implement a bit of PEP 489, including a module create function that always returns the same static module reference instead of creating a new one after the first call, and a module exec function that simply returns

[issue34492] Python/coreconfig.c: Fix _Py_wstrlist_copy()

Change by Alexey Izbyshev : -- title: Python/coreconfig.c: Missing NULL check in _Py_wstrlist_copy() -> Python/coreconfig.c: Fix _Py_wstrlist_copy() ___ Python tracker ___

[issue34492] Python/coreconfig.c: Missing NULL check in _Py_wstrlist_copy()

Change by Alexey Izbyshev : -- versions: +Python 3.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34171] Lib/trace.cover not removed by the clean target

Pablo Galindo Salgado added the comment: @zach.ware Is there a way to clean the workspace of these buildbots programmatically/from the UI? I can do it myself if you tell me how it must be done. -- nosy: +zach.ware ___ Python tracker

[issue34171] Lib/trace.cover not removed by the clean target

Serhiy Storchaka added the comment: Seems this is a temporary issue. Tests are failed due to trace.cover files left from previous runs. Recreating the working space from zero should fix the issue, but I don't know how to do this on all buildbots. --

[issue34492] Python/coreconfig.c: Missing NULL check in _Py_wstrlist_copy()

Change by Alexey Izbyshev : -- pull_requests: +8395 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34499] Extend registering of single-dispatch functions to parametrized generic pseudo-types

New submission from Dutcho : While issue #34498 signalled a break in Python 3.7 of legal Python 3.6 code that registers a single-dispatch function with a 'pseudo-type' like typing.Sequence, both Python 3.6 and Python 3.7 don't work with a 'parametrized pseudo-type' like typing.Sequence[int].

[issue34171] Lib/trace.cover not removed by the clean target

Pablo Galindo Salgado added the comment: Several buildbots are failing due to commit c406d5cd74002964a64c3eb7d9e2445a7fd3a03f: https://buildbot.python.org/all/#/builders/40/builds/709 https://buildbot.python.org/all/#/builders/21/builds/1459

[issue34497] Remove needless set operator restriction

Change by Xiang Zhang : -- nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34498] Python 3.7 breaks on singledispatch_function.register(pseudo_type), which Python 3.6 accepted

New submission from Dutcho : In Python 3.6, the argument to the register() method of a single-dispatch function (i.e. a function decorated by @functools.singledispatch) can be a 'type-like' class (pseudo-type?) from e.g. the typing module that supports isinstance(). The below demonstrates

[issue34497] Remove needless set operator restriction

Change by Dan Snider : -- keywords: +patch pull_requests: +8394 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list

[issue34497] Remove needless set operator restriction

New submission from Dan Snider : I only just now realized that `dict.fromkeys('abc').keys() - 'bc'` returns {'a'} instead of raising an error like {*'abc'} - 'bc' would, which is really quite handy. The __xor__, __and__, and __sub__ methods of dict_keys (and items, assuming no there are no

[issue34395] memory leaks in error handling in csv and pickle modules

Serhiy Storchaka added the comment: Thank you for your report and fix Sergey. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue34395] memory leaks in error handling in csv and pickle modules

Serhiy Storchaka added the comment: New changeset 90555eca44a19c743d39b7fd2e05f7bc37fb5cb8 by Serhiy Storchaka (Sergey Fedoseev) in branch 'master': bpo-34395: Don't free allocated memory on realloc fail in load_mark() in _pickle.c. (GH-8788)

[issue23325] Turn SIG_DFL and SIG_IGN into functions

Change by Serhiy Storchaka : -- pull_requests: +8393 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34453] ipaddress module accepts some strange IPv6 addresses that it shouldn't

Change by Serhiy Storchaka : -- nosy: +ncoghlan, pmoody ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34453] ipaddress module accepts some strange IPv6 addresses that it shouldn't

Prudvi RajKumar Maddala added the comment: I think Michal is right -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue34494] simple "sequence" class ignoring __len__

Prudvi RajKumar Maddala added the comment: I think it should hang, since we are not throwing any StopIteration exception to break the infinite loop -- nosy: +prudvinit ___ Python tracker

[issue34453] ipaddress module accepts some strange IPv6 addresses that it shouldn't

Luke Kenneth Casson Leighton added the comment: that's interesting, michael: it means that all of the IPv6 validators online are wrong, like this one! https://formvalidation.io/guide/validators/ip/ -- ___ Python tracker

[issue34428] tokenize

Luke Kenneth Casson Leighton added the comment: yep good call terry, not getting any response from the autopep8 developer, and i believe it was down to a loop where the text is being thrown line-by-line at tokenize and it was losing critical state information. so... not a bug in tokenize.

[issue34334] QueueHandler logs exc_info twice

Danish Prakash added the comment: I would like to work on this, just making sure you are not. -- nosy: +prakashdanish ___ Python tracker ___

[issue34171] Lib/trace.cover not removed by the clean target

Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue34465] ipaddress should accept bytearray in addition to bytes

Jörn Heissler added the comment: That's what I'm doing now. But it would be more convenient if I could pass a bytearray. -- ___ Python tracker ___

[issue34465] ipaddress should accept bytearray in addition to bytes

Xiang Zhang added the comment: Why not just bytes(buf[:4]) before passing? -- nosy: +xiang.zhang ___ Python tracker ___ ___

[issue34465] ipaddress should accept bytearray in addition to bytes

Jörn Heissler added the comment: My use case is parsing binary data. For that I use a bytearray as a buffer. buf[:4] gets me another bytearray which I'd want to convert to an ipaddress. I can't think of a usecase for list-of-int. -- ___ Python

[issue34334] QueueHandler logs exc_info twice

Change by Xiang Zhang : -- nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34171] Lib/trace.cover not removed by the clean target

miss-islington added the comment: New changeset 80e9fedcf579537c5bc51ff3c9c18d14d9598564 by Miss Islington (bot) in branch '3.7': bpo-34171: Prevent creating Lib/trace.cover when run the trace module. (GH-8841) https://github.com/python/cpython/commit/80e9fedcf579537c5bc51ff3c9c18d14d9598564

[issue34355] SIGSEGV (Address boundary error)

Xiang Zhang added the comment: So this is a dupliate of #34087 and we can close it? -- nosy: +inada.naoki, xiang.zhang ___ Python tracker ___

[issue34465] ipaddress should accept bytearray in addition to bytes

Serhiy Storchaka added the comment: What is your use case? New features can be added only in the developed version. -- nosy: +ncoghlan, pmoody, serhiy.storchaka versions: -Python 3.4, Python 3.5, Python 3.6, Python 3.7 ___ Python tracker

[issue34493] Objects/genobject.c: Missing NULL check in compute_cr_origin()

miss-islington added the comment: New changeset 46af206ea4e9d67375559f8c584a996f70b7b7e5 by Miss Islington (bot) in branch '3.7': closes bpo-34493: Objects/genobject.c: Add missing NULL check to compute_cr_origin() (GH-8911)

[issue34171] Lib/trace.cover not removed by the clean target

Change by miss-islington : -- pull_requests: +8392 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34171] Lib/trace.cover not removed by the clean target

Serhiy Storchaka added the comment: New changeset c406d5cd74002964a64c3eb7d9e2445a7fd3a03f by Serhiy Storchaka in branch 'master': bpo-34171: Prevent creating Lib/trace.cover when run the trace module. (GH-8841)

[issue34486] "RuntimeError: release unlocked lock" when starting a thread

Change by Xiang Zhang : -- nosy: +vstinner, xiang.zhang ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34493] Objects/genobject.c: Missing NULL check in compute_cr_origin()

Change by miss-islington : -- pull_requests: +8391 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34493] Objects/genobject.c: Missing NULL check in compute_cr_origin()

Benjamin Peterson added the comment: New changeset 8fdd331bbf7e60dd81c02c7077f44c7939e2a05d by Benjamin Peterson (Alexey Izbyshev) in branch 'master': closes bpo-34493: Objects/genobject.c: Add missing NULL check to compute_cr_origin() (GH-8911)

[issue34496] Argparse library: parse --set type

New submission from fralau : With argparse, an common requirement is is that a user may want to pass a series of key/value pairs (a sort of equivalent of **args on the command line). Here is a solution that could be implemented in the standard library with little effort. This can be done

[issue34495] excess_args asserts if args == nullptr

Serhiy Storchaka added the comment: object_new and object_init should not be called with args == NULL. This looks like a bug in the user code. Even without assert(PyTuple_Check(args)) in PyTuple_GET_SIZE it dereferences the NULL pointer if args == NULL. Unless there is a code in CPython

  1   2   >