Version 0.28.1

v0.28.1

• [TeamMsgExtractor #181] Fixed issue in Attachment that arose when moving some of the code to a base class.
• Fixed small error in utils.parse_type that caused it to incorrectly compare expected and actual length. Fortunately, this had no actual effect aside from a warning.
• Added the ebcdic module to the requirements to add more supported encodings.

Version 0.28.0

v0.28.0

• [TeamMsgExtractor #87] Added a new system to handle NotImplementedError and other exceptions. All msg classes now have an option called attachmentErrorBehavior that tells the class what to do if it has an error. The value should be one of three constants: ATTACHMENT_ERROR_THROW, ATTACHMENT_ERROR_NOT_IMPLEMENTED, or ATTACHMENT_ERROR_BROKEN. ATTACHMENT_ERROR_THROW tells the class to not catch and exceptions and just let the user handle them. ATTACHMENT_ERROR_NOT_IMPLEMENTED tells the class to catch NotImplementedError exceptions and put an instance of UnsupportedAttachment in place of a regular attachment. ATTACHMENT_ERROR_BROKEN tells the class to catch all exceptions and either replace the attachment with UnsupportedAttachment if it is a NotImplementedError or BrokenAttachment for all other exceptions. With both of those options, caught exceptions will be logged.
• In making the previous point work, much code from Attachment has been moved to a new class called AttachmentBase. Both BrokenAttachment and UnsupportedAttachment are subclasses of AttachmentBase meaning data can be extracted from their streams in the same way as a functioning attachment.
• [TeamMsgExtractor #162] Pretty sure I actually got it this time. The execution flag should be applied by pip now.
• Fixed typos in some exceptions

Version 0.27.16

v0.27.16

• [TeamMsgExtractor #177] Fixed incorrect struct being used. It should be the correct one now, but further testing will be required to confirm this.
• Fixed log error message in extract_msg.prop to actually format a value into the message.

Version 0.27.15

v0.27.15

• [TeamMsgExtractor #177] Fixed missing import.

Version 0.27.14

v0.27.14

• [TeamMsgExtractor #173] Fixed typo that I made in the last version that broke things. I didn't have the resources to test this one myself, unfortunately.
• Fixed a typo in an exception message.

Version 0.27.12

v0.27.12

• [TeamMsgExtractor #173] Made an assumption about where an exception was thrown from and was wrong. While that location would have throw an exception, the function that called that code was the one to actually throw the exception in question. This issue should be fixed...
• [TeamMsgExtractor #162] Made another attempt to fix the execution flag on the wrapper script.

Version 0.27.11

v0.27.11

• [TeamMsgExtractor #173] Tentatively implemented type 0x1014 (PtypMultipleInteger64). Apparently I forgot to do it earlier.

Version 0.27.9

v0.27.9

• [TeamMsgExtractor #161] Added commands to the command line that will allow the user to specify that they want the message data to be output to stdout rather than to a file.
• [TeamMsgExtractor #162] Added a wrapper for extract_msg that will be installed.
• Fixed some of the encoding names to allow them to actually be used in Python. The names they previously held were not aliases that currently exist.
• Added more documentation to constants.CODE_PAGES to give more information about what it is. As it is a list of the possible encodings an msg file can use, I also specified which ones were supported by Python 3.
• Moved the main code into a function so it is now callable from outside of the file.

Version 0.27.8

v0.27.8

• [TeamMsgExtractor #158] Fixed a spelling error in a function name that was causing it to not be seen. The function was called ceilDiv but was accidentally called as cielDiv.

Version 0.27.6

v0.27.6

• Fixed a few lines in data.py.