adding customized function... option..

[ghost]

No description provided.

[thoppe]

Hi @SoftwareMechanic, this looks like it could be useful addition but the checks failed. Can you

1. Fix the errors in the continuous integration (I used tox on this project, if it passes locally it should pass on Travis CI). The errorlog for your patch is here https://travis-ci.org/thoppe/python-hyperoperators/jobs/213830838
2. Describe a use case for a custom function so we can add it to the README.

[coveralls]

Coverage decreased (-5.4%) to 94.624% when pulling fb97f68 on softwaremechanic:master into a5d0cd6 on thoppe:master.

[ghost]

1.Fix the errors.

Well everything except one seem fixed now. For some reason i can't pass kwargs to base_hyperop0.. I'm missing some python internals..

2. Use case for a custom function.

I wanted to be able to apply the reduction/exponentiation functions on more than addition as the base case.
So effectively I wanted to say define the base case as say, subtraction and see if we can make it generic.(so hyper op 1 becomes division, 2 becomes log etc..)

[coveralls]

Coverage decreased (-5.4%) to 94.624% when pulling 1f92a7c on softwaremechanic:master into a5d0cd6 on thoppe:master.

[thoppe]

@SoftwareMechanic I don't have the time to write tests for a customFunction, mostly since I'd like to see your use case. Either way, that brings the coverage down, which is why the build fails. I'm happy to merge it anyways, since it doesn't seem to cause any harm to the existing code.

If you're doing a project with this, please let me know! I'm interested to see what comes out of it.