I'm actually assuming to put this off until 2.6 anyway. On 2/15/06, Fredrik Lundh <[EMAIL PROTECTED]> wrote: > Thomas Wouters wrote: > > > > After reading some of the discussion, and seen some of the arguments, > > > I'm beginning to feel that we need working code to get this right. > > > > > > It would be nice if we could get a bytes() type into the first alpha, so > > > the design can get some real-world exposure in real-world apps/libs be- > > > fore 2.5 final. > > > > I agree that working code would be nice, but I don't see why it should be in > > an alpha release. IMHO it shouldn't be in an alpha release until it at least > > looks good enough for the developers, and good enough to put in a PEP. > > I'm not convinced that the PEP will be good enough without experience > from using a bytes type in *real-world* (i.e. *existing*) byte-crunching > applications. > > if we put it in an early alpha, we can use it with real code, fix any issues > that arises, and even remove it if necessary, before 2.5 final. if it goes in > late, we'll be stuck with whatever the PEP says. > > </F> > > > > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/guido%40python.org >
-- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
