[Python-Dev] .clinic.c vs .c.clinic
Larry Hastings
larry at hastings.org
Mon Jan 20 22:43:19 CET 2014
More information about the Python-Dev mailing list
Mon Jan 20 22:43:19 CET 2014
- Previous message: [Python-Dev] .clinic.c vs .c.clinic
- Next message: [Python-Dev] .clinic.c vs .c.clinic
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 01/20/2014 11:09 AM, Barry Warsaw wrote: > On Jan 20, 2014, at 12:05 AM, Larry Hastings wrote: > >> Contestant 5: "Put in __clinic__ directory, add .h" >> >> foo.c -> __clinic__/foo.c.h >> foo.h -> __clinic__/foo.h.h > This is cached output right? IOW, it can be regenerated if it's missing. If > so, this seems like a nice parallel to __pycache__. It's mostly hidden until > you want to go looking for it. > > +1 It's cached output. The difference to __pycache__ is that the output will be checked in, and is something you might ever want to examine. //arry/ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20140120/fec6824d/attachment.html>
- Previous message: [Python-Dev] .clinic.c vs .c.clinic
- Next message: [Python-Dev] .clinic.c vs .c.clinic
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list