[issue31776] Missing "raise from None" in /Lib/xml/etree/ElementPath.py

Change by Pablo : -- keywords: +patch pull_requests: +3953 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mailin

[issue29762] Use "raise from None"

Change by Pablo : -- pull_requests: +3954 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.

[issue30058] Buffer overflow in kqueue.control()

Serhiy Storchaka added the comment: New changeset 9aa60245a0ff929e528b4521da7af20dacd4145b by Serhiy Storchaka in branch '2.7': [2.7] bpo-30058: Fixed buffer overflow in select.kqueue.control(). (GH-1095). (#3976) https://github.com/python/cpython/commit/9aa60245a0ff929e528b4521da7af20dacd414

[issue30058] Buffer overflow in kqueue.control()

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

[issue31742] Default to emitting FutureWarning for provisional APIs

Change by Ned Deily : -- nosy: +ned.deily ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.

[issue22674] strsignal() missing from signal module

Antoine Pietri added the comment: Hey everyone, We would like to have that feature for a project where we have to use ctypes to achieve that. I don't know the answers to vajrasky's questions but I just wanted to chime in to say having this feature would be greatly appreciated. I can also wor

[issue31767] Windows Installer fails with error 0x80091007 when trying to install debugging symbols

Steve Dower added the comment: FWIW, all your assumptions about how it should work are correct. If you don't know how the files got there instead of a randomly generated temporary path, then I don't know either. /layout is the only time we download anything to a non-temp directory. -

[issue31777] IDLE: Let users add to font selection

New submission from Terry J. Reedy : Config dialog Font tab has a sample box. It currently only contains Ascii chars. #13802 will add characters from extended latin1 and several other character sets. But we cannot show everything. Hence a spinoff proposal: let users augment the sample with

[issue13802] IDLE font settings: use multiple character sets in examples

Terry J. Reedy added the comment: I pushed new commits to the PR that changed the Korean, Japanese, and Indian samples and the help message. Korea: The line is now the first 10 chars of Dong-hee Na's suggestion. Thank you for helping (and Louie for the cc). Japan: The line is now the hiraga

[issue31778] ast.literal_eval supports non-literals in Python 3

New submission from David Bieber : # Overview ast.literal_eval supports some non-literals in Python 3. The behavior of this function runs contrary to the documented behavior. # The Issue The [documentation](https://docs.python.org/3/library/ast.html#ast.literal_eval) says of the function "It

[issue31778] ast.literal_eval supports non-literals in Python 3

Change by David Bieber : -- type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue31761] regrtest: faulthandler.enable() fails with io.UnsupportedOperation: fileno when run from IDLE

Terry J. Reedy added the comment: Victor, what is your opinion of running 'from test import autotest' in a standard python shell window, opened from an icon, as opposed to IDLE's shell? > many tests fail just because of IDLE. We cannot know what to blame on IDLE without a proper control expe

[issue31761] regrtest: faulthandler.enable() fails with io.UnsupportedOperation: fileno when run from IDLE

Terry J. Reedy added the comment: 0:00:28 [ 25/407] test_asyncio F:\dev\3x\lib\asyncio\sslproto.py:330: ResourceWarning: unclosed transport source=self) test_code_module - multiple errors test test_importlib failed -- Traceback (most recent call last): File "F:\dev\3x\lib\test\test_impor

[issue29696] Use namedtuple in string.Formatter.parse iterator response

Change by Pablo : -- keywords: +patch pull_requests: +3956 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mailin

[issue30744] Local variable assignment is broken when combined with threads + tracing + closures

