<div dir="ltr"><div class="gmail_quote">On Fri, May 28, 2010 at 8:12 PM, Lennart Regebro <span dir="ltr"><<a href="mailto:regebro@gmail.com">regebro@gmail.com</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">On Fri, May 28, 2010 at 20:00, cool-RR <<a href="mailto:cool-rr@cool-rr.com">cool-rr@cool-rr.com</a>> wrote:<br>
> I'm not sure we're on the same page here. My intention is that Python 2.x<br>
> users will use only `garlicsim`, and Python 3.x users will use only<br>
> `garlicsim_py3`.<br>
<br>
</div>Why would you want that? Reasonably it should be called garlicsim in both cases.<br>
If not you make it needlessly painful to move from Python 2 to Python 3.<br></blockquote><div><br></div><div>As P.J. said, the package will have the same name `garlicsim` in both versions, but the name on PyPI of the Python 3 version will be `garlicsim_py3`. </div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Also, even though you want your code to be clean, the amount of<br>
compatibility hacks to support both Python 2 and Python 3 you would<br>
need is probably not very large if you use Distribute and it's 2to3<br>
support.<br></blockquote><div><br></div><div>Funny you mention it just now. Python 3 is just giving me an obscure problem that I (a) don't know how to solve and (b) seriously doubt any 2to3 algorithm will handle.</div>
<div><br></div><div>Here it is:</div><div><a href="http://stackoverflow.com/questions/2930792/pickling-an-unbound-method-in-python-3">http://stackoverflow.com/questions/2930792/pickling-an-unbound-method-in-python-3</a></div>
</div><br>
<div>Ram.</div></div>