[ python-Bugs-1595742 ] SocketServer allow_reuse_address checked in constructor

SourceForge.net noreply at sourceforge.net
Fri Nov 17 04:28:15 CET 2006


Bugs item #1595742, was opened at 2006-11-13 11:54
Message generated for change (Comment added) made by parente
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1595742&group_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: Python Library
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Peter Parente (parente)
Assigned to: Nobody/Anonymous (nobody)
Summary: SocketServer allow_reuse_address checked in constructor

Initial Comment:
Python 2.4.3 (#1, Oct  1 2006, 18:00:19)
[GCC 4.1.1 20060928 (Red Hat 4.1.1-28)] on linux2

The documentation in the SocketServer class indicates
that the allow_reuse_address flag may be set on a
SocketServer subclass *or instance.* However, the flag
is read in a call to the server_bind() from the
constructor of the server object. Therefore, setting
the flag on a created instance has no effect. This is
problematic when trying to set the flag on
SimpleXMLRPCServer instances, for instance, which are
often not subclassed.

This flag should probably become one of the keyword
arguments in the constructor of a SocketServer object.

----------------------------------------------------------------------

>Comment By: Peter Parente (parente)
Date: 2006-11-16 22:28

Message:
Logged In: YES 
user_id=624776
Originator: YES

Will do.

----------------------------------------------------------------------

Comment By: Georg Brandl (gbrandl)
Date: 2006-11-15 12:34

Message:
Logged In: YES 
user_id=849994
Originator: NO

Would you want to work on a patch for this?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1595742&group_id=5470


More information about the Python-bugs-list mailing list