[issue27578] inspect.findsource raises exception with empty __init__.py

kernc added the comment: The proposed patch doesn't break any interfaces. `inspect.getsource/.getsourcelines()` still raise `OSError` if the source is unretrievable. `linecache.getlines()` is undocumented, but the change retains perfect compatibility with *docstrings* of

[issue27578] inspect.findsource raises exception with empty __init__.py

Change by kernc : -- keywords: +patch pull_requests: +20006 stage: -> patch review pull_request: https://github.com/python/cpython/pull/20809 ___ Python tracker <https://bugs.python.org/issu

[issue27578] inspect.findsource raises exception with empty __init__.py

Change by kernc : -- nosy: +kernc versions: +Python 3.10, Python 3.9 ___ Python tracker <https://bugs.python.org/issue27578> ___ ___ Python-bugs-list mailin

[issue30533] missing feature in inspect module: getmembers_static

Change by kernc : -- nosy: +kernc ___ Python tracker <https://bugs.python.org/issue30533> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue27069] webbrowser creates zombi processes in the background mode

Change by kernc : -- nosy: +kernc versions: +Python 3.7, Python 3.8, Python 3.9 ___ Python tracker <https://bugs.python.org/issue27069> ___ ___ Python-bugs-list m

[issue17972] inspect module docs omits many functions

Change by kernc : -- nosy: +kernc ___ Python tracker <https://bugs.python.org/issue17972> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue33337] Provide a supported Concrete Syntax Tree implementation in the standard library

Change by kernc : -- nosy: +kernc ___ Python tracker <https://bugs.python.org/issue7> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue24119] Carry comments with the AST

Change by kernc : -- nosy: +kernc ___ Python tracker <https://bugs.python.org/issue24119> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue34624] -W option and PYTHONWARNINGS env variable does not accept module regexes

Change by kernc : -- nosy: +kernc ___ Python tracker <https://bugs.python.org/issue34624> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue9338] argparse optionals with nargs='?', '*' or '+' can't be followed by positionals

Change by kernc : -- nosy: +kernc ___ Python tracker <https://bugs.python.org/issue9338> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue22543] -W option cannot use non-standard categories

Change by kernc : -- nosy: +kernc ___ Python tracker <https://bugs.python.org/issue22543> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue29620] unittest.TestCase.assertWarns raises RuntimeEror if sys.modules changes size

Change by kernc : -- keywords: +patch pull_requests: +4699 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue29620> ___ ___ Python-

[issue29620] unittest.TestCase.assertWarns raises RuntimeEror if sys.modules changes size

New submission from kernc: If any of the objects in sys.modules is a module-like object that performs some additional imports in its __getattribute__ (as appropriate) handler, the following simple unit test test case: import unittest import warnings ... # Ensure one of the

[issue26303] Shared execution context between doctests in a module

kernc added the comment: The use case is not unpopular [1] and with unambiguous examples like >>> arr = np.arange(5) >>> my_sum(arr) 10 (i.e., without importing numpy as np everywhere), it also makes a lot of sense. [1]: http://stackoverflow.com/questions/131

[issue26303] Shared execution context between doctests in a module

New submission from kernc: The doctest execution context documentation [0] says the tests get shallow *copies* of module's globals, so one test can't mingle with results of another. This makes it impossible to make literate modules such as: """ This module i

[issue22253] ConfigParser does not handle files without sections

kernc added the comment: > > I am dubious that there are any with a mixture of both sections and > additional option lines at the top without a section. > rsyncd.conf [1] is one such example, and I wouldn't say there aren't countless more in the wild. > Anyone writi

[issue22253] ConfigParser does not handle files without sections

kernc added the comment: I, for one, would actually prefer if global options were parsed by default and MissingSectionHeaderError was deprecated instead. >From what little specification available, INI format does **not** require >options be in sections [4, 5]. Additionally, "Lin

[issue22253] ConfigParser does not handle files without sections

New submission from kernc: ConfigParser does not handle files that specify options in the "global" section (first option specified before any section is). This configuration "behavior" is present in the configuration files in the wild [1, 2], and while the naive