Removed incorrect exception raise in import code generation function

[danthedaniel]

What does this PR do?

Removes the RuntimeError exception that is raised when no import statements are defined for a pipeline operator

Where should the reviewer start?

Line 164 in tpot/export_utils.py

How should this PR be tested?

Currently the master branch will throw an exception if an exported pipeline uses any operators that don't require any imports (like _combine_dfs()). That behavior can be seen in the existing codebase, and can be tested in the teaearlgraycold/eu_imports_ref codebase to see that it does not persist.

Questions:

• Do the docs need to be updated?

No

• Does this PR add new (Python) dependencies?

No

---

Instead of removing the exception I could alternatively require people to enter blank dicts for operators that do not require import statements, but that seems less preferable.

[danthedaniel]

My bad on this one

[coveralls]

Coverage remained the same at 52.332% when pulling 2f4b7b4 on teaearlgraycold:eu_imports_ref into 7910b93 on rhiever:master.

[rhiever]

This is why we need unit tests. :-)

On Monday, May 9, 2016, Daniel notifications@github.com wrote:

My bad on this one

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#138 (comment)

Randal S. Olson, Ph.D.
Postdoctoral Researcher, Institute for Biomedical Informatics
University of Pennsylvania

E-mail: rso@randalolson.com | Twitter: @randal_olson
https://twitter.com/randal_olson
http://www.randalolson.com