[issue40487] Unexpected exception handler behavior in Jupyter when returning task objects created with create_task

John Smith added the comment: Additional note: In a almost identical set-up, the simple fact of assigning the task object to a variable: `task = loop.create_task(coroutine())` instead of just calling: `loop.create_task(coroutine())` ...results in the same unexpected behavior in exception

[issue40487] Unexpected exception handler behavior in Jupyter when returning task objects created with create_task

Change by John Smith : -- type: -> behavior ___ Python tracker <https://bugs.python.org/issue40487> ___ ___ Python-bugs-list mailing list Unsubscrib

[issue40487] Unexpected exception handler behavior in Jupyter when returning task objects created with create_task

New submission from John Smith : Hi, I'm running the following code in a Jupyter notebook (so there is already a running loop). `run_coro` (non-async function) adds given coroutines to the loop with `loop.create_task`. I want to return the task objects created by `loop.create_task

[issue39724] IDLE threading + stdout/stdin observed blocking behavior

John Smith added the comment: Interesting finding. Just some thoughs: I have to disagree on the "the experience with input() in IDLE is more useful and less confusing, especially to beginners" part. Here are some reasons: 1. If a beginner starts with threading and expect a

[issue39724] IDLE threading + stdout/stdin observed blocking behavior

John Smith added the comment: P.S. here (other computer but with same observed behavior) I have a 3.6 32bit as one can see from the output. -- ___ Python tracker <https://bugs.python.org/issue39

[issue39724] IDLE threading + stdout/stdin observed blocking behavior

Change by John Smith : Added file: https://bugs.python.org/file48901/IDLE_threading_issue_min_example1.py ___ Python tracker <https://bugs.python.org/issue39

[issue39724] IDLE threading + stdout/stdin observed blocking behavior

John Smith added the comment: py -m idlelib -n path output: Python 3.6.4 (v3.6.4:d48eceb, Dec 19 2017, 06:04:45) [MSC v.1900 32 bit (Intel)] on win32 Type "copyright", "credits" or "license()" for more information. No Subprocess WARNING: Run

[issue39724] IDLE threading + stdout/stdin observed blocking behavior

New submission from John Smith : preamble: I am aware that I am not the first to encounter this issue but neither I could identify a preexisting ticket which fully matches nor is the commonly recommended "solution" (stay away from IDLE) satisfying. environment: win10, python 3

[issue1706039] Added clearerr() to clear EOF state

John Smith ebgs...@gmail.com added the comment: Sorry for inconvenience caused with the patch. I should've got more reviews before asking it checked in. I verified eof2.diff-applied-python gets Bus error and Scott Dial's fileobject.diff fixes this. (Test was on 9.6.0 Darwin Kernel Version 9.6.0

[issue1706039] Added clearerr() to clear EOF state

John Smith [EMAIL PROTECTED] added the comment: Hi, when will this patch be checkedin? -- versions: +Python 2.5.3, Python 2.6, Python 3.0 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1706039

[issue1276] LookupError: unknown encoding: X-MAC-JAPANESE

John Smith [EMAIL PROTECTED] added the comment: Confirmed now I can build Python on Mac OS X with Japanese locale. I tested the followings. Python 2.6b3+ trunk:66060 Python 3.0b3+ py3k:66060 Thank you very much. ___ Python tracker [EMAIL PROTECTED] http

[issue1706039] Added clearerr() to clear EOF state

John Smith added the comment: What's in a name? :p Done, anyway. _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1706039 _ ___ Python-bugs-list mailing list Unsubscribe