2014-07-20, 03:43
Just a heads up - I'm looking at the latest Vevo playback issues.
I've figured out the problem - a particularly obscure way of referencing stuff in the Youtube javascript externals - seems to be specifically chosen to stuff up the javascript -> python parsing being done by downloaders and these sort of modules.
I'm playing with ways to decode it, but it's going to be hacky at best, and so I am also looking at ways to do straight javascript interpretation in python, but there's nothing simple or cross-platform I've found so far.
Figured y'all would appreciate at least knowing the current status. Note, also, I'm not "official" when it comes to this module - I have no idea if the actual developer of this module is fixing this as we speak. I'm just a dude who happens to know python and wants his damn youtube videos to work
I've figured out the problem - a particularly obscure way of referencing stuff in the Youtube javascript externals - seems to be specifically chosen to stuff up the javascript -> python parsing being done by downloaders and these sort of modules.
I'm playing with ways to decode it, but it's going to be hacky at best, and so I am also looking at ways to do straight javascript interpretation in python, but there's nothing simple or cross-platform I've found so far.
Figured y'all would appreciate at least knowing the current status. Note, also, I'm not "official" when it comes to this module - I have no idea if the actual developer of this module is fixing this as we speak. I'm just a dude who happens to know python and wants his damn youtube videos to work