New submission from Shai Berger <s...@platonix.com>:
In mailbox.py in the stdlib, the functions MH.add and MH.__setitem__ take a
message object and dump it to a file in the MH folder, which is good and well.
However, they only call self._dump_sequences() if the message was a
Shai Berger added the comment:
Following the last comment, and just as clarification for anyone else running
into this and thinking like me: The bumped code is not included in v3.5.2, and
v3.5.3 hasn't been released yet. Should it be undone?
No, because the bump which was encountered by John
Shai Berger added the comment:
Just got bit by this.
Tim Peters said:
It is odd, but really no odder than zero values of other types evaluating to
false in Boolean contexts.
I disagree. Midnight is not a zero value, it is just a value. It does not
have any special qualities analogous
New submission from Shai Berger:
At least on posix systems, os.write says it takes a string, but in fact it
barfs on strings -- it needs bytes.
$ python
Python 3.3.1 (default, May 6 2013, 16:18:33)
[GCC 4.7.2] on linux
Type help, copyright, credits or license for more information.
import os
Shai Berger added the comment:
Hi,
the reason this stuff can't change [... is] backward compatibility.
Thanks, but this is still unclear to me. The required fix for code that would
break because of the change I propose, is removal of dead code which looks
misleadingly alive
Shai Berger added the comment:
Oh, sure, this was unclear of me. I thought you were talking about Python 3.4.
I wasn't really expecting this to be fixed in the stable branches.
Thanks,
Shai.
--
___
Python tracker rep...@bugs.python.org
http
New submission from Shai Berger:
Consider the following directory structure:
a-\
__init__.py
b.py
b-|
__init__.py
Now, in Python (I checked 2.7.3 and 3.2.3, haven't seen the issue mentioned
anywhere so I suspect it is also in later Pythons), if you import a.b, you
always get
Shai Berger added the comment:
Thanks for the quick response.
If this isn't changing, I'd definitely want better documentation. In
particular, the rationale behind this should be explained.
I submitted the bug because a co-worker unintentionally caused a whole suite of
tests to be ignored
