homepage

This patch addresses the point brought up in the
following post on IDLE-dev by Gregor Lingl. I support
this change and nobody raised an objection.
"
The firewall warning message in the Pythonshell window
was introduced in Python 2.3 (IDLE 1.0 or something
similar?)
I remember well the problems, which have been occurred
then, and
to which it was the answer. (If I remember correctly I was
involved in the discussion thread which led to the
introduction
of that message.)
Since more than three years I've used IDLE on many
different
systems and I didn't encounter a single Firewall
warning since
then. (It seems that firewalls nowadays are not offended by
the use of 127.0.0.1)
Therefore, and because the message is long and ugly,
I'd like to
suggest to delete it from the Python Shell window
and - if considered necessary - for instance to put
it into the IDLE Help - "About IDLE" submenu or
in a special IDLE-Firewall warning submenu of IDLE-Help.
Please observe that it pops up thousands of times and it's
read at most once.
Additional remark (about my personal interest):
I have to do a lot of IDLE-screenshots for a textbook
on programming and I really don't like it to occur on
all those screenshots.
"

Updated (use newer patch file instead of the original):
* Uses new textView utility functions (see patch 1718043)
* Diff relative to Rev. 55290
File Added: IDLE_firewall_warning.070513.patch

I think it would be better if a dialog popped up (before
trying to set up the subprocess!) with the warning. It 
should have a checkbox, "Don't show this again." And it
should be something we can reuse in other situations.
Store a tag in the user's .idlerc if he doesn't want to see it 
again....

What if this message was made part of the error message which is
displayed when the connection to the subprocess fails? This way only
users in situations where it is likely that the warning is relevant will
see it.
I suggest this since the original problem for which the warning was
added has become very uncommon, so bugging all of our users with such a
warning (even if it has a "don't show this again" check-box) seems
unnecessary.