[issue36800] Invalid coding error hidden on Windows

Yuval Greenfield added the comment: Replacing `utf8` with `utf-8` is the best workaround in my situation. Using the `utf8` alias is required to reproduce the issue based on my testing and the cited issue (https://bugs.python.org/issue20844). Thank you for the reference. --

[issue36800] Invalid coding error hidden on Windows

Eryk Sun added the comment: > Note I am aware the actual problem is "utf8" vs "utf-8". That shouldn't be an issue since "utf8" is an alias. The fact that your test file has LF line endings is an issue. It should be fixed in 3.7.4. See issue 20844. -- nosy: +eryksun resolution: ->

[issue36800] Invalid coding error hidden on Windows

Tim Golden added the comment: Python 3.6.6 (v3.6.6:4cf1f54eb7, Jun 27 2018, 03:37:03) [MSC v.1900 64 bit (AMD64)] on win32 I can't reproduce this on Windows. And it does seem an unlikely combination of effect and cause. Do I take it that if you take out all the "logging..." lines, the thing

[issue36800] Invalid coding error hidden on Windows

Change by SilentGhost : -- type: compile error -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue36800] Invalid coding error hidden on Windows

Yuval Greenfield added the comment: Note I am aware the actual problem is "utf8" vs "utf-8". But for some reason on Windows the exception does not reflect that. -- ___ Python tracker ___

[issue36800] Invalid coding error hidden on Windows

New submission from Yuval Greenfield : These lines fail on Windows in a surprising way: # -*- coding: utf8 -*- import threading print("threading %s" % threading) Normally they would throw this: ```File "C:\Python36\Lib\site-packages\missinglink_kernel\callback\log_monitor.py",