There's a course in my university (University of Oslo) that teaches scripting "technique" in general and Python especially. It's an intermediate-level course and assumes that the students already know programming.
The focus is more the way of problem solving with scripting rather than languages as such. Students have the opportunity to select a project (the equivalent of about 7-10 days) to work on and have evaluated, and the course lecturers are positive with my providing them some nicely defined Cython projects. So, any suggestions? Are people be ok with this? As it is only a few days, we're more thinking general "clean up stuff" type of projects than exciting new features. Here's mine: 1) Test system for compiler invocation and usage on file trees. This is not tested today. I.e. test all the behaviour with "whether a pyx file is found in directories with __init__.py" and so on. One should have a script to dynamically create test directories of various structures and then invoke the compiler in various ways (single/multiple) on it. 2) Slightly related: Unit test for invoking the compiler from the command-line, and then rewrite CmdLine.py to use optparse (with backwards-compatible behaviour in all situations), and reverse the relationship between Main.py and CmdLine.py 3) Implement a new compiler directive in order to raise exceptions rather than segfault when attributes are accessed on typed variables set to None. (More hand-holding needed but potentially more exciting and useful, and holding hands may still be less work than doing it ourself + recruitment.) The timeframe for the project is the whole autumn I believe but most students do them around october/november I think. -- Dag Sverre _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
