New submission from Emil Styrke :
When a header with an encoded (QP or Base64) display_name is refolded, it may
lose (some of) its encoding. If it then contains illegal "atext" tokens, an
invalid header will result.
For example, `From: =?utf-8?Q?a=2C=2012345678901234567890123456
Emil Styrke added the comment:
eryksun, thank you for the explanation, the penny finally dropped for me. It's
the *other* child processes that keep the file open, not the parent. Actually
this bug started hitting me after I *stopped* doing exactly what you suggest
(fdopen on the temp
Emil Styrke added the comment:
I have experienced this issue with Python 2.7.8 and 2.7.9. It is almost the
same issue as the OP experiences as far as I can tell: spawn some Python
threads that each create a file, flush, fsync, close, then start a subprocess
which uses the file through the
Emil Styrke added the comment:
Ok, thanks for clearing that up. And yes, I meant the pythonpath variable in
the script, which seems to be derived from sys.executable.
But in that case, it's unfortunate that the c:\python27\scripts dir is not
created during install. I did win_add2path
New submission from Emil Styrke:
OS: Windows 7 Ultimate x64
Python version: 2.7.3 x64
win_add2path.py in the scripts directory is supposed to add the Scripts
directory according to its source. However, it tries to add
$PYTHONPATH/Scripts, when in fact the Scripts directory is at
$PYTHONPATH