-
-
Notifications
You must be signed in to change notification settings - Fork 628
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
Readme: Updated the "Running the Source Code" section to make it clea… #11160
Readme: Updated the "Running the Source Code" section to make it clea… #11160
Conversation
Hi, actually it doesn’t matter as to which Python executable gets used (pyw or py), as they are needed for different needs: Pyw if you are strictly looking for running as GUI, and regular py if you want to look at dumps fros PowerShell, Command Prompt and such (dealing with issues that may not show up if run strictly as a GUI app). Thanks.
|
Is this better? Note: Use |
Hi, yes. Note that there is a more convenient way: py/pyw. Thanks.
|
@josephsl wrote;
It is more convenient only if you have one version of Python installed. If not py/pyw defaults to the most recently installed which is not always what we want. It is also easier to run pythonw.exe from the specific path in case of multiple versions installed rather than fiddle with pyw parameters to specify version. |
Hi, true. One must specify the version to run (py/pyw -3.7-32). Thanks.
|
I think it is up to the developer to choose the version and python executable to use. Adding the details for the same in the readme seem unnecessary. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, thanks for clarifying this for new developers.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @ShubhamJain7 🎉
Link to issue number:
None
Summary of the issue:
The "Running From Source" section of the Readme was a bit unclear as it didn't mention the exact commands needed to run the source code.
Description of how this pull request fixes the issue:
The "Running From Source" section of the Readme now mentions the commands for running from source and the reason for using
pythonw.exe
is now a note that immediately follows the commands.Testing performed:
None
Known issues with pull request:
None
Change log entry:
not necessary