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
3.9 IDLE documentation. #86134
Comments
|
https://docs.python.org/3/library/idle.html |
|
I am not touching the issue nosy and components for now but suspect this is a Windows installation issue. As you said, there is no
I agree it may be nice to give a brief overview on IDLE's "behind-the-scenes" though I am slightly confused why you raised this issue as a documentation issue. |
|
I agree that the doc needs more, but I am closing this as a duplicate of bpo-31329, which is specifically doc about starting IDLE. You can still answer Paine's questions here if you want. File association: IDLE is not Python. It is one of many Python-oriented editors and IDEs. .py files are and by default should be associated for running with something that runs the file with python.exe. On Windows, this is done via C:/Windows/py.exe. The default version for double clicking is determined by a checkmark in the installer. The Windows installer does associate .py files with IDLE for editing: rt click, edit with IDLE .... idle.exe is not needed for starting idle. I don't know what you mean by 'source format'. IDLE is written in Python. The directory structure is mostly implementation detail not relevant to using IDLE. File are described in idlelib/README.txt. This might be mentioned in the doc. |
|
As Terry said, the issue of Idle not starting by a .py file association was This post was specifically about the documentation. One of the So I went to the IDLE documentation page to find how IDLE was implemented I apologise for the confusion. However in the past, I had a similar On Thu, 8 Oct 2020 at 01:07, Terry J. Reedy <report@bugs.python.org> wrote:
|
|
Paine: thank you for your offer to sort the problem out. My laptop's operating system Win10 64 bit was mashed by Windows update I have installed 3.9 for all users and clicking the PATH box, and on I had gone to the documentation page to sort the problem myself, but that You have made clear that it is not really a Python issue, but my initial Thank you On Wed, 7 Oct 2020 at 18:20, E. Paine <report@bugs.python.org> wrote:
|
|
Velson, when you respond to a post by email, rather than on the web page, please delete the post you are responding to, except for maybe a quoted line or two. When your response is added to the web page below previous posts, posts quoted in full constitute noise that makes the stream of posts harder to read. I forgot to mention above that I added a link to this issue on bpo-31329 so that when I work on that, I will be reminded to read comments here also. IDLE is intended for learning to write Python programs and to develop programs that can be run directly with Python, without IDLE. It is not intended for production runs (though there are a few cases where that might be sensible). So, to run with IDLE, edit with IDLE and hit F5. I installed 3.9.0 with the python.org Windows installer and clicked "[X] make this default" (or however that is worded, top of second page, I believe). Double-clicking file.py or right-clicking and clicking Open runs the file with C:/Windows/py.exe, as I said in my first response. py.exe then runs the file with the default python.exe. Right-click also shows Edit with IDLE and a choice of versions. To get this on your system, you probably best delete all pythons on your system and start over with the python.org installer. For any more help on installing and using Python, please post to the python-list mail list. |
|
If you had a bad update, it is likely your registry is corrupt. If at all possible, I would recommend a Windows reinstall (it is quite likely other software has also been affected). However, in the past I have had similar problems and the Python installer does seem particularly susceptible to problems if corruption occurs (I resolved this without a Windows reinstall by uninstalling Python then deleting all registry entries related to it - though I would not recommend this more generally). I may take this up with Steve (in a separate issue) to see if we can make the installer more resilient. |
cvhorie mannequin commentedOct 7, 2020
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: