inconsistency about the project's name about guess-filename.py HOT 2 CLOSED

from guess-filename.py.

First: you are absolutely right. I did not pay attention in creating a consistent naming scheme which caused this mess you're describing.

I guess my original intention was to "mark" this tool as a Python one by adding ".py" to its repository name. This does not provide any benefit for the CLI execution as a user and therefore I might have omitted the ".py" in the alias I created.

So what about now?

Fixing this mess is not an easy job to do. I refrain from renaming this repository because this would break all existing links which are many. I could maybe find all my own references which are scattered across many blog articles and project READMEs. I can not fix links published in talks and slide-sets. Therefore, I can not rename this repository.

Adding a useless ".py" to the CLI alias would not provide any benefit from my point of view.

Maybe I fix that stupid inconsistency when I follow my "migrate everything from GitHub to a more free alternative" which will break stuff anyway. This is very low priority at the bottom of my list of projects. I won't give it much chances unless Microsoft gets even more evil in future.

Therefore, I can only beg for forgiveness for this mess I've caused.

from guess-filename.py.