Guido van Rossum added the comment: Wow, nothing here is simple. :-( Even though the examples show that there's obviously a bug, I would caution against fixing it rashly without understanding how the current behavior may be useful in other circumstances. I've lost what I recall from reading P

[issue31761] regrtest: faulthandler.enable() fails with io.UnsupportedOperation: fileno when run from IDLE

Terry J. Reedy added the comment: The Python console exits because test.libregrtest.main.Regrtest._main calls sys.exit. test.autotest consists of from test.libregrtest import main main() The main call should be wrapped with try:...except sys.exit: pass The output also has this variance from

[issue31742] Default to emitting FutureWarning for provisional APIs

Guido van Rossum added the comment: OK, so the Django and Twisted developers had to resist some pressure from their users. These are mature projects and if they can't resist pressure from users something is wrong with those projects, and just pointing users to PEP 411 would have been a suffic

[issue31761] regrtest: faulthandler.enable() fails with io.UnsupportedOperation: fileno when run from IDLE

Terry J. Reedy added the comment: When I import autotest in IDLE's shell, test_code_module fails, test_importlib and test_warnings fail, as without IDLE, and test_gc and test_logging are new failures. (Results are easy to see because SystemExit is caught and ignored.) test test_gc failed --

[issue31742] Default to emitting FutureWarning for provisional APIs

Ned Deily added the comment: Besides making the provisional warning more noticeable in module doc pages, perhaps we should have a "Provisional Package / API" section somewhere in the release's docset: a liat of all provisionals and perhaps a list of formerly provisional, now stable items that

[issue31742] Default to emitting FutureWarning for provisional APIs

Nick Coghlan added the comment: If a proposed standard library API is sufficiently stable that the folks proposing it are reluctant to emit a runtime warning about any remaining stability risks, then I think it's reasonable to expect them to propose it as non-provisional and accept the relate

[issue31742] Default to emitting FutureWarning for provisional APIs

Guido van Rossum added the comment: I am at a loss for words. On Oct 12, 2017 6:27 PM, "Nick Coghlan" wrote: > > Nick Coghlan added the comment: > > If a proposed standard library API is sufficiently stable that the folks > proposing it are reluctant to emit a runtime warning about any remai

[issue31732] Add TRACE level to the logging module

Raymond Hettinger added the comment: No need to be brusque with me. Vinay is the decision maker on this. Overall, this seems rehash and second guess the discussions and decisions made 15 years ago when PEP 282 was accepted. At that time, it was decided that five levels had advantages for le

[issue30632] IDLE: add unittests to test_autocomplete

Change by Berker Peksag : -- superseder: -> IDLE: Add test_autocomplete unittest ___ Python tracker ___ ___ Python-bugs-list mailing

[issue31772] SourceLoader uses stale bytecode in case of equal mtime seconds

Nick Coghlan added the comment: Increasing the number of stat calls required for a successful import is a good reason to close the submitted PR, but I'm not sure it's a good reason to close the *issue*, as there may be other ways to solve it that don't result in an extra stat call for every s

[issue31509] test_subprocess hangs randomly on AMD64 Windows10 3.x

Ned Deily added the comment: I also have seen test_subprocess hangs on both macOS and on Debian Linux on both 3.6 and master, as recently as 3.6.3 and 3.7.0a1 but not with current heads. After some experimenting and bisecting, I tracked the fix down to the mock os.waitpid fixes for bpo-31178

[issue30744] Local variable assignment is broken when combined with threads + tracing + closures

Nick Coghlan added the comment: Aye, what's in PEP 558 is the least invasive implementation change I've been able to come up that fixes the reported bug, but Nathaniel's right that it would break debuggers (and probably some other things) as currently written. So the above design comes from a

[issue31732] Add TRACE level to the logging module

pmpp added the comment: Sorry, i didn't mean to be rude. Just wanted to pick your attention because i think you miss the point: logging as is it with its levels is perfect for *log messages*. Review the typical usage shown and you'll see that tracing level is for logging tracebacks : the deb

[issue31742] Default to emitting FutureWarning for provisional APIs

Nick Coghlan added the comment: Keep in mind that I'm not proposing that we retroactively change our approach to managing any currently provisional APIs that were proposed and implemented under the current version of PEP 411. Instead I'm merely suggesting that the policy for any *future* prov

[issue31772] SourceLoader uses stale bytecode in case of equal mtime seconds

Devin Bayer added the comment: Thanks for the support Nick. I think your proposed idea would still result in rare but confusing behavior, which is the type of surprise Python should avoid. The hash-based pyc files doesn't seem like a solution to me, because it won't be enabled by default. And

[issue31772] SourceLoader uses stale bytecode in case of equal mtime seconds

Nick Coghlan added the comment: The problem with changing the bytecode format is that code other than the import machinery reads the bytecode headers, so when we change the format, we need to consider the impact on that code. (Even my multiplication proposal above suffers from that problem)

[issue31772] SourceLoader uses stale bytecode in case of equal mtime seconds

Devin Bayer added the comment: That wouldn't always work either. If the source file is imported, then edited, then not reimported until the next second (or far in the future) the stale bytecode would still be used. -- ___ Python tracker

<    1   2