Issue 38 in fabricate: Python3 support

60 views
Skip to first unread message

fabr...@googlecode.com

unread,
Apr 6, 2013, 9:39:32 PM4/6/13
to fabrica...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 38 by daniel.b...@gmail.com: Python3 support
http://code.google.com/p/fabricate/issues/detail?id=38

What steps will reproduce the problem?
1. attempt to import or run fabricate with python 3+

I wasn't necessarily expecting Python3 (python 3, py3k, whatever) to be
supported, but am working on making a codebase that *uses* fabricate
Python3-compatible.

I'm using fabricate 1.25 on both OSX and Linux with Python 3.3.0.

Attached is a patch that works for my uses but is probably not exhaustive.

Attachments:
fabricate-py3k-r163.patch 5.3 KB

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

fabr...@googlecode.com

unread,
Apr 6, 2013, 11:07:24 PM4/6/13
to fabrica...@googlegroups.com

Comment #1 on issue 38 by benh...@gmail.com: Python3 support
http://code.google.com/p/fabricate/issues/detail?id=38

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.

fabr...@googlecode.com

unread,
Apr 7, 2013, 10:10:53 AM4/7/13
to fabrica...@googlegroups.com

Comment #2 on issue 38 by daniel.b...@gmail.com: Python3 support
http://code.google.com/p/fabricate/issues/detail?id=38

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

fabr...@googlecode.com

unread,
Apr 7, 2013, 10:11:53 AM4/7/13
to fabrica...@googlegroups.com

Comment #3 on issue 38 by daniel.b...@gmail.com: Python3 support
http://code.google.com/p/fabricate/issues/detail?id=38

Assuming my master branch is up to date, here's the comparison view for
quick reference:
https://github.com/meatballhat/fabricate/compare/py3k-compat

fabr...@googlecode.com

unread,
May 3, 2013, 9:24:07 AM5/3/13
to fabrica...@googlegroups.com
Updates:
Status: Started

Comment #4 on issue 38 by simon.al...@gmail.com: Python3 support
http://code.google.com/p/fabricate/issues/detail?id=38

Imported the changes from git hub. Will merge with master and test.

fabr...@googlecode.com

unread,
May 3, 2013, 9:26:26 AM5/3/13
to fabrica...@googlegroups.com

Comment #5 on issue 38 by daniel.b...@gmail.com: Python3 support
http://code.google.com/p/fabricate/issues/detail?id=38

:thumbsup: and yay!

fabr...@googlecode.com

unread,
Apr 10, 2014, 4:16:34 AM4/10/14
to fabrica...@googlegroups.com

Comment #6 on issue 38 by wber...@google.com: Python3 support
http://code.google.com/p/fabricate/issues/detail?id=38

Any update on this? Python3 is getting standard now.

fabr...@googlecode.com

unread,
Feb 16, 2015, 8:24:00 AM2/16/15
to fabrica...@googlegroups.com

Comment #7 on issue 38 by chang...@gmail.com: Python3 support
https://code.google.com/p/fabricate/issues/detail?id=38

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
Reply all
Reply to author
Forward
0 new messages