I installed Python 2.7RC1 on Mac OS X 10.6.3 and tried my script and it
worked for me. Imaplib throws the right exception instead of looping
forever:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "imapmail/explore/test2.py", line 30, in f
    server.select("INBOX")
  File
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/imaplib.py",
line 642, in select
    typ, dat = self._simple_command(name, mailbox)
  File
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/imaplib.py",
line 1060, in _simple_command
    return self._command_complete(name, self._command(name, *args))
  File
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/imaplib.py",
line 890, in _command_complete
    raise self.abort('command: %s => %s' % (name, val))
imaplib.abort: command: SELECT => socket error: EOF
>>>

On Wed, Jun 16, 2010 at 6:12 PM, Shashwat Anand <report@bugs.python.org>wrote:

>
> Shashwat Anand <anand.shashwat@gmail.com> added the comment:
>
> "import imaplib
>
> HOST="imap.gmail.com"
> PORT=993
> USERNAME="username@gmail.com"
> PASSWORD="password"
>
> server = imaplib.IMAP4_SSL(host=HOST, port=PORT)
> server.login(USERNAME, PASSWORD)
>
> def f():
>        print server.select("INBOX")
>        print server.uid("FETCH", "1:*", "(UID FLAGS BODY.PEEK[HEADER.FIELDS
> (Subject)])")
>
> Call the f() function and then wait about about an hour. Call f() again and
> server.select() will not return but take all CPU."
>
> Tried to reproduce this on Python 2.7RC1. Seemed Ok to me. Took some 3
> seconds to call f() not only once, but twice, thrice.
>
> ----------
> nosy: +l0nwlf
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue9010>
> _______________________________________
>