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

windows is python and not python3 #127

Closed
River-Mochi opened this issue Mar 27, 2023 · 2 comments
Closed

windows is python and not python3 #127

River-Mochi opened this issue Mar 27, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@River-Mochi
Copy link
Contributor

River-Mochi commented Mar 27, 2023

To Reproduce
Steps to reproduce the behaviour:

  1. just installed Source-all v 1.12.8 on windows 11
  2. setup-dev.bat file is made for Windows terminal users yet it calls for python3 and not python
    this causes error messages and for it to not execute correctly.
  3. on Windows installs, all python will be simply python and not python3 which does not exist
  4. only way I can get this script to work is to manually remove the "3" from all locations in the script.
  5. this might be one real reason some people have issues getting Pinesam to run on Windows, not the install of python on windows but that the setup-dev.bat is calling for a command name that does not exists.

Issues with script are highlighted
image

Alias's can be made in windows to point python3 names to python but making users do that it's a lot of extra work and confusing steps for windows users. also if they don't do it certain way then it's not persistent, it's really easier to just call it Python and not python3 (since python3 does not exist in Windows).

see screenshot, on Windows Python will be installed as simply "python" the Terminal Powershell and also Command will not know what "python3" is since this command does not exist.

image

@River-Mochi River-Mochi added the bug Something isn't working label Mar 27, 2023
@River-Mochi
Copy link
Contributor Author

After removing all the "3" from the setup-dev.bat and running it again in Windows Powershell terminal, it correctly checks for python things now but still has a couple other warnings and errors not related to python ( a lot less after I removed all the "python3" references in setup-dev.bat).

@River-Mochi
Copy link
Contributor Author

Closed as fixed with update #128

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant