[issue9686] asyncore infinite loop on raise

2013-03-08 Thread Terry J. Reedy

Changes by Terry J. Reedy tjre...@udel.edu:


Removed file: http://bugs.python.org/file18647/unnamed

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



[issue9686] asyncore infinite loop on raise

2013-03-08 Thread Terry J. Reedy

Terry J. Reedy added the comment:

I am closing this because there is no identified, fixable implementation bug in 
any particular Python module.  The fix for the asyncore *design* will be a new, 
re-designed module.

--
nosy: +terry.reedy
resolution:  - invalid
status: open - closed

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



[issue9686] asyncore infinite loop on raise

2013-03-08 Thread Terry J. Reedy

Changes by Terry J. Reedy tjre...@udel.edu:


--
stage:  - committed/rejected

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



[issue9686] asyncore infinite loop on raise

2010-08-26 Thread Giampaolo Rodola'

Giampaolo Rodola' g.rod...@gmail.com added the comment:

I agree with you that asyncore API model is far from being robust and I've 
personally seen infinite recursion more than once if certain asyncore methods 
aren't properly subclassed.

What I don't understand is what changes you are proposing and, again, it would 
be very helpful if you could provide an example code which demonstrates the 
problems you're complaining about (infinite recursion? broken pipe error? 
both?).

--

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



[issue9686] asyncore infinite loop on raise

2010-08-25 Thread mmw

New submission from mmw 0xcafef...@gmail.com:

def send(self, data):
try:
result = self.socket.send(data)
return result
except socket.error, why:
if why.args[0] == EWOULDBLOCK:
return 0
elif why.args[0] in (ECONNRESET, ENOTCONN, ESHUTDOWN, ECONNABORTED):
self.handle_close()
return 0
else:
raise

for whatever reason the connection could break client side, if you raise an 
anonymous exception there it's uncatchable, raise on a socket.error or dismiss 
async chat is a looper.

that's the main reason why everybody gets this crazy infinite loop on for 
instance broken pipe error and the thing never exit, you just raise on 
your-self other and other again, 

BTW, you could have the same issue whatever the language, this is a developer 
bug.

--
components: Library (Lib)
messages: 114931
nosy: mmw
priority: normal
severity: normal
status: open
title: asyncore infinite loop on raise
versions: Python 2.7

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



[issue9686] asyncore infinite loop on raise

2010-08-25 Thread Raymond Hettinger

Raymond Hettinger rhettin...@users.sourceforge.net added the comment:

What change are you proposing?

--
nosy: +rhettinger

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



[issue9686] asyncore infinite loop on raise

2010-08-25 Thread Raymond Hettinger

Changes by Raymond Hettinger rhettin...@users.sourceforge.net:


--
assignee:  - giampaolo.rodola
nosy: +giampaolo.rodola

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



[issue9686] asyncore infinite loop on raise

2010-08-25 Thread Giampaolo Rodola'

Giampaolo Rodola' g.rod...@gmail.com added the comment:

Could you provide a code sample which demonstrates the problem?

--

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



[issue9686] asyncore infinite loop on raise

2010-08-25 Thread Giampaolo Rodola'

Changes by Giampaolo Rodola' g.rod...@gmail.com:


--
nosy: +josiah.carlson, josiahcarlson

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



[issue9686] asyncore infinite loop on raise

2010-08-25 Thread mmw

mmw 0xcafef...@gmail.com added the comment:

First it depends on the socket type but might use a select call, secondable
raise on a socket.error, thirdable you could call the close_handle with the
message and let the guys if he would like to retry, network connection might
be capricious especially for client connected through a wifi network or
behind some firewall blocking port

the asyncchat is a looper if you don't let him catch the exception you just
create an infinite loop, this API needs a stronger model.

On Wed, Aug 25, 2010 at 3:45 PM, Giampaolo Rodola'
rep...@bugs.python.orgwrote:


 Giampaolo Rodola' g.rod...@gmail.com added the comment:

 Could you provide a code sample which demonstrates the problem?

 --

 ___
 Python tracker rep...@bugs.python.org
 http://bugs.python.org/issue9686
 ___


--
Added file: http://bugs.python.org/file18647/unnamed

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9686
___First it depends on the socket type but might use a select call, secondable 
raise on a socket.error, thirdable you could call the close_handle with the 
message and let the guys if he would like to retry, network connection might be 
capricious especially for client connected through a wifi network or behind 
some firewall blocking portbr
brthe asyncchat is a looper if you don#39;t let him catch the exception you 
just create an infinite loop, this API needs a stronger 
model.br brbrdiv class=gmail_quoteOn Wed, Aug 25, 2010 at 3:45 PM, 
Giampaolo Rodola#39; span dir=ltrlt;a 
href=mailto:rep...@bugs.python.org;rep...@bugs.python.org/agt;/span 
wrote:br
blockquote class=gmail_quote style=border-left: 1px solid rgb(204, 204, 
204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;br
Giampaolo Rodola#39; lt;a 
href=mailto:g.rod...@gmail.com;g.rod...@gmail.com/agt; added the 
comment:br
br
Could you provide a code sample which demonstrates the problem?br
br
--br
divdiv/divdiv class=h5br
___br
Python tracker lt;a 
href=mailto:rep...@bugs.python.org;rep...@bugs.python.org/agt;br
lt;a href=http://bugs.python.org/issue9686; 
target=_blankhttp://bugs.python.org/issue9686/agt;br
___br
/div/div/blockquote/divbr
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com