Open GoogleCodeExporter opened 9 years ago
Nice! I definitely think it's a good idea to make fabricate support Python 3,
and to do so with a single codebase. I like the "from __future__" approach
here, and even if there are a couple of "if PY3K"s, that's better than
supporting two codebases.
Original comment by benh...@gmail.com
on 7 Apr 2013 at 3:07
I accidentally left a huge amount of stuff out of this patch. No idea what
happened there. Anyway, I'm going to be keeping a git clone + branch going
over here as I re-add the necessary bits:
https://github.com/meatballhat/fabricate/tree/py3k-compat
Original comment by daniel.b...@gmail.com
on 7 Apr 2013 at 2:10
Assuming my master branch is up to date, here's the comparison view for quick
reference: https://github.com/meatballhat/fabricate/compare/py3k-compat
Original comment by daniel.b...@gmail.com
on 7 Apr 2013 at 2:11
Imported the changes from git hub. Will merge with master and test.
Original comment by simon.al...@gmail.com
on 3 May 2013 at 1:24
:thumbsup: and yay!
Original comment by daniel.b...@gmail.com
on 3 May 2013 at 1:26
Any update on this? Python3 is getting standard now.
Original comment by wber...@google.com
on 10 Apr 2014 at 8:16
I've rebased the py3k branch on master, dropped a bad commit, and added more
fixes: https://github.com/Changaco/fabricate/compare/master...py3k-compat
Original comment by chang...@gmail.com
on 16 Feb 2015 at 1:23
Original issue reported on code.google.com by
daniel.b...@gmail.com
on 7 Apr 2013 at 1:39Attachments: