(2013-10-14, 01:11)Martijn Wrote: what fix? if you got the message it's simply not supported anymore.
i'm not going to do some guessing games here.
we deprecated the python 1.0 API so if you are still using that old junk make sure it's getting updated.
The abuse is definitely not appreciated.
I am coming to this thread more than a year later, searching for the solution to a problem, only to get this.
An explanation, only, especially for the new user like myself just trying sink into what is this XBMC thing, would have been appreciated.
Merely saying, instead, "Python 1.0 is an old API that has since been deprecated. If you are getting such errors you will need to wait for the author to update their addon. Asking for them to do so in their support forum is your only course of action." would have entirely answered the OP.
The old questions and answers are useful to new users, even a year and more later. Sadly, however, the abusive bullying also came along, and reflects poorly on 'Team Kodi' - as the profile says. I don't expect this is the impression Kodi wants to have left behind ... forever.
The additional problem here is that things fail silently and mysteriously.
Perhaps marking such addons as 'broken', 'dependency unavailable', or 'out of date' would be more useful than having followed instructions, and different results being obtained, from the 'system' (appropriately) taking care of and protecting itself. As it stands, the NEW user has nowhere to go to try and sleuth out what's going on.
Perhaps as a system setting 'Display broken addons (with notation)'. Give the new / gui user a breadcrumb.
CDN$0.02
P.S. Mods - for the reasons given above, perhaps editing this thread would be prudent, should any spare time for it miraculously appear.
