On Thu, Jul 3, 2008 at 6:42 AM, Mark Hammond <[EMAIL PROTECTED]> wrote:
> For people on Windows, win32 isn't a "compatibility" consideration. I
> suspect most users of the other platforms MAL mentioned and all others with
> their own native unicode implementations would agree.
I'm sorry, but you'
On Thu, Jul 3, 2008 at 5:39 AM, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> 1. If you are advocating disallowing the use of characters outside the BMP
> in a UCS-2 build, enumerate the advantages of doing so (paying particular
> attention to any advantages which cannot be obtained simply by using an
First of all, you're conflating my two possible patches.
One patch just addresses the problem of strings and bytes, as GvR
asked me to do, and adds an 8-line class called iterator_producer that
adapts iterators into producers. The patch doesn't change how the
module works at all, and iterator_prod
They applied when posted them, but subsequent patches seem to have
broken them. I've now posted updated patches that apply cleanly
against revision 60780.
On Feb 13, 2008 6:52 PM, Bill Janssen <[EMAIL PROTECTED]> wrote:
> It's a big patch, but I'll try applying it to the current py3k branch
> -- d
A while back, I volunteered to update asyncore and asynchat for py3k.
I posted a patch, and in response to feedback posted a more
complicated patch+modification.
Both versions have been languishing at
http://bugs.python.org/issue1563 for a couple of months now without
any further feedback or actio
On Tue, 15 Jan 2008 06:57:02 -0500, Kevin Jacobs wrote:
> On Jan 15, 2008 6:24 AM, Oleg Broytmann <[EMAIL PROTECTED]> wrote:
>
> > On Mon, Jan 14, 2008 at 11:41:47PM +, Jon Ribbens wrote:
> > > It makes sense, but personally I have never heard before of ~/.local.
> > > Whereas ~/bin is somethin
> From: "Giampaolo Rodola'" <[EMAIL PROTECTED]>
> I remembered right now that there's a patch pending which should be
> included in the trunk before solving issues related to py3k and/or
> applying other changes:
> http://bugs.python.org/issue1736190
> Since it solves a lot of older and newer async
I've posted a new patch with the documentation for handle_expt and
handle_error adjusted, thanks to the feedback from Giampaolo Rodola
and James Y Knight.
http://bugs.python.org/issue1563
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.pyth
> "Josiah Carlson" <[EMAIL PROTECTED]> wrote:
> On Dec 5, 2007 9:19 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> > The asyncore and asynchat modules are in a difficult position when it
> > comes to Python 3000. None of the core developers use it or
> > particularly care about it (AFAIK), and t
Guido van Rossum wrote:
> The asyncore and asynchat modules are in a difficult position when it
> comes to Python 3000. None of the core developers use it or
> particularly care about it (AFAIK), and the API has problems because
> it wasn't written to deal with bytes vs. unicode. E.g. in
> http://b
10 matches
Mail list logo
