Revision 1111 of Software Carpentry just went into the repository. All the images are now there (thanks, Nick), along with code fragments and exercises (not as many as I'd like, but enough to get people started). Printed, it comes to 346 pages, but don't do this at home—the supposedly-transparent PNGs are still solid black when printed.
Things I'd like to do (or would like volunteers to contribute in the usual open source way) include:
#5: complete the description of how to use the subprocess module.
#14: add a lecture on numerical programming, and another one on how to test numerical code.
#24, #25, #115, and #120: put material on eval, exec, code coverage, profiling, and other reflective ideas back in.
#28: fix the markers around regular expressions so that they display on all platforms.
#40: add a lecture on object-oriented analysis and design using the ICONIX process.
#65: come up with a better way to display the evolution of code fragments on-line using JavaScript.
#67: document the XML markup used in slides so that other people can easily contribute.
#93: fix image backgrounds so that they print properly.
Several: clean up the build process used to produce the notes.
#105: automatically check that all Python source examples conform to style guidelines.
#116: put material on time/date handling back into lectures.
#121: add a second lecture on style that focuses on what makes a good (or bad) class.
Any volunteers?
Originally posted 2006-05-03 by Greg Wilson in Content.