Hi Steven, I’m happy to collaborate on this project together — it would be great to have your experience with CPython internals on the team.
> And by the way, I can get to work long before the start-coding time point of > GSoC timeline. I can be involved in some capacity before the start-coding period as well (I originally planned to spend the time getting well acquainted so as to hit the ground running) but I would prefer if we leave the more involved tasks (e.g reference count checking, format string checking) to the start-coding time point as I can’t work in a full time manner until late May due to commitments in school before then. Perhaps we can begin with the more low hanging fruits such as Error-handling checking, errors in exception handling, and verification of PyMethodDef tables in the time before the start-coding period? It might be good for us to start with these smaller tasks first to be more efficient in tackling the more involved tasks anyways. It would also be easy to divvy these tasks up as well. Best, Eric
