fix: Python highlighting issues

[rennsax]

TL;DR: Go to "Detailed Changes"

This PR reverts disapproved #223, improves Python semantic highlighting features, with #232 finished. #223 happened to remove the highlight of self keyword, which is mentioned in #233.

The syntax highlighting and semantic highlighting work together to provide the developers with more recognizable tokens. Semantic highlighting is more powerful, and generally more precise. It's highly recommended to turn on semantic highlighting features in VS Code.

To enable it, install the corresponding language support extension (typically a language server, for example, Pylance for Python), and configure in your settings.json:

    "editor.semanticHighlighting.enabled": true

This setting entry is true by default, in case someone unexpectedly set it to false.

No semantic:

With semantic:

In addition, since semantic highlighting overrides common syntax highlighting, it also offers the abilities to customize the token color with much flexibility. See this example.

Therefore, this PR expands the semantic highlighting feature on Python language. I've made the changes for one more months, and I didn't detect any side effects (like accidentally changing other language's highlighting color).

Detailed Changes

1. Fix the self keyword problem. This is done by reverting Customize the color of specific object types in python #218 #223 and add rules into "semanticTokenColors".
   

2. Add additional highlighting to Python function decorators.
   

PS:

• About Customize the color of specific object types in python #218: I suggest turn on the semantic highlighting feature, rather than focus on the native syntax tokens. It's hard to strike a balance, and can easily produce side effects.
• Is it necessary to revert Customize the color of specific object types in python #218 #223? Yes. It acts strangely, no matter whether the semantic highlighting is enabled or not. See below.
  With semantic:
  
  Without semantic:
  

Thanks for your checking! @wesbos @palashmon

[SmitAkbari26]

@Eitheages In mine vs code no difference make with semantic or without semantic.

And at same time it's not solve issue which pr is merged.

[rennsax]

@SmitAkbari26 Have you installed and enabled Pylance?

[SmitAkbari26]

@Eitheages I install it and with semantic and with your changes

Previously it was look like this after i remove mine merged pr with semantic

And this without semantic

This is after mine pr is merged without semantic sorry for i not set self scope

And this is with semantic

This is i make some little bit change in mine previous changes with semantic

And without semantic

Why you need to make that much changes to do same things?

[rennsax]

@SmitAkbari26 I've emailed you a comment because I think it's better to communicate more with you :)

[SmitAkbari26]

Ye i installed pylance

…

On Fri, 25 Aug 2023 at 11:12, Bojun Ren ***@***.***> wrote: @SmitAkbari26 <https://github.com/SmitAkbari26> I've emailed you a comment because I think it's better to communicate more with you :) — Reply to this email directly, view it on GitHub <#236 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A54QOVKEKA7UNN474AAYWATXXA3MJANCNFSM6AAAAAA3ZN4JNE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Sanqui]

Chiming in: I would like to see this merged (to have self differentiated again).