Describe how to use ouroboros library on different python implementation

[windelbouwman]

Several projects would potentially benefit from this effort:

• micropython
• pypy
• rustpython
• ironpython
• brython
• jython
• grumpy
• cpython

To be of benefit to those projects, it should be clear how the files are organized.

Some suggestions:

• Describe in the documentation page how to use the standard library on top of a custom python implementation.
• Split the source directory into several source directories. For example entirely-python with the python only modules. Another folder half-python with modules consisting of a python part and a low level-underscore-prefixed part. Maybe it is an idea to structure the standard library such that language implementors can copy paste the pieces they want, and implement other parts themselves.

[ncw]

I'll just add gpython to the list!

[pfalcon]

A shameless plug - pycopy-lib is an alternative project for an alternative and standalone Python library. Pycopy-lib was started 2014-03-30 (initially targetting MicroPython, but outgrew it by now), comparing to Ouroborous start date 2016-01-17. Commit count is 2500+ comparing to Ouroborous' 24. Pycopy-lib also specifically targets minimalist Python implementations, so a noticeable share of content is actually written from scratch (the rest is copied from CPython stdlib, just the same as Ouroborous, but usually being patched to rely on small functionality basis).