Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Issues with calling "python" from WinPython Command Prompt.exe #352

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.

Sign up for GitHub

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

Jump to bottom
Closed
dougthor42 opened this issue Jun 30, 2016 · 3 comments
Closed

Issues with calling "python" from WinPython Command Prompt.exe #352

dougthor42 opened this issue Jun 30, 2016 · 3 comments
Milestone
2016-03 Ipython 5...

Comments

@dougthor42
Copy link
Contributor

dougthor42 commented Jun 30, 2016 •
edited
Loading

Summary

There seem to be a couple issues when calling python from the WinPython Command Prompt.

Issue 1:

  • Bug: Calling python while in the install_dir/scripts directory opens up ptPython.
  • Expected: Calling python from any directory should run the standard python REPL. Calling ptpython from any directory should run ptpython.

Issue 2:

  • Bug: Exiting ptPython while in the install_dir/scripts directory exits to the install_dir/notebooks directory, but only if entered by using Bug1 above.
  • Expected: Exiting ptpython while in the install_dir/scripts directory should return the user to the install_dir/scripts directory.

Example:

winpython_ptpython_issue

Version:

Fresh install of WinPython 3.5.1.3 (bd23ff5)
@dougthor42
Copy link
Contributor Author

Note that calling ptpython from install_dir/scripts does not cause the 2nd issue to occur. I've updated the OP to reflect this.

@stonebig
Copy link
Contributor

this should be fix with #317 of April 2nd. Please try recent builds or wait next release

@dougthor42 dougthor42 mentioned this issue Aug 30, 2016
Closed
@dougthor42
Copy link
Contributor Author

I've finally gotten around to testing this, sorry for the delay! Issue 1 seems to be resolved. However, issue 2 still occurs. I've opened up bug #384 for it.

Thanks,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2016-03 Ipython 5 / PyQt5.6 / Matplot...
Development

No branches or pull requests
2 participants
@stonebig @dougthor42