What the title says. Guido has decided the inconsistency with the space instead of parentheses is evil.
I can submit a PR. What path do you want to take?
Fork genesource.py into genesource2.py and genesource3.py. Maintain 2 separate files going forward.
Keep genesource.py but use 2to3 to build genesource3.py. This requires a separate build step by you, the maintainer, to release into ELPA or whatever going forward.
Keep genesource.py but require the user to have 2to3 in their Python env, which (from personal experience) is not included by virtualenv, or at least pyenv-virtualenv. (Not sure about other combinations like virtualenvwrapper.) Put this in the instructions.
All these require elisp to shell out to get the Python version to figure out the .py file to call.
What the title says. Guido has decided the inconsistency with the space instead of parentheses is evil.
I can submit a PR. What path do you want to take?
All these require elisp to shell out to get the Python version to figure out the .py file to call.
Which do you want?