-
Notifications
You must be signed in to change notification settings - Fork 13
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
Cannot start s3e on Windows 10 x64 with Python 3.9.7 x86 #36
Comments
I run s3e in a command window. I've never heard of the composable shell. How does one start the composable shell? I cannot find any documentation about it. I am not sure if I understand your suggestions. When you say, check the returned string for being empty. Are you referring to this line in your example code?
If that is the line, I don't understand how it can be empty. When you say the same bitness for both Python and Windows, what are you referring to? |
I have no idea what is the process The value in
If Python is 64-bit then the issue doesn't happen on Windows 64-bit (I haven't checked this though). |
As you point out, this issue is a problem within psutil. I do not want to make any changes in my code that mask a problem in someone else's. In addition, I do not want to have to change my code again if the psutil fix causes some other issue. One option for you is to fork s3-extend, make the changes you wish in s3e and save them. Then go to the directory above where the forked version of the s3-extend setup.py file is stored, and then enter:
You will then have a local copy with the fix. When psutil is repaired, you can always reinstall s3-extend from pypi to have the official version. Since the s3e file is the only file to be affected, and I do not see any reason to change it at this time, I feel this is the lowest risk solution for both of us. |
To explain why I am not willing to take on any additional risk in changing the code, here are the download statistics for s3-extend from pepy. Since I cannot test the changes you are requesting, with 35000 users, if something breaks, I will have many unhappy users. |
I searched the web for articles on windowsinternal.composableshell.experiences.textinput.inputapp.exe, and apparently, it has caused users some issues. There are several articles on disabling and removing it, but since this process does not run on any of my computers, I cannot suggest which, if any, is the best. There are also articles on forcing short names in Windows, but I do not know if this works for process names. Perhaps you can experiment with these solutions. I am going to close this issue, but it can be reopened if necessary. |
psutil 5.9.0 was released, so this issue shouldn't happen any longer |
I just installed s3-extend using Python 3.9.7 on Windows 10 without any issues. If you are still seeing the same errors you posted above, and still have windowsinternal.composableshell.experiences.textinput.inputapp.exe, |
I'm unable to start
s3e
on Windows 10 64-bit with Python 3.9.7 32-bit:Other servers (namely
backplane
,espgw
,wsgw
andmonitor
) run fine, when started individually.Here is the test script (rewritten fragment of
start_backplane
froms3e.py
):Output:
Screenshot from Task Manager:
It looks like another bug in
psutil
- see giampaolo/psutil#1980 where the module can't properly handle long names (due to "bitness mismatch").I'm not sure whether a process can run without a name, but it may be worth checking the returned string (is it empty?) before trying to search for
backplane
in it (yeah, it's a kind of hack/workaround).Another possible workaround it to use same 'bitness' both for Python, and for Windows.
The text was updated successfully, but these errors were encountered: