[issue21519] IDLE : Bug in keybinding validity check

[Terry J. Reedy]

Terry J. Reedy added the comment:

Thanks for the patch.  The F3-missing bug has been fixed.

--
resolution:  -> fixed
stage: test needed -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21519] IDLE : Bug in keybinding validity check

[Terry J. Reedy]

Terry J. Reedy added the comment:


New changeset 93b88e995373c48713c9f7d4b32fe1d0166709e5 by terryjreedy in branch 
'3.6':
[3.6] bpo-21519: IDLE basic custom key entry better detects duplicates. 
(GH-2428) (#2433)
https://github.com/python/cpython/commit/93b88e995373c48713c9f7d4b32fe1d0166709e5


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21519] IDLE : Bug in keybinding validity check

[Terry J. Reedy]

Changes by Terry J. Reedy :


--
pull_requests: +2481

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21519] IDLE : Bug in keybinding validity check

[Terry J. Reedy]

Terry J. Reedy added the comment:


New changeset 44913e584bcf4e2a0e1a6372c304c2d5ea521fc6 by terryjreedy in branch 
'master':
bpo-21519: IDLE basic custom key entry better detects duplicates. (#2428)
https://github.com/python/cpython/commit/44913e584bcf4e2a0e1a6372c304c2d5ea521fc6


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21519] IDLE : Bug in keybinding validity check

[Terry J. Reedy]

Changes by Terry J. Reedy :


--
pull_requests: +2479

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21519] IDLE : Bug in keybinding validity check

[Terry J. Reedy]

Terry J. Reedy added the comment:

configdialog.ConfigDialog.getNewKeys() calls config_key.GetKeysDialog with a 
list of lists of one or more sequences (currentKeySequences).  
GetKeysDialog.KeysOK looks for keys.split() in currentKeySequences.  Since 
KeysOK on only called for the no-space 'keys' produced by the basic dialog, 
keys.split is always [keys].  This can only match one of the length-1 lists in 
currentKeySequences.

The patch semi-flattens the latter to a list of lists of 1 sequence each
.  But instead of looking for [keys] in the result, better and faster to omit 
the list wrappers and look for keys in a list or set of sequences.

A separate improvement would be to have a reverse map of sequences to 
pseudoevents, so the error message can specify the exact conflict instead of 
just saying 'some conflict'.  I have separately thought that the [keys] tab of 
ConfigDialog should be able to display such a mapping to help one plan a new 
key mapping.

Off topic for this issue: the keys tab could have a 'load key-def file' 
function that would check a definition and if ok, load it.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21519] IDLE : Bug in keybinding validity check

[Terry J. Reedy]

Terry J. Reedy added the comment:

#6739 is about rejecting *invalid* sequences, this is about rejecting a 
*duplicate* valid sequence.  Both fixes are needed.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21519] IDLE : Bug in keybinding validity check

[Terry J. Reedy]

Terry J. Reedy added the comment:

I believe patch affects same area of file as patch for #6739.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21519] IDLE : Bug in keybinding validity check

[Terry J. Reedy]

Terry J. Reedy added the comment:

#6739 also has a patch to refuse invalid key bindings.

--
assignee:  -> terry.reedy
versions: +Python 3.6, Python 3.7 -Python 2.7, Python 3.4

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24572] IDLE Bug

[Kevin Phillips (kmecpp)]

New submission from Kevin Phillips (kmecpp):

This appears to be a bug with IDLE that happens when printing out ASCII codes. 
I posted the issue to stackoverflow when I came accross it because I didn't 
know what the problem was, so there is a more detailed description of the 
there: http://stackoverflow.com/q/31235670/3476226

--
components: IDLE
files: python_bug.png
messages: 246343
nosy: Kevin Phillips (kmecpp)
priority: normal
severity: normal
status: open
title: IDLE Bug
type: behavior
versions: Python 3.4
Added file: http://bugs.python.org/file39873/python_bug.png

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24572
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21519] IDLE : Bug in keybinding validity check

[Terry J. Reedy]

Terry J. Reedy added the comment:

#6739 may also be relevant

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21519
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21519] IDLE : Bug in keybinding validity check

[Saimadhav Heblikar]

Saimadhav Heblikar added the comment:

A small bug in line 185 in keybindingDialog.py. 'F2' appears twice and 'F3' is 
missing. Since this is a typo, I did not create a new issue.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21519
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21519] IDLE : Bug in keybinding validity check

[Terry J. Reedy]

Terry J. Reedy added the comment:

 Now the Control-Key-C binding will be assigned to two actions.

I do not see this. I only see Control-Key-c duplicated, which is bad enough 
to be patched. What did you leave out ;-).

Also see #12387, which we need to finish, and Ned's link to  
http://wiki.tcl.tk/28331 

A patch for KeysOK should include test_bindings.py with class KeysOK_Test. As 
with the test of name_ok in test_configname.py (sp?), the method should be 
embedded in a dummy class and use a dummy message box.

The problem with the method goes deeper. It is not called if the 'advanced' 
(hand entry, therefore primitive) pane is used. As near as I can tell (and if I 
am wrong, please tell me), multiple bindings, which are required to ignore 
lower-upper case issues, can only be entered with this 'advanced' method. 
Hence, most new entries are not checked at all. The basic pane, which is 
advanced in that one can only enter possibly valid combination, should be 
modified to allow multiple entries. (The two panes should be called 'Easy' and 
'Error-prone ;-)

As it is, 'keys' is a misnomer[note], keys.strip() is a no-op in that 'keys' 
is auto-generated, and keySequence = keys.split() is the same as keySequence 
= [keys][note]. Many of the tests only test mistakes that can happen with 
hand-entry, which is not tested. I believe that the duplicate check is the only 
one needed (except possible for the modifier check, which I have not looked at 
enough to tell).

[note] If the easy pane were modified to define multiple keys, and all were 
passed at once, then the two noted lines would become valid, but then each key, 
would have to be tested individually against the flat list.

This suggests to me that the flattening should be done just once and that 
KeysOK should become KeyOK, or rather key_ok. It might even be replaced by 
newkey in flat_list or something nearly that simple.

--
stage:  - test needed

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21519
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21519] IDLE : Bug in keybinding validity check

[Saimadhav Heblikar]

New submission from Saimadhav Heblikar:

Steps to reproduce the bug:
1. IDLE  options  configure idle  keys

2. Try to replace a keybinding for an action with that of another action which 
has more than one keybinding.
For eg : Default binding of copy=Control-Key-c Control-Key-C.
So, try to replace any other keybinding with Control-Key-c

3. This change is accepted

Now the Control-Key-C binding will be assigned to two actions.

This bug only applies if the other action has more than one binding.
In case the other action has only one binding, an error is raised(as expected).


Attaching a patch to fix this issue.

--
components: IDLE
files: keybinding.diff
keywords: patch
messages: 218734
nosy: sahutd, terry.reedy
priority: normal
severity: normal
status: open
title: IDLE : Bug in keybinding validity check
type: behavior
versions: Python 2.7, Python 3.4
Added file: http://bugs.python.org/file35275/keybinding.diff

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21519
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Re: IDLE bug

[harrismh777]

Terry Reedy wrote:


Go ahead and report, noting which Linux distribution, and include my
negative report. Add me as nosy.


Done.  11896 created.
msg(s)  134194
134195


thanks
--
http://mail.python.org/mailman/listinfo/python-list

Re: IDLE bug

[rantingrick]

On Apr 18, 11:16 pm, James Mills prolo...@shortcircuit.net.au wrote:
 On Tue, Apr 19, 2011 at 2:05 PM, harrismh777 harrismh...@charter.net wrote:
  Are bug reports wanted here, or just in issue tracker?

 Pretty sure they're wanted in the Issue Tracker.

My opinion is to report bugs on the tracker AND here since this list
is viewed by more people than the bug tracker is. And the wider
community needs to know where the shortcomings of this language exist.

-- 
http://mail.python.org/mailman/listinfo/python-list

Re: IDLE bug

[Terry Reedy]

On 4/19/2011 12:05 AM, harrismh777 wrote:

Are bug reports wanted here, or just in issue tracker?


If one is somewhat experienced with Python and is sure about having 
identified a bug, and is willing to search the tracker for existing 
reports and respond to questions, then report on the tracker. If one is 
new to Python and perhaps not sure, or should not be sure, then I prefer 
that one ask here for a second opinion.


--
Terry Jan Reedy

