[issue25834] getpass falls back when sys.stdin is changed

Adam Bartoš added the comment: Sorry, I don't. But my use case is not relevant any more since my package was a workround for problems with entering Unicode interactively on Windows, and these problems were resolved in Python since

[issue18838] The order of interactive prompt and traceback on Windows

Adam Bartoš added the comment: The order is fine on Python 3.8, Windows 10. -- ___ Python tracker <https://bugs.python.org/issue18838> ___ ___ Python-bugs-list m

[issue18838] The order of interactive prompt and traceback on Windows

Adam Bartoš added the comment: So far I could reproduce the issue on Python 3.7, Windows Vista 64bit. I'll try with newer versions. The output I got: >>> from subprocess import * >>> Popen("py -i foo.py", stdin=PIPE, stdout=PIPE, stderr=PIPE).communicate() (b'',

[issue11395] print(s) fails on Windows with long strings

Adam Bartoš added the comment: I've been hit by this issue recently. On my configuration, print("a" * 10215) fails with an infinite loop of OSErrors (WinError 8). This even cannot by interrupted with Ctrl-C nor the exception can be catched. - print("a" * 10214) is fine

[issue28373] input() prints to original stdout even if sys.stdout is wrapped

Adam Bartoš added the comment: Does GNU readline do anything fancy about printing the prompt? Because you may want to use GNU readline for autocompletition while still enable colored output via wrapped stdout. Both at the same time with one call to input(). It seems that currently either you

[issue18597] On Windows sys.stdin.readline() doesn't handle Ctrl-C properly

Adam Bartoš added the comment: The main reason I have extended the support of win_unicode_console to Python 2.7 was that the related issues won't be fixed there, so using win_unicode_console may fix this as well. -- ___ Python tracker <

[issue28373] input() prints to original stdout even if sys.stdout is wrapped

Adam Bartoš added the comment: Other related issues are #1927 and #24829. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/i

[issue18597] On Windows sys.stdin.readline() doesn't handle Ctrl-C properly

Adam Bartoš added the comment: Maybe this was fixed with the recent fix of #1602. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/i

[issue28373] input() prints to original stdout even if sys.stdout is wrapped

Adam Bartoš added the comment: A related issue is that the REPL doesn't use sys.stdin for input, see #17620. Another related issue is #28333. I think that the situation around stdio in Python is complicated an inflexible (by stdio I mean all the interactions between REPL, input(), print

[issue28333] input() with Unicode prompt produces mojibake on Windows

New submission from Adam Bartoš: In my setting (Python 3.6b1 on Windows), trying to prompt a non-ASCII character via input() results in mojibake. This is related to the recent fix of #1602 and so is Windows-specific. >>> input("α") ╬▒ The result corresponds to prin

[issue17620] Python interactive console doesn't use sys.stdin for input

Adam Bartoš added the comment: > Unfortunately, it looks like detecting when a readline hook has been added is > going to involve significant changes to the tokenizer, which I really don't > want to do. We don't need to detect the presence of readline hook, it may be so that there

[issue1602] windows console doesn't print or input Unicode

Adam Bartoš added the comment: There is also the following consequence of (not) having the standard filenos: input() either considers the streams interactive or not. To consider them interactive, standard filenos and isatty are needed on sys.stdin and sys.stdout. If the streams are considered

[issue1602] windows console doesn't print or input Unicode

Adam Bartoš added the comment: Hello Steve, that's great you are working on this! I've ran through your patch and I have the following remarks: • Since wide chars have two bytes, there may be problem when someone wants to read or write odd number of bytes. If the number is > 1, it's ok si

[issue27582] Mispositioned SyntaxError caret for unknown code points

Adam Bartoš added the comment: Maybe this is related: http://bugs.python.org/issue26152. -- nosy: +Drekin ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/i

[issue27469] Unicode filename gets crippled on Windows when drag and drop

Adam Bartoš added the comment: Without a handler the drop feature is disabled. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/i

[issue27469] Unicode filename gets crippled on Windows when drag and drop

Adam Bartoš added the comment: Also, what versions of Windows does this affect? I have 64bit Vista, so maybe this is fixed in say Windows 10. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/i

[issue27469] Unicode filename gets crippled on Windows when drag and drop

