Hi Bernhard,<br><br><div class="gmail_quote">On 18 October 2011 13:36, Bernhard Reiter <span dir="ltr"><<a href="mailto:bernhard@intevation.de">bernhard@intevation.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">> I'm wondering about versioning though.<br>
> Would this become pyshapelib 1.1 or 1.0.1.<br>
<br>
</div>I'd say 1.1 or 2 because it is a major step forward.<br>
<br></blockquote><div><br></div><div>Then I'll go for 1.1, as this isn't a major API upgrade.</div><div><br></div><div>There is one little thingy though: Unicode.</div><div><br></div><div>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.</div>
<div>However, the 3.x python series now uses unicode strings by default. So I'm thinking of reversing the default:</div><div><br></div><div>return types for strings, according to return_unicode flag:</div><div>2.x:</div>
<div>False (default) -> str</div><div>True -> unicode</div><div>3.x:</div><div>False -> bytes</div><div>True (default) -> str</div><div><br></div><div>What do you think?</div><div><br></div><div>Bram</div><div>
<br></div><div><br></div><div> </div></div>-- <br>hi, i'm a signature viruz, plz set me as your signature and help me spread :)<br>