<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>Am 04.12.2012 um 00:42 schrieb Gregory P. Smith <<a href="mailto:greg@krypto.org">greg@krypto.org</a>>:</div><div><br></div><blockquote type="cite"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; ">* How would we convert all the builtins to use Clinic? I fear any<br>
solution will involve some work by hand. Even if we can automate<br>
big chunks of it, fully automating it would require parsing arbitrary<br>
C. This seems like overkill for a one-shot conversion.<br>
(Mark Shannon says he has some ideas.)<br></blockquote><div><br></div><div>A lot of hand work. Sprints at pycon. etc. Automating nice chunks of it could be partially done for some easy cases such as things that only use ParseTuple today.</div>
</div></div></blockquote></div><br><div>I don’t see this as a big problem. There’s always lots of people who want to get into Python hacking and don’t know where to start. These are easily digestible pieces that can be *reviewed in a timely manner*, thus ideal. We could even do some (virtual) sprint just on that.</div><div><br></div><div>As for Larry: great approach, I’m impressed!</div></body></html>