Adam Bartoš added the comment: Thank you very much for the analysis. So Python Windows installers may be changed to set the other drop handler. If the short paths are problem, they may be converted to long ones when initializing `sys.argv

[issue27469] Unicode filename gets crippled on Windows when drag and drop

New submission from Adam Bartoš: When a Python script is run by drag-and-dropping another file on it in Windows explorer, the other file's path becomes sys.argv[1]. However, when the path contains a Unicode characters (e.g. α), it gets crippled – it is replaced by ordinary question mark

[issue26090] More correct string truncating in PyUnicode_FromFormat()

Changes by Adam Bartoš <dre...@gmail.com>: -- nosy: +Drekin ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26090> ___ __

[issue13592] repr(regex) doesn't include actual regex

Adam Bartoš added the comment: Isn't the trucation of long patterns too rough? Currently, repr(re.compile("a" * 1000)) returns something like "re.compile('a)", i.e. no ending quote and no indication that something was truncated (besides the missing quote).

[issue1927] Change input() to always prompt to stderr

Adam Bartoš added the comment: Regarding the comment by Martin Panter from 2015-11-22: It would be nice if PyOS_StdioReadline worked that way. Unfortunately, it's still based on C file objects and char* for the prompt string rather than using actual Python objects. The relevant issue

[issue19570] distutils' Command.ensure_dirname fails on Unicode

Adam Bartoš added the comment: Recently, I was also hit by this when trying to autoset `sys.argv` to a list of Unicode string (see https://github.com/Drekin/win-unicode-console/issues/20#issuecomment-225638271 ). It would be nice to have this fixed. It seems to me (I may be wrong) that every

[issue27268] Incorrect error message on float('')

New submission from Adam Bartoš: >>> float('foo') ValueError: could not convert string to float: 'foo' >>> float('') ValueError: could not convert string to float: should be ValueError: could not convert string to float: '' The message comes from Objects/floatobject

[issue26152] A non-breaking space in a source

Adam Bartoš added the comment: We have one particular invalid token, so why it should point to the next token rather than to the invalid one? -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/i

[issue26152] A non-breaking space in a source

Adam Bartoš added the comment: It could still point to the first or the last byte of the invalid token rather than to the start of the next token. Also, by the Python implementation of the tokenizer in tokenize module we get an ERRORTOKEN containing a non-breaking space followed by a number

[issue26152] A non-breaking space in a source

Adam Bartoš added the comment: That explains the message. But why is the caret at a wrong place? -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/i

[issue26152] A non-breaking space in a source

New submission from Adam Bartoš: Consider the following code: >>> 1, 2 File "", line 1 1, 2 ^ SyntaxError: invalid character in identifier The error is due to the fact, that the space before "2" is actually a non-breaking space. The error message

[issue25834] getpass falls back when sys.stdin is changed

New submission from Adam Bartoš: There is a check in Lib/getpass.py:win_getpass that causes a fallback version to be used when `sys.stdin` is changed. I change `sys.stdin` in my `win_unicode_console` package, and in this situation there is no reason to use the fallback version (see https

[issue17620] Python interactive console doesn't use sys.stdin for input

Adam Bartoš added the comment: I've formulated a proposal regarding this issue: https://mail.python.org/pipermail/python-dev/2015-November/142246.html . Does it make sense? -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.p

[issue12869] PyOS_StdioReadline is printing the prompt on stderr

Adam Bartoš added the comment: > * The interactive interpreter always reads from the original standard input, > whether Readline is used or not. This is not true – the interactive interpreter reads via PyOS_Readline, which may call whatever readline hook is installed. I think the sit

[issue1602] windows console doesn't print or input Unicode

Adam Bartoš added the comment: dead1ne: Hello, I'm maintaining a package that tries to solve this issue: https://github.com/Drekin/win-unicode-console . There are actually many related problems. -- ___ Python tracker <rep...@bugs.python.org>

[issue24829] Use interactive input even if stdout is redirected

Adam Bartoš added the comment: How about reconsidering in the case that the machinery around PyOS_Readline is rewritten as I suggest in #17620 ? -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/i

[issue23572] functools.singledispatch fails when not BaseClass is True

Adam Bartoš added the comment: I was also bitten by this via Enum. Is there any chance this will be fixed in Python 3.5? -- nosy: +Drekin ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23572

[issue9232] Allow trailing comma in any function argument list.

Adam Bartoš added the comment: Some remarks: • A trailing comma after a non-empty argument list is allowed in every call form, including class statement and optional call in decorator syntax. In the grammar, this correponds to `arglist`. • In function definition, trailing comma is allowed

[issue9232] Allow trailing comma in any function argument list.

Adam Bartoš added the comment: Do we want to allow a trailing comma after *args or **kwargs in a function definition? Unlike in a call, **kwargs is always the last thing in the list and nothing can be added after that. Just asking. -- ___ Python

[issue12854] PyOS_Readline usage in tokenizer ignores sys.stdin/sys.stdout

Adam Bartoš added the comment: http://bugs.python.org/issue17620 is a duplicate, but with more discussion. -- nosy: +Drekin ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12854

[issue24829] Use interactive input even if stdout is redirected

New submission from Adam Bartoš: Currently, if one redirects stdout, readline hook is not used (see https://hg.python.org/cpython/file/default/Parser/myreadline.c#l208). I would assume that if I run Python as py -i output.txt, I can use GNU readline or other readline hook for input just like

[issue19518] Add new PyRun_xxx() functions to not encode the filename

Adam Bartoš added the comment: I'm not sure this is the right issue. The support for Unicode filenames is not (at least on Windows) ideal. Let α.py be a Python script with invalid syntax. py α.py File encoding error, line 2 as as compile error ^ SyntaxError: invalid syntax

[issue24771] Cannot import _tkinter in Python 3.5 on Windows

Adam Bartoš added the comment: It seems that both tcl86t.dll and tk86t.dll can be found, but their dependency VCRUNTIME140.dll cannot. For some reason, Dependency Walker cannot locate also python35.dll and ieshims.dll (but it tries to find all three libraries in Python 3.5\DLLs and at least

[issue24771] Cannot import _tkinter in Python 3.5 on Windows

New submission from Adam Bartoš: I found out that I cannot import tkinter in Python 3.5.0b4 on 64-bit Windows Vista. Trying to import _tkinter results in ImportError: DLL load failed. On the other hand I have no problem importing _ctypes whose .pyd file is at the same location as _tkinter.pyd

[issue18838] The order of interactive prompt and traceback on Windows

Adam Bartoš added the comment: Yes, it is a behavior change between Python 2 and Python 3. I just tried with 2.7 and 3.0. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18838

[issue24695] Don't print traceback header if traceback is None in TracebackException

Adam Bartoš added the comment: I meant this one: https://docs.python.org/3.5/whatsnew/changelog.html#python-3-5-beta-4 . -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24695

[issue24695] Don't print traceback header if traceback is None in TracebackException

Adam Bartoš added the comment: Ok, thanks. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24695 ___ ___ Python-bugs-list mailing list

[issue24695] Don't print traceback header if traceback is None in TracebackException

Adam Bartoš added the comment: Just out of my curiosity – why is not this issue listed in Python 3.5b4 changelog even though the issue is fixed there? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24695

[issue24695] Don't print traceback header if traceback is None in TracebackException

Adam Bartoš added the comment: Thank you all for a quick reaction. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24695 ___ ___ Python-bugs-list

[issue24695] Don't print traceback header if traceback is None

New submission from Adam Bartoš: The documentation of traceback.print_exception says if traceback is not None, it prints a header Traceback (most recent call last):. That also meant that the header wasn't printed if traceback was None. However, the new Python 3.5 TracebackException object

[issue24696] Don't use None as sentinel for traceback

New submission from Adam Bartoš: There is a subtle bug in Python 3.4 implementation of traceback library: import traceback try: ... 1 / 0 ... except Exception as e: ... exc = e ... traceback.print_exception(exc.__class__, exc, exc.__traceback__) Traceback (most recent call last

[issue24677] def f(*args, ): pass does not compile

New submission from Adam Bartoš: I think that a trailing comma in function definition should be allowed also after *. Current situation with definitions: def f(*args, ): pass # SyntaxError def f(*, ): pass # SyntaxError def f(*, a, ): pass # SyntaxError def f(*, a=2, ): pass # SyntaxError

[issue9232] Allow trailing comma in any function argument list.

Adam Bartoš added the comment: Reposting from from my newest duplicate of this issue (Issue 24677), which is now closed: I think that a trailing comma in function definition should be allowed also after *. Current situation with definitions: def f(*args, ): pass # SyntaxError def f

[issue23057] [Windows] asyncio: support signal handlers on Windows (feature request)

Adam Bartoš added the comment: David Robertson: The behaviour you pointed out is a consequence of the general issue: signals on Windows aren't fully supported. Basically, they cannot interrupt the event loop when every coroutine is waiting for something. Instead, they are fired when something

[issue23057] [Windows] asyncio: support signal handlers on Windows (feature request)

Adam Bartoš added the comment: I've also run into this issue (see https://mail.python.org/pipermail/python-list/2015-July/693496.html and the following thread). I'm adding some small examples showing the behavior. import asyncio async def wait(): await asyncio.sleep(5) loop