[issue1563] asyncore and asynchat incompatible with Py3k str and bytes

R. David Murray added the comment: Since no doc only patch has been proposed and there is some disagreement as to whether it is needed anyway, I'm closing this per msg88559. -- resolution: -> out of date stage: -> committed/rejected status: open -> closed ___

[issue1563] asyncore and asynchat incompatible with Py3k str and bytes

Changes by R. David Murray : Removed file: http://bugs.python.org/file11018/unnamed ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue1563] asyncore and asynchat incompatible with Py3k str and bytes

Jean-Paul Calderone added the comment: > It's not, I was more thinking of push_str(foo), where it uses a default encoding. I think some people don't know what unicode or encoding is, or don't want to worry about it. Nice as it sounds, the problem with this is that those people cannot write corr

[issue1563] asyncore and asynchat incompatible with Py3k str and bytes

Jorrit Posthuma added the comment: On 13 jul 2009, at 17:33, Jean-Paul Calderone wrote: > > Jean-Paul Calderone added the comment: > >> It's not 'that' clear you should only work with bytes on a socket. > > It's pretty clear to me. :) That's what sockets can deal with - > bytes. It's allso

[issue1563] asyncore and asynchat incompatible with Py3k str and bytes

Jean-Paul Calderone added the comment: > It's not 'that' clear you should only work with bytes on a socket. It's pretty clear to me. :) That's what sockets can deal with - bytes. If you want to transfer something other than bytes via a socket, then you need to convert it to bytes. In the ca

[issue1563] asyncore and asynchat incompatible with Py3k str and bytes

Jorrit Posthuma added the comment: It's not 'that' clear you should only work with bytes on a socket. Especially not when using a wrapper like asynchat. They are supposed to make it easier, and passing a string is easier. Maybe it's possible to do a default byte conversion when the user is wo

[issue1563] asyncore and asynchat incompatible with Py3k str and bytes

Josiah Carlson added the comment: You can probably close this unless someone says otherwise. asyncore/asynchat work in Python 3.0+, as long as only bytes are passed. As of right now, this is a request for documentation stating "you can only send/receive bytes"...which may be implicit with t

[issue1563] asyncore and asynchat incompatible with Py3k str and bytes

R. David Murray added the comment: Reducing priority since the critical issues seem to have been resolved already. Also retargeting for 3.2 since 3.1 is about to go rc. -- nosy: +r.david.murray priority: critical -> normal versions: +Python 3.2 -Python 3.0

[issue1563] asyncore and asynchat incompatible with Py3k str and bytes

Changes by intgr : -- nosy: +intgr ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailma

[issue1563] asyncore and asynchat incompatible with Py3k str and bytes

Josiah Carlson <[EMAIL PROTECTED]> added the comment: Sounds good. I look forward to seeing the patch :) . ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue1563] asyncore and asynchat incompatible with Py3k str and bytes

Daniel Arbuckle <[EMAIL PROTECTED]> added the comment: As of December 2007, Guido did not believe that you or anyone else cared enough about asyncore/asynchat to update them to py3k: http://mail.python.org/pipermail/python-dev/2007-December/075574.html Thankfully there's been a resurgence of act

[issue1563] asyncore and asynchat incompatible with Py3k str and bytes

Josiah Carlson <[EMAIL PROTECTED]> added the comment: Asyncore and asynchat are not going to be removed, and were not being seriously discussed as being removable in Python 3.0 since January of 2007 when I took over maintenance. If there was a miscommunication in an email thread on python-3000 o

[issue1563] asyncore and asynchat incompatible with Py3k str and bytes

Daniel Arbuckle <[EMAIL PROTECTED]> added the comment: > From what I understand, the OP wants to be able to pass unicode strings > across a network connection. That's incorrect. At the time I formulated this patch, asyncore/asynchat were slated for removal from the standard lib unless somebody

[issue1563] asyncore and asynchat incompatible with Py3k str and bytes

Josiah Carlson <[EMAIL PROTECTED]> added the comment: The current revision of 3.0 handles the case where reading from the socket returns a Python 3.0 str object, which it then translates into bytes objects. This is sufficient for passing the 3.0 unittests. See asynchat.async_chat.use_encoding a

[issue1563] asyncore and asynchat incompatible with Py3k str and bytes

Bill Janssen <[EMAIL PROTECTED]> added the comment: Thanks. I'll read it. Bill On Thu, Jul 31, 2008 at 6:16 AM, Daniel Arbuckle <[EMAIL PROTECTED]>wrote: > > Daniel Arbuckle <[EMAIL PROTECTED]> added the comment: > > I'll update the patch and post it again. > > ___

[issue1563] asyncore and asynchat incompatible with Py3k str and bytes

Daniel Arbuckle <[EMAIL PROTECTED]> added the comment: I'll update the patch and post it again. ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Py

[issue1563] asyncore and asynchat incompatible with Py3k str and bytes

Giampaolo Rodola' <[EMAIL PROTECTED]> added the comment: Now that the major bugs have been fixed I think this patch needs to be re-adapted to the new asynchat.py currently available in the trunk. ___ Python tracker <[EMAIL PROTECTED]>

[issue1563] asyncore and asynchat incompatible with Py3k str and bytes

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Any progress? -- assignee: -> josiahcarlson nosy: +benjamin.peterson, josiahcarlson ___ Python tracker <[EMAIL PROTECTED]> ___

[issue1563] asyncore and asynchat incompatible with Py3k str and bytes

Changes by Brett Cannon <[EMAIL PROTECTED]>: -- priority: normal -> critical __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list

[issue1563] asyncore and asynchat incompatible with Py3k str and bytes

Changes by Daniel Arbuckle: Added file: http://bugs.python.org/file9428/asyn_py3k_restructured.diff __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-li

[issue1563] asyncore and asynchat incompatible with Py3k str and bytes

Changes by Daniel Arbuckle: Added file: http://bugs.python.org/file9427/asyn_py3k.diff __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing li

[issue1563] asyncore and asynchat incompatible with Py3k str and bytes

Changes by Bill Janssen: -- nosy: +janssen __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue1563] asyncore and asynchat incompatible with Py3k str and bytes

Josiah Carlson added the comment: The patches that giampaolo sent you were for 2.x, not 3.x . Arguably they should be applied to 2.6 first, tested, etc., then be run through the 2.6 to 3.0 converter, then adjusted for str/bytes stuff. One of my concerns with your changes (which are hard to work

[issue1563] asyncore and asynchat incompatible with Py3k str and bytes

Giampaolo Rodola' added the comment: There's a patch pending which should be included in the 2.6 trunk before solving issues related to py3k and/or applying other changes, imho: http://bugs.python.org/issue1736190 -- nosy: +giampaolo.rodola __ Tracker <[

[issue1563] asyncore and asynchat incompatible with Py3k str and bytes

Changes by Christian Heimes: -- keywords: +py3k priority: -> normal __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubs

[issue1563] asyncore and asynchat incompatible with Py3k str and bytes

New submission from Daniel Arbuckle: [EMAIL PROTECTED] is working up a patch for this. -- components: Library (Lib) messages: 58251 nosy: djarb severity: normal status: open title: asyncore and asynchat incompatible with Py3k str and bytes type: behavior versions: Python 3.0 ___