GET /api/v2/video/2279
HTTP 200 OK Vary: Accept Content-Type: text/html; charset=utf-8 Allow: GET, PUT, PATCH, HEAD, OPTIONS
{ "category": "PyOhio 2013", "language": "English", "slug": "keeping-library-compatible-with-python-26-34-u", "speakers": [ "Zbigniew J\u0119drzejewski-Szmek" ], "tags": [ "talk" ], "id": 2279, "state": 1, "title": "Keeping library compatible with Python 2.6-3.4 using python-systemd as example", "summary": "How hard is it to port a library to python 3? How much work is it going forward? Based on two examples (a pure Python, and a C-extension-based library), I want to show how in my experience the work required is modest, without significant impact on old code. At the same time, keeping Python2 compatibility constrains development under Python 3 because only the common subset of features can be used.", "description": "", "quality_notes": "", "copyright_text": "CC BY-SA 2.5 CA", "embed": "<object width=\"640\" height=\"390\"><param name=\"movie\" value=\";hl=en_US\"></param><param name=\"allowFullScreen\" value=\"true\"></param><param name=\"allowscriptaccess\" value=\"always\"></param><embed src=\";hl=en_US\" type=\"application/x-shockwave-flash\" width=\"640\" height=\"390\" allowscriptaccess=\"always\" allowfullscreen=\"true\"></embed></object>", "thumbnail_url": "", "duration": 60, "video_ogv_length": null, "video_ogv_url": null, "video_ogv_download_only": false, "video_mp4_length": null, "video_mp4_url": "", "video_mp4_download_only": true, "video_webm_length": null, "video_webm_url": null, "video_webm_download_only": false, "video_flv_length": null, "video_flv_url": null, "video_flv_download_only": false, "source_url": "", "whiteboard": "", "recorded": "2013-07-28", "added": "2013-07-26T10:11:25", "updated": "2014-04-08T20:28:26.203" }