tpltnt

Hey @hayd, i merged your PR in [here](https://github.com/tpltnt/SimpleCV). Do you think further actions are required to support Python 3?

@hayd thank you for the hint. I added an issue in my (fork) repo.

@golyalpha I commented on the differences between openCV2 and openCV3 (and the porting of the Python binding) in issue #689. Maybe that helps a bit.

Hi @jxieeducation I added your changes to my fork [here](https://github.com/tpltnt/SimpleCV), but your SimpleCv repo seems to be gone. I did acknowledge you in the commit message. If that is not...

The documentation e.g. [basic usage](https://iocage.readthedocs.io/en/latest/basic-use.html) describes the expected behavior. I consider this a bug.

Looks good. No downstream issues. Should be merged soon.

Looks like a great contribution to the documentation and should be merged soon.

@mtytel if you want I can start doing some maintenance work (and try to implement a MIDI feature I want). To to this I need the right to push code...

I understand what you want to achieve and there is a good case for it. My current view is that a chapter is like a guide on a given topic...

I missed the part about moving the text. I adjusted everything accordingly.