write_clinic_file tells Clinic to start writing to the clinic file, which I think is best to do at the very top of the file.  include_clinic_file spits out the #include, which you probably want near the bottom of the file, just before the static module declarations.  You can't put the #include at the top because it may refer to typedefs declared further down. 

Antoine Pitrou <report@bugs.python.org> wrote:

>
>Antoine Pitrou added the comment:
>
>> * Antoine: I've implemented shunting the bulk of Argument Clinic's
>>   output into a separate file.  Please see Modules/zlibmodule.c
>>   and Modules/zlibmodule_clinic.c for more.
>
>Interesting, thanks :-)
>Why do you need both clinic.write_clinic_file() and clinic.include_clinic_file() ?
>
>> I don't suppose we can get some decisions made and some code checked
>> in before the PyCon sprints...?
>
>I suppose that depends on how quick everyone is.
>But code can be written before the PEP is finally accepted, of course.
>
>----------
>title: Integrate "Argument Clinic" specialized preprocessor into CPython trunk -> Integrate "Argument Clinic" specialized preprocessor	into CPython trunk
>
>_______________________________________
>Python tracker <report@bugs.python.org>
><http://bugs.python.org/issue16612>
>_______________________________________