pyshapelib for Python 3.x

[Bernhard Reiter]

Am Tuesday, 18. October 2011 17:02:48 schrieb 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.

I'd say it is a major upgrade as Python 3K is a major step.
No hard preprence, though. ;)

> 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

I'm sure that unicode should be default for Python 3.
As for changing the default for Python 2, I'm unsure. 
You could say that less changes if you keep the old default,
but hey, old applications could change the default back anyway
and it might be good to use the same default.
So up to you to decide in the details, I'd say.

Best,
Bernhard

-- 
Managing Director + Owner: www.Intevation.net <- A Free Software Company
Kolabsys.com: Board Member          FSFE.org: Founding GA Member
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url : http://www.intevation.de/pipermail/thuban-devel/attachments/20111019/bb7a29ce/attachment.bin