-
Notifications
You must be signed in to change notification settings - Fork 317
Open With "IDLE (Python GUI).exe" doesn't open the py script and only opens the shell #1576
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
Comments
shall fix winpython#1576 (for this rc at least)
on your version, try:
then
|
the new version is more explicit on what it does in "-v" verbose mode, yet --register as a bug in rc but, I don't see what miss you in the old one. new version in verbose mode:
|
Will do a rc2 to fix "current" one bug found inquiring on your problem. the new release shall be more easy to read in its "registering" and is verbose |
The title and description seem to suggest that this is a duplicate of #1564. The launchers, including "IDLE (Python GUI).exe", were rewritten between the WinPython 3.10.9 and WinPython 3.13.2 releases in a way that doesn't pass the file name to the respective invoked programs, IDLE in this case. There are PRs to fix the issue, but they haven't been merged yet due to the reason discussed in #1564 (also the same reason why the launcher was rewritten in the first place). |
rc 2 released, which fix the wppm --register of the rc1 of last night but normally, previous releases should have their "wppm --register" working ... unless subtelty with advantage of the re-engineer effort of this cycle: |
@stonebig, my understanding about the issue being reported is that if the reporter tries to open a Python source file with "Open with" → "IDLE (Python GUI).exe", the Python shell is shown, rather than the specific source file. That, as you're aware, is caused by #1564, not by whether registering or deregistering is working properly. The fact that the reporter even deleted the previous WinPython folder and the shell is still being shown suggests that the batch file is working correctly. |
haaaaaaaaaaa, I didn't figure that ""IDLE (Python GUI).exe" really meant using the launcher that way. So @firai is right: that feature was lost in the battle to get Anti-Virus happy. There is a chance we can bring back that feature on some launchers in next cycle, without affecting WinPython Anti-Virus social score, if we advance carefully (not like last year) Today Social score is : all anti-virus happy of all forms of build, .zip .7z, .exe , at the exception of "Bkav Pro" on the .exe builds. |
the "Drag & Drop" enabled launcher for IDLE is now in the repository |
but pre-test was not handling well spaces in the path... so there is no way. |
Some of these virus scanners are like random number generators. The launchers that I compiled using |
No doubt, yet the number of reds must stay low. |
This doesn't affect me personally since I now know how to compile (and have compiled) the launchers. I assume @lilpetamoix would want the IDLE launcher. I speculate that the IDLE, Jupyter Lab, Jupyter Notebook, Spyder and VS Code launchers are probably the most likely to be used with arguments by the wider community. The 4 WinPython prompt and interpreter launchers are probably less critical, and they also happen to give the most number of false positives from the files that I compiled. |
today, the same IDLE launcher raises 4 alarms, ... a downgrade vs an improvement.... for same hash256 |
Funnily enough, the IDLE launcher on my end doesn't trigger anything today. Microsoft also doesn't trigger on any of the launchers anymore, but Trellix now triggers on some launchers. 3 total on the interpreter, 2 and 1 for others. |
it can be that virustotal uses different servers, and they are not in synchronization. |
Sorry, just to be clear, the files I submitted are the files that I compiled, using a slightly later version of MSVC and probably a different version of the Windows SDK. |
I'm using the latest version on current channel, version 17.13.6. |
ok, updated... retrying |
so will try a b1 Drag&Drop for:
|
Which Windows SDK are you building against? |
It upgraded to 17.13.6 like you. |
reverted to non Drag&Drop for the IDLE launcher for now, to not degrade the social score |
trying to get Drag &Drop on Spyder, as it's need for "edi with" in fact, raising the CONSOLE or WINDOW variant and update VS:
|
with updated compiler chain, IDLE launcher is way more loved too:
|
Hello, I've recently downloaded 31320 and previously had 31090.
I've registered via command wppm --register.
I've tried opening a script file as usual, and selected open with "IDLE (Python GUI).exe".
However, doing so only opens the shell and not the script itself.
I made sure to unregister the prior version 31090, deleted the 31090 folder, and ran a registry cleaner to ensure there was no conflict with the prior version.
So I'm pretty sure I'm trying to open my scripts with version 31320 only, but open the script file with "IDLE (Python GUI).exe" doesn't open it and only opens the shell.
Is there a way to fix this issue?
The text was updated successfully, but these errors were encountered: