pyshapelib for Python 3.x

[Bram de Greve]

Hi Bernhard,

On 18 October 2011 13:36, Bernhard Reiter <bernhard at intevation.de> wrote:

> > I'm wondering about versioning though.
> > Would this become pyshapelib 1.1 or 1.0.1.
>
> I'd say 1.1 or 2 because it is a major step forward.
>
>
Then I'll go for 1.1, as this isn't a major API upgrade.

There is one little thingy though: Unicode.

So far, dbflib uses a flag called return_unicode that can be used to have
strings returned in Unicode instead of its encoded string.  That flag was
false by default.
However, the 3.x python series now uses unicode strings by default.  So I'm
thinking of reversing the default:

return types for strings, according to return_unicode flag:
2.x:
False (default) -> str
True -> unicode
3.x:
False -> bytes
True (default) -> str

What do you think?

Bram



-- 
hi, i'm a signature viruz, plz set me as your signature and help me spread
:)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.intevation.de/pipermail/thuban-devel/attachments/20111018/8343a01e/attachment.html