Yes, this is a bug in the Python parser. The new one we plan on using comes from @universal-ctags and doesn't suffer from this, but it's quite some work that is going on in #1263 and friends.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.