RetroSearch Browse

Fri Jun 25 04:38:35 EDT 2004 · https://mail.python.org/pipermail/python-dev/2004-June/045587.html

Guido van Rossum wrote:
>>Ok, how about a compromise: .encode() and .decode() of string
>>and unicode objects may return string or unicode objects only
>>(limiting the set of types to two base types).
> 
> 
> This works for me, especially since I expect type inferencers to
> collapse the two types (just as they should collapse int and long).

Ok, I'll make the necessary changes next week.

-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Source  (#1, Jun 25 2004)
 >>> Python/Zope Consulting and Support ...        http://www.egenix.com/
 >>> mxODBC.Zope.Database.Adapter ...             http://zope.egenix.com/
 >>> mxODBC, mxDateTime, mxTextTools ...        http://python.egenix.com/
________________________________________________________________________
IL Workshop @ Net.ObjectDays 2004, Erfurt, Germany          93 days left

::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ::::

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2004-June/045587.html below:

[Python-Dev] Allowing u.encode() to return non-strings