-
Notifications
You must be signed in to change notification settings - Fork 2
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
Issues in README.md #125
Comments
Good catch.
WSL 2 installs linux in a virtual machine. I don't know for sure, but that sounds like it would have a separate path, and any Python installed would be a Linux-style install. This seems to confirm: https://stackoverflow.com/questions/78033592/do-wsl-use-the-python-installation-which-is-installed-on-windows-host#:~:text=You%20can%20install%20Python%20within,command%20sudo%20apt%20install%20python3%20.
For several reasons, I prefer the behavior of the Python plcc script which doesn't have a default file and would prefer to remove the "default code" in the plcc bash script.
|
Typo fixed. |
I am in favor of this, for the same reasons that Stoney stated. |
After the table, the text is "Having your students/developers perform native installations on their individual machines can lead to unexpected challenges do to the variety of different environments this creates. " That should be "due to".
In the Python section, we have the reader check their version of Python by running the command
python3 --version
Doesn't Windows install the interpreter for Python 3.x with the old name "python"? If so I don't think that the installation of WSL would change that, but I don't know it from personal experience. Perhaps it uses python3.exe as an alias now.
According to the scripts, it looks like the default grammar file is named "spec", and the second choice is "grammar". The former is not documented anywhere. Also, It looks like the plain plcc script does not assume any default grammar file name.
The text was updated successfully, but these errors were encountered: