Python 3.4 plistlib doesn't work (str vs bytes errors) -

-

so, started on new toy project , decided i'd use python 3 first time...

in [1]: import plistlib  in [2]: open("/volumes/thunderbay/current/music/itunes/itunes library.xml") itl:     library = plistlib.load(itl)    ...: --------------------------------------------------------------------------- typeerror                                 traceback (most recent call last) <ipython-input-3-6459a022cb71> in <module>()       1 open("/volumes/thunderbay/current/music/itunes/itunes library.xml") itl: ----> 2     library = plistlib.load(itl)       3  /usr/local/cellar/python3/3.4.3_1/frameworks/python.framework/versions/3.4/lib/python3.4/plistlib.py in load(fp, fmt, use_builtin_types, dict_type)     984         fp.seek(0)     985         info in _formats.values(): --> 986             if info['detect'](header):     987                 p = info['parser']     988                 break  /usr/local/cellar/python3/3.4.3_1/frameworks/python.framework/versions/3.4/lib/python3.4/plistlib.py in _is_fmt_xml(header)     556     557     pfx in prefixes: --> 558         if header.startswith(pfx):     559             return true     560  typeerror: startswith first arg must str or tuple of str, not bytes

hmm ok, let's give hint:

in [3]: open("/volumes/thunderbay/current/music/itunes/itunes library.xml") itl:     library = plistlib.load(itl, fmt=plistlib.fmt_xml)    ...: --------------------------------------------------------------------------- typeerror                                 traceback (most recent call last) <ipython-input-4-ef5f06b44ec2> in <module>()       1 open("/volumes/thunderbay/current/music/itunes/itunes library.xml") itl: ----> 2     library = plistlib.load(itl, fmt=plistlib.fmt_xml)       3  /usr/local/cellar/python3/3.4.3_1/frameworks/python.framework/versions/3.4/lib/python3.4/plistlib.py in load(fp, fmt, use_builtin_types, dict_type)     995     996     p = p(use_builtin_types=use_builtin_types, dict_type=dict_type) --> 997     return p.parse(fp)     998     999  /usr/local/cellar/python3/3.4.3_1/frameworks/python.framework/versions/3.4/lib/python3.4/plistlib.py in parse(self, fileobj)     323         self.parser.endelementhandler = self.handle_end_element     324         self.parser.characterdatahandler = self.handle_data --> 325         self.parser.parsefile(fileobj)     326         return self.root     327  typeerror: read() did not return bytes object (type=str)

plistlib in standard library, problems above have feeling has not been converted python 3?

i wondering if decision try python 3 on 2.7 going prove masochistic , pointless...

oh yes, actual question: possible open xml plist file plistlib in python 3.4.3?

surely i'm missing obvious here perhaps... noticed py2 version of plistlib (which works!) has different interface, has modified code of library inclusion py3...

thanks @j presper eckert giving me clue for...

i found article:
http://python-notes.curiousefficiency.org/en/latest/python3/text_file_processing.html#the-binary-option

which suggests answer open file in binary mode, tried , works!

with open("/volumes/thunderbay/current/music/itunes/itunes library.xml", 'rb') itl:     library = plistlib.load(itl)

Comments

Post a Comment

Popular posts from this blog

c# - Better 64-bit byte array hash -

-
i need hash algorithm produces 64-bit hash code ( long ) fewer collisions string.gethashcode() , fast (no expensive calls cryptographic functions). here's implementation of fnv still shows 3% of collisions after testing 2 million random strings. need number way lower. void main() { const string chars = "abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz!#@$%^&*()_+}{\":?><,./;'[]0123456789\\"; const int n = 2000000; var random = new random(); var hashes = new hashset<long>(); int collisions = 0; for(int = 0; < n; i++) { var len = random.next(chars.length); var str = new char[len]; (int j = 0; j < len; j++) { str[j] = chars[random.next(chars.length)]; } var s = new string(str); if(!hashes.add(get64bithash( s ))) collisions++; } console.writeline("collision percentage after " + n + " random strings: " + ((doubl
Read more

webrtc - Which ICE candidate am I using and why? -

-
[questions in bold below] i have setup kurento media server 5.1.3 in datacenter behind firewall running os ubuntu 14.04. has 2 network cards: 222.222.222.222 (eth0 - private ip) 111.111.111.111 (eth1 - public ip) attached below sdp (setremotedescription) when browser connected kurento media server type: answer, sdp: v=0 o=- 5487318114793304426 0 in ip4 0.0.0.0 s=kurento media server c=in ip4 0.0.0.0 t=0 0 a=group:bundle audio video m=audio 59068 rtp/savpf 111 0 c=in ip4 111.111.111.111 a=rtpmap:111 opus/48000/2 a=rtpmap:0 pcmu/8000 a=sendrecv a=rtcp:59068 in ip4 111.111.111.111 a=rtcp-mux a=ssrc:669011897 cname:user39019747@host-6e83e4c2 a=extmap:3 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time a=mid:audio b=as:20 a=ice-ufrag:ymdk a=ice-pwd:lylifk5ueqzpwm91ddj37e a=fingerprint:sha-256 ff:0f:81:8c:41:4e:b4:b6:c6:d8:36:f3:d6:5f:09:fd:5f:af:13:b3:9d:fc:12:66:ac:f3:56:d6:5b:0a:73:5d a=candidate:1 1 udp 2013266431 111.111.111.111 55239 typ host a=candidate:2 1 udp
Read more

php - Zend Framework / Skeleton-Application / Composer install issue -

-
i trying create zend framework application using skeleton in netbeans. when run composer install, following error message: "c:\php\php.exe" "c:\composer\composer.phar" "--ansi" "--no-interaction" "update" "--dev" using deprecated option "dev". dev packages installed default now. loading composer repositories package information updating dependencies (including require-dev) requirements not resolved installable set of packages. problem 1 - package requires php >=5.5 php version (5.4.42) not satisfy requirement. problem 2 - installation request zendframework/zendframework 2.5.1 -> satisfiable zendframework/zendframework[2.5.1]. - zendframework/zendframework 2.5.1 requires php >=5.5 -> php version (5.4.42) not satisfy requirement. done. apparently, zend framework only needs php 5.3+ contradicts above. need use php 5.4. my composer.json following: { "name": "
Read more