Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Highlight self #21

Closed
Olivia5k opened this issue Oct 3, 2014 · 4 comments
Closed

Highlight self #21

Olivia5k opened this issue Oct 3, 2014 · 4 comments

Comments

@Olivia5k
Copy link

Olivia5k commented Oct 3, 2014

self is the standard keyword for self-reference in Python OO. I suggest that we link it to special.

I tried to find prior discussion about this since I felt that this kinda had to be discussed before, but I found nothing. Apologies if that was the case!

@lonetwin
Copy link

Strictly speaking self is not really a keyword but yeah it would be good to highlight it (and the other strong conventional keyword cls as well)

@hdima
Copy link
Owner

hdima commented Dec 28, 2014

Well, it was discussed a little bit before in #10.

I don't want to add highlighting for self for a number of reasons:

  • I actually tried it and I don't really like how it looks. It adds too many colors to the code to the point that it's getting harder to follow.
  • As @lonetwin already mentioned, self is actually just a conventional name for the first argument of a method. And if somebody uses for example just s instead it won't be highlighted and just will be confusing.
  • As it just an argument of a method it also can raise a question "why the other arguments not highlighted?" and also can add to the confusion.

@Olivia5k
Copy link
Author

It is a conventional name, but it is used in literally 99.99% of all OO Python code. I have worked with Python almost exclusively for the better part of a decade, and I have never seen anyone use anything but self. So, if someone averts themselves from this de facto standard, I don't think they will be confused if their tooling would not follow suit 100%. Even if they are, I would argue that the other 99.99% of all users would be happy to have all their keywords highlighted.

For your first and second points, they can be tweaked. self highlight could be a default-on option so that it can be disabled, and adding highlights for other arguments is actually something that can be done. I have already implemented a light way (highlighting *args and **kwargs and the value part of key=value) into this project, but I was holding off on making PRs until this was resolved. Guess I won't be adding them.

I'll respect your decision, but I'll also express some general concern about the Open Source way of disregarding useful ideas and changes because they might be troublesome for a single hypothetical power user. The lack of colored prompts and tab completion in default Debian and Ubuntu shells come to mind; the argument was that people still using print terminals or really slow computers would have a slightly worse time.

@hdima
Copy link
Owner

hdima commented Jan 2, 2015

Probably not so good example but there's a class which uses s instead of self: https://hg.python.org/cpython/file/3.4/Lib/sched.py#l45

I'll respect your decision, but I'll also express some general concern about the Open Source way of disregarding useful ideas and changes because they might be troublesome for a single hypothetical power user.

I think the main point of Open Source is that you can create your own version of a project if you think that your changes are useful and they can't be incorporated to the mainline version for some reason. It's actually one of the reasons why this project exists.

anntzer pushed a commit to anntzer/python-syntax that referenced this issue Apr 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants