Move test_py_htm to nupic.core and refactor test

[david-ragazzi]

Fixes #281

[coveralls]

Coverage remained the same when pulling 3d8f594 on david-ragazzi:include_test_py_region into 08731c8 on numenta:master.

[david-ragazzi]

🍏 Ready to review and merge

[rhyolight]

I want to hear what @subutai and @scottpurdy have to say.

[subutai]

How is PyRegionTest being run and tested in nupic.core? Doesn't it need access to the python bindings and python regions to execute?

[david-ragazzi]

How is PyRegionTest being run and tested in nupic.core? Doesn't it need access to the python bindings and python regions to execute?

@subutai It is build in nupic.core but tested in nupic through Updates nupic.core to latest built SHA PRs. So all tests and README instructions remains in nupic. Only its build is perfomed on nupic.core because it doesn't need python support files to be linked: actually its compile/link flags are indentical to cpp_region_test (old testscpphtm) located in nupic.core.

[subutai]

@david-ragazzi Ah ok, got it. That makes sense to me - thanks! I am fine with this structure.

[subutai]

We might want to put some comments in the PyRegionTest with the purpose of the test plus David's explanation so that someone looking at it doesn't get confused.

[rhyolight]

@subutai said:

We might want to put some comments in the PyRegionTest with the purpose of the test plus David's explanation so that someone looking at it doesn't get confused.

Good idea. @david-ragazzi do this and I'll merge it!

[david-ragazzi]

@david-ragazzi do this and I'll merge it!

b853fe5