Change by sblondon :
--
keywords: +patch
pull_requests: +5419
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issue32800>
___
_
New submission from sblondon :
The documentation about namespace of ElemenTree
(https://docs.python.org/3/library/xml.etree.elementtree.html#parsing-xml-with-namespaces)
has a link for 'default namespace' to
'https://www.w3.org/TR/2006/REC-xml-names-20060816/#defaulting'.
sblondon added the comment:
If the access is read-only, the lock is not required [1]. However, I agree
it does not worth to be more complex (changing the signature of the
subclass or adding another context manager for the lock).
I updated the patch and documentation so the mailbox is locked at
Change by sblondon :
--
keywords: +patch
pull_requests: +4673
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue32234>
___
___
Python-
sblondon added the comment:
Currently, the implementation of .close() methods call flush() and
unlock() if it's needed.
About the ambiguity for the enter call, I think the context manager
should provide access to Mailbox, not a lock. If a lock is needed, we
could imagine another co
New submission from sblondon :
mailbox.Mailbox has a .close() method that should be called at the end of
Mailbox use.
I think it would be nice to use Mailbox instances with a 'with' statement so
.close() will be called it automatically. So there is no need to check for
which f
