Testbed import

[carlosalberto]

Initial import of the testbed used in other languages.

Summary:

• It adds a new testbed directory where the tests live, with extra dependencies in setup.py (not affecting the main package, of course).
• It includes samples for asyncio, tornado, threading and gevent, as well as basic implementation of ScopeManager for each of them.
• A small script to run all the suite (testbed/__main__.py) checks the Python version, and disables the ones for asyncio if running under Python 2 (otherwise, doing py.test testbed/ runs all the tests). This also can be done through make testbed.
• Included a README for the whole suite and a README per pattern, including any big semantic difference between them.

Ideally I'd like to have this merged (and adjusted if/as needed), prior to do the RC 2 ;)

@yurishkuro @palazzem @tedsuo

[yurishkuro]

I have no idea why we're using .rst for readme... seems like the only OT repo that does that :-(

[palazzem]

It's very common in Python projects (or at least it was) using .rst instead of Markdown. Some examples with widely used libraries:

• https://github.com/pallets/flask/blob/master/README.rst
• https://github.com/django/django/blob/master/README.rst

I don't have strong opinions on that, since what is important to me is the content of the README and keeping it consistent across other OT repos is a good idea.

[yurishkuro]

I was under impression futures is not available in py3

[palazzem]

Technically it should not be installed for py3, but since the stdlib takes precedence in modules resolution, it should not be harmful / wrong in our testbed. Conditional requires are available as follow:

setup(
    ...
    extras_require={
        ':python_version == "2.7"': ['futures']
    }
)

as described in the futures package

[carlosalberto]

Thanks for the feedback @yurishkuro and @palazzem

• I updated the README (just in case) to use the .md format (I used that for the actual per-sample README anyway).
• As @palazzem said, resolution worked just fine for futures under Python 3 (Travis didn't fail for Python 3, for example). But to be in the safe side, I made it conditional for extras_require).

Let me know ;)

[carlosalberto]

Going to merge as we did for the java-examples at the time (too much to review, and we needed to get a RC by then, just as we want it for Python now ;) )

Feel free to open an issue/PR on any change regarding the testbed integration, and I will take a look. And thanks for the feedback so far!

@yurishkuro @palazzem

[palazzem]

Sure thing, we can iterate over the testbed as soon we discover new edge/legit use cases.