--
http://mail.python.org/mailman/listinfo/python-list

Re: IDLE bug

[harrismh777]

Terry Reedy wrote:

If one is new to Python and perhaps not sure, or should not be sure,
then I prefer that one ask here for a second opinion.


Thanks Terry. I am not new to Python, but I am new to Python3, and I'm 
also relatively new to IDLE. Typically I edit with vi, test on the 
terminal, and run on the server. I have been using IDLE more these days, 
and also working more with Tk, so I've run into a couple little minor 
snags.  Anyway, sorry, I'm digressing a bit...as usual.


Here is the bug, for a second opinion:

Under some circumstances, which I will detail later down the note, if I 
click File -- Close without explicitly saving, and without running the 
module with Run -- Run Module , then the last changes I made to the 
file do not get saved. The save dialogue pop-up does appear, and I do 
select YES--- I want to save before closing--- but when I re-open the 
file (IDLE or vi) the changes are not there... as though the save 
binding did not work, or like there was some timing glitch that 
prevented the save somehow before the edit window closed down. The error 
is not solid, in that, if the file is larger (significantly) then the 
File -- Close (select Yes on the dialogue) does work... ??


The work around is to do either 1) run the module, or 2) explicitly 
click File -- Save.


The alleged bug can be reproduced on both of my primary desk machines, 
Linux systems, using IDLE on 2.6, 2.7, and 3.2/  These are the 
instructions for reproducing this little snag:


1) Open a new edit window with File -- New Window

2) Enter the following code on the first two lines:
def testfunc():
return None

3) Click File -- Save( testit.py )

4) Click File -- Close

5) Open the file with  File -- Recent Files   ( select testit.py )

6) Use the edit window to place these three lines above testfunc:

# comment block
##

7) ClickFile -- Close

8) When the Save on Close dialogue appears select Yes

9) Re-open the file with   File -- Recent Files   ( select testit.py )

10) The comment block will not be there...  didn't save.


Well, there it is. Of course I must admit, I've used IDLE for months 
without ever noticing this, so its really a nit... if I'm doing 
something incorrect, let me know.  If it is something I can fix myself 
let me know that too... I've compiled 2.7 and 3.2 from sources, 2.6 came 
installed on my distro... which is another point to bring up actually, 
because all three of them are using the same Tk libraries (8.5.x)


Thanks Terry.

kind regards,
m harris



--
http://mail.python.org/mailman/listinfo/python-list

Re: IDLE bug

[Terry Reedy]

On 4/19/2011 11:39 PM, harrismh777 wrote:

Terry Reedy wrote:

If one is new to Python and perhaps not sure, or should not be sure,
then I prefer that one ask here for a second opinion.


Thanks Terry. I am not new to Python, but I am new to Python3, and I'm
also relatively new to IDLE. Typically I edit with vi, test on the
terminal, and run on the server. I have been using IDLE more these days,
and also working more with Tk, so I've run into a couple little minor
snags. Anyway, sorry, I'm digressing a bit...as usual.

Here is the bug, for a second opinion:

Under some circumstances, which I will detail later down the note, if I
click File -- Close without explicitly saving, and without running the
module with Run -- Run Module , then the last changes I made to the
file do not get saved. The save dialogue pop-up does appear, and I do
select YES--- I want to save before closing--- but when I re-open the
file (IDLE or vi) the changes are not there... as though the save
binding did not work, or like there was some timing glitch that
prevented the save somehow before the edit window closed down. The error
is not solid, in that, if the file is larger (significantly) then the
File -- Close (select Yes on the dialogue) does work... ??

The work around is to do either 1) run the module, or 2) explicitly
click File -- Save.

The alleged bug can be reproduced on both of my primary desk machines,
Linux systems, using IDLE on 2.6, 2.7, and 3.2/ These are the
instructions for reproducing this little snag:

1) Open a new edit window with File -- New Window

2) Enter the following code on the first two lines:
def testfunc():
return None

3) Click File -- Save ( testit.py )

4) Click File -- Close

5) Open the file with File -- Recent Files ( select testit.py )

6) Use the edit window to place these three lines above testfunc:

# comment block
##

7) Click File -- Close

8) When the Save on Close dialogue appears select Yes

9) Re-open the file with File -- Recent Files ( select testit.py )

10) The comment block will not be there... didn't save.


