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
docs: Clarify "python" vs "python3" #14
Comments
@windelbouwman: Do you agree that this makes sense, should I make such a change if see a bare "python" command usage? |
Hmm, I don't know, since python2 is officially dead (for some hours ;)), we might assume the default is python3 now? I propose to leave the docs as it is, and improve the error message, which I agree is poor, and should be more explaining. |
I added a more explanatory error message 726dea0 do you mean something like this? |
I personally don't think we can. While "official" deadline has been passed, my system still has "python" pointing to "python2". And it's the same for millions of other users, for months to come, and for sizable numbers still, for years to come. And I expect the echo of confusion to roll around for the next 10-20 years. While "python3" is already there, will be there, and even was there all the time.
Ok, but then I'd suggest to keep this ticket open, and revisit again in some time. |
Yes, that's detailed enough, thanks. |
Ok, in the name of keeping set of open tickets (more) manageable, let's close this ticket (in preference of more "meta" tickets). I for one got that preference is to use bare "python", and followed in e.g. https://github.com/windelbouwman/ppci-mirror/pull/39/files#diff-112623563404e927d73b171234939b31R1 to be consistent within the project, even though I myself would use "pyhon3". We can reopen if there will be actual user reports of confusion. |
It looks like PPCI requires Python3, which is great. It looks like "python -m ppci" syntax is used somewhere in the docs (as suggested in #11), which is also great: https://ppci.readthedocs.io/en/latest/reference/lang/java.html#compile-java-ahead-of-time
However, that uses exactly
python
, and for most users nowadays that will lead to stack trace ending with:Not exactly user friendly (especially for people not familiar with Python, and #11 suggests to keep those in mind).
So, suggested to use
python3
consistently in the commands everywhere.The text was updated successfully, but these errors were encountered: