thanks for offering to help out. the list in the wiki describes only
unsolved problems. as jeremie mentioned, you could also have a look at
the list of currently open issues.
but perhaps the best method to get involved in development is to just
play around with it, to see what breaks or could be improved, and then
try to look into that (and ask questions about here). for example by
locating new programs on the web that we might add to
shedskin/examples, getting them to work and profiling the resulting
there's no large-scale roadmap in any case. I'm personally happy with
the current state of things, and am not much interested in, say,
Python 3 or unicode support (or lifting just about any limitation
mentioned in the documentation), and would prefer to just stabilize
and optimize the current code .