CM added the comment:
I understood what Ned meant, and I did seek advice from the third party
software creator, it was the first thing I did because like you stated I
thought it was an issue with the third party software and not python. Coming to
this bug website was my last resort but I can
CM added the comment:
Hi Thanks for your response.
So as you have correctly surmised I am using a software package call oof. I ran
the package using gdb and this is the output that I got. I'm having the same
issue on i.e. Segmentation fault on three machines, one is a Linux
Centos/R
New submission from CM:
Process: Python [556]
Path:
/opt/local/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python
Identifier: Python
Version: 2.7.10 (2.7.10)
Code Type: X86-64 (Native)
Parent Process: bash [510
New submission from CM:
On Windows (tested on XP), the datetime module (and, as reported online in [1],
time module) apparently gets the timezone only when a Python instance first
starts, but then never updates the timezone during the life of that Python
instance. So, if the user changes the
New submission from Marcus CM <[EMAIL PROTECTED]>:
When using maildir on windows, the maildir._dump_message erronously
added "\r\n" to "\r\r\n" : in mailbox.py
target.write(buffer.read().replace('\n', os.linesep))
--
components: Library (Lib)
me
New submission from Marcus CM <[EMAIL PROTECTED]>:
The __getaddr does not handle certain valid MAIL FROM well :
For eg,
<[EMAIL PROTECTED]> SIZE= AUTH=<>
would result in a mismatch of bracket handling.
Suggested fix is :-
def __getaddr(self, keyword, arg):
