GET /api/v2/video/109
HTTP 200 OK Vary: Accept Content-Type: text/html; charset=utf-8 Allow: GET, PUT, PATCH, HEAD, OPTIONS
{ "category": "Kiwi PyCon 2009", "language": "English", "slug": "douglas-bagnall---pyserf---a-shortcut-for-writing", "speakers": [ "Douglas Bagnall" ], "tags": [ "extensions", "kiwipycon", "kiwipycon2009", "pyserf" ], "id": 109, "state": 1, "title": "Douglas Bagnall - pyserf - a shortcut for writing C extensions in C", "summary": "", "description": "pyserf - a shortcut for writing C extensions in C\n\nPresented by Douglas Bagnall\n\nAbstract\n\nThere are many clever ways of connecting Python and C code together, and\npyserf is one of those. It is just a short script that parses a module outline\nand produces an idiomatic template for a C extension providing the same\nsignatures, so all you need to do is write the bits that actually do stuff.\n\nOutline\n\nPyserf is a tiny project that I wrote for my own use years ago and never\nreleased because it is so obvious that dozens of better versions must exist.\nThe idea is simple -- you write an outline of a module like this:\n\n \n \n \"\"\"module documentation\"\"\"\n def top_level_function(int_a, float_b):\n \"function documentation\"\n return float_c\n \n class SomeModule:\n \"\"\"class documentation\"\"\"\n def foo(self, int_ants obj_zoo):\n \"\"\"method documentation\"\"\"\n return float_frogs\n \n\nand pyserf uses the parsing modules in the standard library to generate a C\nfile that will compile to an extension providing the interface it describes,\nwith the documentation appearing in the right place and the type conversions\nall properly handled. The generated file is not a hideous unreadable mess,\nrather it is within a few characters of best practise according to the\nofficial tutorial. Once you have this template, you abandon your outline and\nwrite the middles of each function in C. In describing what pyserf does, this\ntalk will demonstrate what is required to write an extension in C by hand, and\nshow you some ways of using the standard libraries parsing modules.\n\n[VIDEO HAS ISSUES: Sound and video are poor. Slides are hard to read.]\n\n", "quality_notes": "", "copyright_text": "No license (All rights reserved)", "embed": "", "thumbnail_url": "", "duration": null, "video_ogv_length": null, "video_ogv_url": null, "video_ogv_download_only": false, "video_mp4_length": null, "video_mp4_url": null, "video_mp4_download_only": false, "video_webm_length": null, "video_webm_url": null, "video_webm_download_only": false, "video_flv_length": null, "video_flv_url": "", "video_flv_download_only": false, "source_url": "", "whiteboard": "", "recorded": null, "added": "2012-02-23T04:20:00", "updated": "2014-04-08T20:28:25.472" }