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

Skip to content

Exiting python after being called from "...\scripts" directory changes the CWD. #384

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

Closed
dougthor42 opened this issue Aug 30, 2016 · 1 comment

Comments

@dougthor42
Copy link
Contributor

Summary

Exiting python after being called from "...\scripts" directory changes the CWD.

Steps to Reproduce:

  1. Open up <install_dir>\WinPython Command Prompt.exe
  2. type python to start the interpreter
  3. type exit()

Expected Behavior:

The CWD stays at <install_dir>\scripts.

Actual Behavior:

The current directory changes to <install_dir>\notebooks.

Example:

winpython_python_issue

Versions:

  • Fresh install of WinPython 3.5.2.2, 64-bit, Qt5
  • Windows 10 Pro, Anniversary Update (v1607, build 14393.82)

Related Issues:

@stonebig stonebig added this to the 2016-05 "next wave": Matplotlib 2.0 / scikit-optimize / Pandas 0.19.1 milestone Aug 31, 2016
@stonebig
Copy link
Contributor

stonebig commented Sep 1, 2016

in scripts, change current python.bat from

@echo off
call "%~dp0env_for_icons.bat"
cd/D "%WINPYWORKDIR%"
rem backward compatibility for  python command-line users
"%WINPYDIR%\python.exe"  %*

to

@echo off
call "%~dp0env_for_icons.bat"
rem backward compatibility for  python command-line users
"%WINPYDIR%\python.exe"  %*

will be in next beta

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants