You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 5, 2023. It is now read-only.
What does CPython's ast module give in this case? (Preferably fro Python 3.6, since that's what typed_ast is currently derived from -- we're trying to find time to work on Python 3.7 support.) If the same problem occurs with CPython's ast module, the problem is there and should be fixed there before we can fix it here.
I just checked on 3.7 and it seems that typed_ast has the same behavior as the ast module, so I presume it is the same as for 3.6 (thus this seems to an issue for upstream).
Hello.
I'm working on a bug affecting
pylint
, which usesastroid
, which usestyped_ast
:pylint-dev/pylint#2610
What troubles me is the
.col_offset
value of aStr
node containing a non-ASCII character with Latin1 encoding.Here is a minimal code example:
From my understanding a "
é
" character as a length of 1 in Latin-1:https://en.wikipedia.org/wiki/ISO/IEC_8859-1#Code_page_layout
Hence, could someone help me understanding why the
.col_offset
is higher in that case, please ?The text was updated successfully, but these errors were encountered: