{"id":373,"date":"2012-05-31T10:33:57","date_gmt":"2012-05-31T15:33:57","guid":{"rendered":"http:\/\/www.alandmoore.com\/blog\/?p=373"},"modified":"2012-05-31T10:33:57","modified_gmt":"2012-05-31T15:33:57","slug":"wcgbrowser-updated","status":"publish","type":"post","link":"https:\/\/alandmoore.com\/blog\/2012\/05\/31\/wcgbrowser-updated\/","title":{"rendered":"WCGBrowser updated"},"content":{"rendered":"

I’ve been wanting for some time to update my wcgbrowser<\/a> code to be python3 compatible, but I’ve been held back by the ambiguity surrounding the configobj library — in a nuthshell, the official project isn’t 3.x compatible, but there is a fork that is. Unfortunately the fork maintainer isn’t putting real effort into a release, and Debian won’t include it until they do.<\/p>\n

So fed up with that, I got a wild idea last night to port the code to something more supported. I considered JSON and XML, but settled on YAML<\/a>, since it seems to be reasonably hand-hackable, well supported, and handles about any data types I need.<\/p>\n

I thought this would be a big deal, but surprisingly it only took about 20 minutes to get things working. I decided to keep going with my momentum by adding the remaining command-line configuration parameters to the config file and making sure the whole thing worked with python 3.<\/p>\n

I also fixed some logic bugs in the process. Nice.<\/p>\n

If anyone out there is actually using it, you can get the latest code on github<\/a>. \u00a0Naturally, the conversion to YAML will break any existing configuration; sorry in advance. \u00a0To make up for it, I’ve fully commented the config file so it should be pretty simple to figure out how to port it over. \u00a0Also, bear in mind that it’s now looking for a config file called “wcgbrowser.yaml”, not “wcgbrowser.conf”.<\/p>\n","protected":false},"excerpt":{"rendered":"

I’ve been wanting for some time to update my wcgbrowser code to be python3 compatible, but I’ve been held back by the ambiguity surrounding the configobj library — in a nuthshell, the official project isn’t 3.x compatible, but there is a fork that is. Unfortunately the fork maintainer isn’t putting real effort into a release, […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,7,5],"tags":[16,33,28,41],"class_list":["post-373","post","type-post","status-publish","format-standard","hentry","category-general","category-programming","category-technology","tag-floss-2","tag-kiosk","tag-programming-2","tag-software-projects"],"_links":{"self":[{"href":"https:\/\/alandmoore.com\/blog\/wp-json\/wp\/v2\/posts\/373","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/alandmoore.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/alandmoore.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/alandmoore.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/alandmoore.com\/blog\/wp-json\/wp\/v2\/comments?post=373"}],"version-history":[{"count":2,"href":"https:\/\/alandmoore.com\/blog\/wp-json\/wp\/v2\/posts\/373\/revisions"}],"predecessor-version":[{"id":416,"href":"https:\/\/alandmoore.com\/blog\/wp-json\/wp\/v2\/posts\/373\/revisions\/416"}],"wp:attachment":[{"href":"https:\/\/alandmoore.com\/blog\/wp-json\/wp\/v2\/media?parent=373"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/alandmoore.com\/blog\/wp-json\/wp\/v2\/categories?post=373"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/alandmoore.com\/blog\/wp-json\/wp\/v2\/tags?post=373"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}