Merge downstream changes into project for a new release

[jwflory]

Summary

The HFOSS Fall 2016 class is resuming development on PyCut to expand the idea and develop it further – we'd like to coordinate with the downstream project to merge their changes and improvements back here to the upstream.

Analysis

The team working on PyCut for the HFOSS class are @tcreeds, @PatrickGormley, and @adf5051. The downstream repo is forked by tcreeds here. The scope of their changes is not yet clear, but some of the more abstract goals are to close out existing issues in this repo (#10 and #33), a more strict adherence to some of the NYS curriculum goals (detailed here), and some of the "to-do" list of tasks we determined towards the end of our project semester. This is not an exhaustive list or limiting factor to what can or cannot happen. 😄

If needed, @wilfriedE and myself can provide commentary to questions about design or implementation of the existing code (and maybe @spg1502 too if he's still hanging around and interested).

Whether the new team would like to submit pull requests back upstream in small changes (and benefit from any feedback by past team members) or submit everything in a big PR at the end of the semester is up to the current team to decide. In either case, upstream is receptive to supporting the work happening downstream whichever way they choose!

This issue can be a place for any current team members to get feedback or ask questions too.

[jwflory]

@PatrickGormley @adf5051 @tcreeds Whenever you submit the PR back upstream, be sure to include a changelog of sorts – something simple in markdown will be fine!

[jwflory]

Completed in #39.