Destiny Peterson

Os independent as far as I can tell. I've tested it on multiple operating systems and the problem still occurs. A file that triggers the exception is literally ANYTHING that...

Wait, I think I know what happened. I don't know WHY it happened, but it did. In olefile.py at some point IOError got reassigned to be OSError

Wait It's python 3 itself. IOError has been replaced with OSError. Try `help(IOError)` in a python 3 console.

IMO, the custom exception doesn't need to be anything fancy. Just a simple: ``` class OleFileError(IOError): # or whatever name and whatever exception you want to derive from pass ```...

Added a new pull request that will fix this issue

Greetings, I can provide you with an update. You have participated in issues on the msg-extractor threads, so you may already know this, but I am currently the manager of...

> Not sure it would help in your case, but I developed a generic RTF parser as part of my tool rtfobj in the oletools package. It's the RtfParser class...

@decalage2 Okay, so I have no idea at all how I would even properly use your parser. I put data in, told it to parse, but then it doesn't return...

Also, @decalage2 The rtf parser I am working on is going to be quite intelligent, able to improve the format of rtf files so that it is much easier from...

The extract-msg conflict seems to be because the module wants to retain support for Python 2.7, and 0.29.* is the last version that supports it. To use future versions, either...