SVN revision 383: added use_wired_web configuration option and updated test/mediaxml.py
So that you don't have to make that edit every time you update, I have added the configuration file option use_wired_web. It defaults to 0 but you can change it to 1 for basic subscribers who want to use nexdef.
In fact, if premium subscribers want to do some testing for me, they can add use_wired_web=1 to their configuration file as well. I want to know if you notice any performance or quality differences. If you see no difference, I could make use_wired_web=1 the default for everyone. Also, did you know that those XML replies from the test tools are saved to ~/.mlb/successful-1.xml and ~/.mlb/successful-2.xml (or unsuccessful-1.xml and unsuccessful-2.xml) for all media requests? Yeah, me neither. :p Sometimes I make debug additions I forget I made. :D You can use test/mediaxml.py on either one of those files to see a decoded version of the xml similar to that pastebin I posted above. |
Quote:
ETA: Is there any way to play all the top plays from a game in a playlist? I'm not sure if it's possible but I'd love to be able to catch the highlights form a game that way. |
Cannot create configuration file
For some reason, mlbviewer.py is giving me an error in trying to create a configuration file. I'm wondering if I can bypass the problem by manually creating the file. Can someone here pass along a generic configuration file and tell me where it should be located?
I don't see how this can be a permissions issue, since it happens even if I try to run the program as root. Thanks for any help that can be offered. |
Quote:
|
Quote:
|
Quote:
Also I have something else up my sleeve that I've been playing with that as a non-subscriber, you'll probably appreciate. ;) |
Quote:
print 'Creating configuration files' SyntaxError: invalid syntax Then, if I comment out line 113 (the print command), I get this: File "mlbviewer.py", line 118 print 'Could not create directory: ' + '\n' SyntaxError: invalid syntax |
Quote:
|
Quote:
What does "python --version" say? See if you can install python2.7 on your system. |
Quote:
The other thing(s) I'm working will take longer. |
Quote:
I don't know how to get mlbviewer to use 2.7, though. Any suggestion? Thanks again for your help. |
Quote:
|
Quote:
No, it's more of a problem to interact with an already open mplayer instance. If you want a sneak preview of what will eventually be implemented: Code:
cd test |
Quote:
|
Quote:
Now that I have that off my chest. You could change the symbolic link from /usr/bin/python from python3.3 to python2.7 but that may break a whole ton of system stuff if they actually did the system stuff in python3.3. You could change the top line of every file from #!/usr/bin/env python to #!/usr/bin/python2.7 except you'll have to do that every time a file gets updated. Not a good option. If you have /usr/local/bin ahead of /usr/bin in your PATH (env | grep PATH), you can add try adding a symbolic link in /usr/local/bin to python2.7 (ln -s /usr/bin/python2.7 /usr/local/bin/python) That third option may be the safest but there may still be user-level python bindings that could get affected. You can try it and see if that fixes mlbviewer for you. Then you'll have to watch to see if anything else breaks (maybe anything that uses dbus?) Let me look into this and see what I can come up with. |
All times are GMT -5. The time now is 09:04 PM. |