> On Dec 31, 2019, at 10:45 AM, Tal Einat <talei...@gmail.com> wrote:
>
> Hi David,
>
> I'm very happy that you and your son are finding IDLE useful for learning
> programming with Python!
>
> On Tue, Dec 31, 2019 at 8:22 PM David <david.lin...@gmail.com
> <mailto:david.lin...@gmail.com>> wrote:
> I have two things I would like to see in future versions:
>
> 1. The ability to build executables directly from IDLE
> -- pyinstaller works on my sons Win10 system, but is a bit hard to
> install. On my Linux Mint 19.3 system, pyinstaller is easily installed, but
> does not make functioning executables. It would be very nice to have this
> feature in IDLE, as it would make it a more complete IDE.
>
> With IDLE being part of the Python standard library, it can't depend on other
> modules in standard library, and there are no such tools in the stdlib. I
> also don't foresee something like that being added to the stdlib any time
> soon.
>
> This would be a great IDLE extension through! If you, or anyone else, would
> like to take this up as a project, I'd be happy to provide guidance and
> support.
>
> 2. A startup option to open both Editor and Shell side by side, full extent.
>
> This is the first time someone has asked for this, as far as I know. You're
> welcome to open an issue on bugs.python.org <http://bugs.python.org/> with
> this suggestion, where it can be further discussed and worked on.
>
> I personally think it would be unlikely for this to be added, since it
> appears to be a rather minor convenience, but at the same time depending on
> the quirks of OS window managers, which tend to change over time and cause
> lots of maintenance headaches. On the other hand, sometimes it's possible to
> come up with an alternative feature which would provide similar benefits.
>
> BTW, have you tried hacking this up with an external tool, e.g. AutoHotKey
> for Windows?
>
> - Tal Einat
> _______________________________________________
Hi Tal,
I use IDLE in all the Python classes I teach. It's great for beginning
students.
With regard to the second item above, I would like to point out something odd,
and request a hopefully minor change in IDLE. I am using IDLE 3.7.3 (with
Python 3.7.3) on a Mac. I have my Mac set up so that when I double-click on a
Python source file, IDLE opens. When I double-click on a Python file in the
Finder, both the Shell and the source file open in separate windows. However,
when this happens, the Shell is given focus, then the source file opens (often
covering the Shell window). Therefore, I must click on the source file window
to give it keyboard focus before I can run or edit the file.
I think it would be more appropriate to give focus to the chosen source file
window instead. My thinking is that if I select a Python file that I want to
edit or run, then the window associated with that file should be given initial
focus rather than the Shell window.
(FYI: If IDLE is already open, and I go to the Mac Finder and double-click on
another Python file, then that file opens in IDLE and *is* given focus.)
My use case might be slightly different than most because I do a lot of grading
of student homework files. I will typically download a student's assignment,
double-click on it, and press F5 to run it - and nothing happens. That's
because the Shell has focus instead of the student's file. I find myself
running into this (seemingly minor problem) multiple times every day. If it is
a simple change to give focus to the selected Python source file, I would
greatly appreciate it.
(If you would like me to fill out a bug report for this, I would be glad to do
that.)
Irv
_______________________________________________
IDLE-dev mailing list
IDLE-dev@python.org
https://mail.python.org/mailman/listinfo/idle-dev
