Ok, I'll try to take a look at all asyncore/chat reports and try to summarize them by splitting patches which solve bugs and patches which add enhancements or functionalities. On 14 Feb, 16:12, "Facundo Batista" <facundobati... at gmail.com> wrote: > 2008/2/14, Giampaolo Rodola' <gne... at gmail.com>: > > > asyncore and asynchat are in a difficult position right now since a > > lot of patches for both modules are pending and no decisions are > > taken. > > In detail I'm talking about patches 1519, 1541, 2073 and 1736190 which > > is the most important one since it includes a lot of fixes for other > > reported issues (e.g. 1740572, 1736101, 909005). > > I took a look to some of these in other opportunity, and IIRC, the > main issue here is exactly what you say: lots of issues with problem > *and* fixes, but some decisions needs to be taken. > > No decision taken, the pile of issues (and real problems behind them) > accumulate through time. I think it's a good idea to bring this > discussion here, and with luck a result will come up regarding them. > > So, it would be great if you (please) summarize here the problems > behind those issues and the decisions that must be taken... Thanks! > > Regards, > > -- > . Facundo > > Blog:http://www.taniquetil.com.ar/plog/ > PyAr:http://www.python.org/ar/ > _______________________________________________ > Python-Dev mailing list > Python-... at python.orghttp://mail.python.org/mailman/listinfo/python-dev > Unsubscribe:http://mail.python.org/mailman/options/python-dev/python-dev2-garchiv...
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4