Looking at imaplib.py, class IMAP4, method open(),
there are two arguments, host and port, which are never
used in the method.  Instead, self.host and self.port
(set only in __init__) are used.  This gives a
misleading notion of what open() does.  I suggest that
these arguments be removed, because currently an IMAP4
object cannot be open()ed later by an external user,
i.e., open() is really private.

Logged In: YES 
user_id=80475

The two arguments are needed because open() can be 
overridden in a sub-class.

Suggest testing to see if arguments are supplied and using 
them instead of self.host and self.port.  See attached 
patch.

Logged In: YES 
user_id=265183

Looks OK, but shouldn't self.host and self.port be set if
they are specified in open()?  (Presumably in case another
method wants to use them.)  See attached alternative patch.

Logged In: YES 
user_id=6380

Hm, you seem to be right. Piers, what do you think?

Logged In: YES 
user_id=196212

It's a bug. One should definately be able to supply
alternate host and port values when using open() from
a sub-class. Will fix.

Logged In: YES 
user_id=196212

Updated imaplib.py containing new versions of open for IMAP4
and IMAP4_SSL classes checked into CVS.

NB: the "self.host" and "self.port" instance variables are redundant,
but I've retained them for the sake of backwards-compatibility.