Tag Archives: django

Fetch OAuth Authenticated YouTube API Version 2.0 Requests with GData-Python-Client, Including Insight

Posted on October 26, 2010 by kfarr

We’ve been using Google’s GData-Python-Client library to connect our VidCaster client accounts to YouTube, which allows for neat operations like importing* and exporting of video. A key component of VidCaster is to provide simple aggregated video analytics to our users, … Continue reading →

Posted in tech, work | Tagged analytics, api, client library, csv, django, gdata, google, insight, oauth, online video, python, python-gdata-client, statistics, stats, v20, version 2, vidcaster, video, youtube | Leave a comment

Making a complex customized Django form template? Remember to include form.non_field_errors!

Posted on April 4, 2008 by kfarr

This drove me crazy for about 30 minutes. If you’re making a heavily customized form template with Django, the newforms documentation suggests this format: But, if you do any sort of non-field specific (form-level) validation, those validation messages won’t be … Continue reading →

Posted in internets, tech | Tagged 0.96, attribute, dev, django, error, field, field specific, form, form wide, form-level, form.as_ul, form.errors, form.errors.all, form.field_errors, forms, forms.ValidationError, level, message, new forms, newforms, non, non-field, non-field-specific, non-specific, non_field_errors, python, release, specific, svn, validation, validationerror, validator | 13 Comments

Tag Archives: django

Fetch OAuth Authenticated YouTube API Version 2.0 Requests with GData-Python-Client, Including Insight

Making a complex customized Django form template? Remember to include form.non_field_errors!

Archives

Meta