This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: help asyncore recover from repr() probs
Type: Stage:
Components: Library (Lib) Versions: Python 2.3
process
Status: closed Resolution: out of date
Dependencies: Superseder:
Assigned To: jhylton Nosy List: gvanrossum, jhylton, loewis, skip.montanaro
Priority: normal Keywords: patch

Created on 2002-03-25 21:12 by skip.montanaro, last changed 2022-04-10 16:05 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
asyncore.diff skip.montanaro, 2002-03-25 21:12
Messages (4)
msg39348 - (view) Author: Skip Montanaro (skip.montanaro) * (Python triager) Date: 2002-03-25 21:12
I've had this patch my my copy of asyncore.py
for quite awhile.  It works for me as a way to
recover from repr() bogosities, though I'm
unfamiliar enough with repr/str issues and
asyncore to know if this is the right way to
make it more bulletproof (or if it should even be
made more bulletproof).

Skip
msg39349 - (view) Author: Guido van Rossum (gvanrossum) * (Python committer) Date: 2002-04-04 17:12
Logged In: YES 
user_id=6380

Jeremy, what do you think of this? Looks harmless to me...
msg39350 - (view) Author: Skip Montanaro (skip.montanaro) * (Python triager) Date: 2002-07-09 23:46
Logged In: YES 
user_id=44345

Looking for a vote up or down so I can get rid of the "M" when I execute
"cvs up"...

S
msg39351 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2002-08-14 15:11
Logged In: YES 
user_id=21627

That patch is out of date. In the code you replace, self is
not printed, so there is no need to protect against repr
failures. 
History
Date User Action Args
2022-04-10 16:05:09adminsetgithub: 36329
2002-03-25 21:12:21skip.montanarocreate