[issue775321] plistlib error handling

2011-04-10 Thread Ezio Melotti
Ezio Melotti ezio.melo...@gmail.com added the comment: Note that this behavior is documented[0]: The XML data is parsed using the Expat parser from xml.parsers.expat – see its documentation for possible exceptions on ill-formed XML. Unknown elements will simply be ignored by the plist parser.

[issue775321] plistlib error handling

2011-04-10 Thread Ned Deily
Ned Deily n...@acm.org added the comment: I agree. If it were important to make plistlib error handling more useful, using a different parser would be the way to go, I think. In any case, Apple has deprecated the use of XML plists and moved to a binary plist format that plistlib does not

[issue775321] plistlib error handling

2011-01-12 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: I think this was closed prematurely. I would like a core dev to assess this issue and reject or validate it. -- nosy: +eric.araujo -BreamoreBoy resolution: wont fix - stage: patch review - status: closed - open versions: +Python 3.3

[issue775321] plistlib error handling

2011-01-12 Thread Éric Araujo
Changes by Éric Araujo mer...@netwok.org: -- nosy: +georg.brandl, mher, ned.deily, ronaldoussoren ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue775321 ___

[issue775321] plistlib error handling

2011-01-12 Thread Mher Movsisyan
Mher Movsisyan mher.movsis...@gmail.com added the comment: I don't see compelling reasons to wrap ExpatError in ValueError. ExpatError contains extra diagnostic information such as line and column numbers. -- ___ Python tracker

[issue775321] plistlib error handling

2010-08-18 Thread Mark Lawrence
Mark Lawrence breamore...@yahoo.co.uk added the comment: Closing as no reply to msg110335. -- resolution: - wont fix status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue775321

[issue775321] plistlib error handling

2010-07-14 Thread Mark Lawrence
Mark Lawrence breamore...@yahoo.co.uk added the comment: If anything is to be done the patch needs updating. I'd be inclined to close this as won't fix unless someone can come up with a really compelling reason to implement it. -- nosy: +BreamoreBoy versions: +Python 3.2 -Python 2.7

[issue775321] plistlib error handling

2009-04-22 Thread Daniel Diniz
Changes by Daniel Diniz aja...@gmail.com: -- keywords: +easy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue775321 ___ ___ Python-bugs-list mailing

[issue775321] plistlib error handling

2009-02-14 Thread Daniel Diniz
Changes by Daniel Diniz aja...@gmail.com: -- dependencies: -plistlib error handling ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue775321 ___ ___

[issue775321] plistlib error handling

2009-02-11 Thread Daniel Diniz
Changes by Daniel Diniz aja...@gmail.com: -- dependencies: +plistlib error handling stage: - patch review ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue775321 ___

[issue775321] plistlib error handling

2009-02-09 Thread Daniel Diniz
Daniel Diniz aja...@gmail.com added the comment: Here's a very simple patch, is this the only path for errors from garbage? I think docs are needed too: if apps catching ExpatError explicitly, will break. Not sure if this should actually change, as I don't use plistlib. I havve nothing against