Gilectomy

As if the bad behavior the GIL becoming a no-op doesn't mean that all C extensions don't need a once-over anyways. A thread-specific variable might do for a compatibility layer where the existing API just uses that as an implicit variable to the new API functions, but that probably wouldn't work for multi threaded contexts so well. But just doing that half-solution means you still can't use two interpreters in a single thread.