-
Notifications
You must be signed in to change notification settings - Fork 40
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
SublimeREPL broken, due invalid handle error when calling subprocess.Popen().poll()
#6091
Comments
Just to clarify, is that working using both Python 3.3 and Python 3.8 hosts? Or is it a bug in just the Python 3.3 host? |
Behavior is equal on both python 3.3 and 3.8. Sending text fails due to failed Console command works on both. Also note, that sending text and evaluating works as expected if replacing The interpreter itself is alive and the |
Looks like SublimeREPL has a custom I had a look through the difference between 3.8.8 and 3.8.12 in relation to subprocess and file handles and there isn't anything that jumps out. I'd be surprised if it didn't have the same issue in 3.8.8 and earlier versions of 3.8. |
Looks like SublimeREPL will remain broken then. It looks rather unmaintained. |
Looking over PRs it appears this issue has already hit someone earlier. wuub/SublimeREPL#577 fixes the issue. |
Description of the bug
Latest dev builds (ST4153/4154) break SublimeREPL package. I just had a hard time trying to reproduce a users error, because sending text to a REPL failed with WinError 6.
Exactly the same procedure works in ST4143. (Haven't checked 4152)
Steps to reproduce
print("me")
and save it.ctrl+,
,f
key sequence to send file content to the repl.Expected behavior
That's what ST4143 does.
Actual behavior
ST4153/54 however displays a WinError 6, while checking for alive interpreters.
I can however successfully call the following in ST's console:
Sublime Text build number
4153
Operating system & version
Windows 11
(Linux) Desktop environment and/or window manager
No response
Additional information
No response
OpenGL context information
No response
The text was updated successfully, but these errors were encountered: