Re:How not to write Python: Part 1 (Courtesy of Adobe)
by Rinzai on Thursday March 29, 2012 @09:06PM
(#3774006)
Honestly, this looks like automatically generated code.
[ Parent
| on HN ]
Re:How not to write Python: Part 1 (Courtesy of Adobe)
by pjscott on Thursday March 29, 2012 @09:16PM
(#3774043)
Specifically, it looks like someone created a decision tree using Weka's J48graft class, then translated it automatically to Python code.
Re:How not to write Python: Part 1 (Courtesy of Adobe)
by DallaRosa on Thursday March 29, 2012 @10:11PM
(#3774195)
What I can't get is the need to translate the Java code to Python. Ideas, anyone?
Re:How not to write Python: Part 1 (Courtesy of Adobe)
by prodigal_erik on Thursday March 29, 2012 @10:19PM
(#3774214)
Python does has a nice clean grammar if you have to generate code, but yeah, if they already had a Weka model it's not clear why they aren't just evaluating that in a JVM. The only exotic thing they're doing is calling a Python module that can read Win32 portable executable files, though there appear to be similar Java libraries. Maybe they want end users to install and run something, so they avoided requiring the huge download footprint of a modern JRE?