On my winxp, following the above *exactly*, the comment block is there. 
But I can believe there might be a system specific glitch around save 
and close. See

http://bugs.python.org/issue9803
http://bugs.python.org/issue10365

Go ahead and report, noting which Linux distribution, and include my 
negative report. Add me as nosy.


--
Terry Jan Reedy

--
http://mail.python.org/mailman/listinfo/python-list

IDLE bug

[harrismh777]

Are bug reports wanted here, or just in issue tracker?

thanks

--
http://mail.python.org/mailman/listinfo/python-list

Re: IDLE bug

[James Mills]

On Tue, Apr 19, 2011 at 2:05 PM, harrismh777 harrismh...@charter.net wrote:
 Are bug reports wanted here, or just in issue tracker?

Pretty sure they're wanted in the Issue Tracker.

cheers
James

-- 
-- James Mills
--
-- Problems are solved by method
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: IDLE bug

[Westley Martínez]

On Mon, 2011-04-18 at 23:05 -0500, harrismh777 wrote:
 Are bug reports wanted here, or just in issue tracker?
 
 thanks
 

If it's a super-critical bug that can destroy data, yes, else just the
issue tracker.

-- 
http://mail.python.org/mailman/listinfo/python-list

[ python-Bugs-1179168 ] IDLE bug - changing shortcuts - Shift-Tab broken!

[SourceForge.net]

Bugs item #1179168, was opened at 2005-04-08 07:54
Message generated for change (Settings changed) made by kbk
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=105470aid=1179168group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: IDLE
Group: None
Status: Closed
Resolution: Fixed
Priority: 6
Submitted By: Przemys#322;aw Gocy#322;a (bld_d16)
Assigned to: Kurt B. Kaiser (kbk)
Summary: IDLE bug - changing shortcuts - Shift-Tab broken!

Initial Comment:
On Python 2.4.1 on WinXP I have changed keyboard 
shortcut settings for indent/unindent.
New shorcut was Tab/Shift+Tab.

When I did it IDLE hanged up and I could not to launch it 
again.

I have tried everything. Uninstall whole Python and then 
reinstall (tried both version 2.3 and 2.4).
It just looks like from the change of shortcuts IDLE don't 
works.

I tried to:
  import idlelib.PyShell
  idlelib.PyShell.main()
and result with bug are in attachment

Where is the information about IDLE shortcuts keeped ?
Why IDLE remember this even after reinstall ?
How to fix it up?

Best regards,
Przemek

--

Comment By: Kurt B. Kaiser (kbk)
Date: 2006-07-18 00:05

Message:
Logged In: YES 
user_id=149084

rev 50695

--

Comment By: Kurt B. Kaiser (kbk)
Date: 2005-04-14 16:58

Message:
Logged In: YES 
user_id=149084

Your user keyset config file on Windows is at
Documents and Settings\YourUserName\.idlerc\config-keys.cfg
This file doesn't get removed when Python is uninstalled.

Open this file with a text editor and find the Key-tab entry.
Change it to Key-Tab

This is a bug in IDLE.  (normally people don't try to re-assign
the tab key, so it got missed)

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=105470aid=1179168group_id=5470
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[ python-Bugs-1179168 ] IDLE bug - changing shortcuts - Shift-Tab broken!

[SourceForge.net]

Bugs item #1179168, was opened at 2005-04-08 07:54
Message generated for change (Settings changed) made by kbk
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=105470aid=1179168group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: IDLE
Group: None
Status: Open
Resolution: None
Priority: 6
Submitted By: Przemys#322;aw Gocy#322;a (bld_d16)
Assigned to: Kurt B. Kaiser (kbk)
Summary: IDLE bug - changing shortcuts - Shift-Tab broken!

Initial Comment:
On Python 2.4.1 on WinXP I have changed keyboard 
shortcut settings for indent/unindent.
New shorcut was Tab/Shift+Tab.

When I did it IDLE hanged up and I could not to launch it 
again.

I have tried everything. Uninstall whole Python and then 
reinstall (tried both version 2.3 and 2.4).
It just looks like from the change of shortcuts IDLE don't 
works.

I tried to:
  import idlelib.PyShell
  idlelib.PyShell.main()
and result with bug are in attachment

Where is the information about IDLE shortcuts keeped ?
Why IDLE remember this even after reinstall ?
How to fix it up?

Best regards,
Przemek

--

Comment By: Kurt B. Kaiser (kbk)
Date: 2005-04-14 16:58

Message:
Logged In: YES 
user_id=149084

Your user keyset config file on Windows is at
Documents and Settings\YourUserName\.idlerc\config-keys.cfg
This file doesn't get removed when Python is uninstalled.

Open this file with a text editor and find the Key-tab entry.
Change it to Key-Tab

This is a bug in IDLE.  (normally people don't try to re-assign
the tab key, so it got missed)

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=105470aid=1179168group_id=5470
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[ python-Bugs-1179168 ] IDLE bug - changing shortcuts

[SourceForge.net]

Bugs item #1179168, was opened at 2005-04-08 06:54
Message generated for change (Comment added) made by kbk
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=105470aid=1179168group_id=5470

Category: IDLE
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Przemys#322;aw Gocy#322;a (bld_d16)
Assigned to: Kurt B. Kaiser (kbk)
Summary: IDLE bug - changing shortcuts

Initial Comment:
On Python 2.4.1 on WinXP I have changed keyboard 
shortcut settings for indent/unindent.
New shorcut was Tab/Shift+Tab.

When I did it IDLE hanged up and I could not to launch it 
again.

I have tried everything. Uninstall whole Python and then 
reinstall (tried both version 2.3 and 2.4).
It just looks like from the change of shortcuts IDLE don't 
works.

I tried to:
  import idlelib.PyShell
  idlelib.PyShell.main()
and result with bug are in attachment

Where is the information about IDLE shortcuts keeped ?
Why IDLE remember this even after reinstall ?
How to fix it up?

Best regards,
Przemek

--

Comment By: Kurt B. Kaiser (kbk)
Date: 2005-04-14 15:58

Message:
Logged In: YES 
user_id=149084

Your user keyset config file on Windows is at
Documents and Settings\YourUserName\.idlerc\config-keys.cfg
This file doesn't get removed when Python is uninstalled.

Open this file with a text editor and find the Key-tab entry.
Change it to Key-Tab

This is a bug in IDLE.  (normally people don't try to re-assign
the tab key, so it got missed)

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=105470aid=1179168group_id=5470
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[ python-Bugs-1179168 ] IDLE bug - changing shortcuts

[SourceForge.net]

Bugs item #1179168, was opened at 2005-04-08 13:54
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=105470aid=1179168group_id=5470

Category: IDLE
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Przemys#322;aw Gocy#322;a (bld_d16)
Assigned to: Nobody/Anonymous (nobody)
Summary: IDLE bug - changing shortcuts

Initial Comment:
On Python 2.4.1 on WinXP I have changed keyboard 
shortcut settings for indent/unindent.
New shorcut was Tab/Shift+Tab.

When I did it IDLE hanged up and I could not to launch it 
again.

I have tried everything. Uninstall whole Python and then 
reinstall (tried both version 2.3 and 2.4).
It just looks like from the change of shortcuts IDLE don't 
works.

I tried to:
  import idlelib.PyShell
  idlelib.PyShell.main()
and result with bug are in attachment

Where is the information about IDLE shortcuts keeped ?
Why IDLE remember this even after reinstall ?
How to fix it up?

Best regards,
Przemek

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=105470aid=1179168group_id=5470
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

sys.stdin and idle bug?

[Jason B Burke]

Greetings All,

I apologize if this has been brought up before, but
I'm having a small issue with the handling of sys.stdin
in Idle.

I'm using a routine to mimic the c library function 
getch(), to get a single character from the keyboard.
The function works in the standard python shell, but
in Idle I get an error when I try to reference sys.stdin.fileno().

Within the standard shell sys.stdin is a file object with
a mode of 'r'. Looks like this in the interpreter:

open file 'stdin', mode 'r' at 0xSome_address

However, in Idle the object is quite different:

idlelib.rpc.RPCProxy instance at 0xSome_address

and typing sys.stdin.fileno() returns an AttributeError: fileno.

Is this a bug in idle, or is this normal? If it's normal is
there a work around for it?

Thanks for any replies and references to more info
on this issue.

Sincerely,

Jason Burke-- 
http://mail.python.org/mailman/listinfo/python-list