<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 16, 2014 at 1:58 PM, Marko Rauhamaa <span dir="ltr"><<a href="mailto:marko@pacujo.net" target="_blank">marko@pacujo.net</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div id=":3jw" class="" style="overflow:hidden">IMO, you should consider forking your library code for Python2 and<br>
Python3.</div></blockquote></div><br>I don't get the idea that Brett Cannon agrees with you:</div><div class="gmail_extra"><br></div><div class="gmail_extra"><a href="http://nothingbutsnark.svbtle.com/commentary-on-getting-your-code-to-run-on-python-23">http://nothingbutsnark.svbtle.com/commentary-on-getting-your-code-to-run-on-python-23</a><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">While he doesn't explicitly say so, I got the distinct impression reading his recent blog post that he supports one source, not forked sources.</div><div class="gmail_extra"><br></div><div class="gmail_extra">In the absence to evidence to the contrary, I think of Brett as the most expert developer in the porting space.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Skip</div><div class="gmail_extra"><br></div></div>