gh-67512: Document IMAP4.append() flags argument#149907
Conversation
Documentation build overview
|
2cdbe5e to
43ef5ad
Compare
gvanrossum
left a comment
There was a problem hiding this comment.
Thanks! This looks like a good improvement -- there's no way to guess what to pass from the docs otherwise.
|
Thanks @savagemechanic for the PR, and @gvanrossum for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13. |
|
Thanks @savagemechanic for the PR, and @gvanrossum for merging it 🌮🎉.. I'm working now to backport this PR to: 3.14. |
|
Thanks @savagemechanic for the PR, and @gvanrossum for merging it 🌮🎉.. I'm working now to backport this PR to: 3.15. |
|
GH-153076 is a backport of this pull request to the 3.14 branch. |
|
GH-153077 is a backport of this pull request to the 3.13 branch. |
|
GH-153078 is a backport of this pull request to the 3.15 branch. |
Clarify the type and format expected for the
flagsargument toimaplib.IMAP4.append().The current documentation names the argument but does not explain that it should be an IMAP flag string. This can lead readers to pass a Python tuple or list of flags, which does not match the API. The updated text documents that
flagsmay beNoneor a string of IMAP flag tokens, shows a multi-flag example, and notes that parentheses are added automatically when omitted.Docs-only change.
Testing:
make -C Doc check./Doc/venv/bin/pre-commit run sphinx-lint --files Doc/library/imaplib.rst