Skip to content

Conversation

@mcepl
Copy link
Contributor

@mcepl mcepl commented Apr 22, 2018

Just checking whether this is a good idea at all. If so, I will add metadata required.

https://bugs.python.org/issue33336

@vstinner vstinner requested a review from warsaw June 4, 2018 15:07
@mcepl
Copy link
Contributor Author

mcepl commented Jun 4, 2018

I would love to eventually have some way how to make moving messages universally possible (https://bugs.python.org/issue33327), but this is the least what I can hope for.

Copy link
Member

@vstinner vstinner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should add a ".. versionchanged:: 3.7" markup near https://docs.python.org/dev/library/imaplib.html#imaplib.IMAP4.uid (Doc/library/imaplib.rst) to document that MOVE is now supported.

@mcepl
Copy link
Contributor Author

mcepl commented Jun 21, 2018

You should add a ".. versionchanged:: 3.7" markup near https://docs.python.org/dev/library/imaplib.html#imaplib.IMAP4.uid (Doc/library/imaplib.rst) to document that MOVE is now supported.

@vstinner I still hold that this is not change in API. We never documented which IMAP commands are supported in IMAP4.uid, so there is no change in documentation.

I would like this bugfix be ported to other older versions of Python, which won't happen for change of API.

And yes, if calling this bugfix as change of API makes you stop stalling merging of this PR (I thought we went through all this on IRC, but apparently that discussion didn't change anything), I am willing to shut up and let it be limited to 3.8. Better that than nothing.

Copy link
Member

@vstinner vstinner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

I don't know the IMAP protocol nor the imaplib module. I would be more confortable if someone from the "email team", @warsaw or someone else review this PR. But this PR was created in April, 3 monhs ago, and didn't get any review whereas the PR looks safe and good (to me).

I suggest to backport the change to 2.7, 3.6 and 3.7 branches.

I will merge this PR next week except if someone show up against it.

@@ -0,0 +1,2 @@
``imaplib`` now allows ``MOVE`` command in ``IMAP4.uid()`` and potentially
as a name of supported method of ``IMAP4`` object.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would you mind to add a reference to the RFC 6851? Example:

imaplib now allows MOVE command in IMAP4.uid() (RFC 6851: IMAP MOVE Extension)
and potentially as a name of supported method of IMAP4 object.

@vstinner
Copy link
Member

@bitdancer, @warsaw: Would you mind to review this imaplib PR?

@bedevere-bot
Copy link

GH-8370 is a backport of this pull request to the 2.7 branch.

@bedevere-bot
Copy link

GH-8373 is a backport of this pull request to the 3.6 branch.

@bedevere-bot
Copy link

GH-8386 is a backport of this pull request to the 3.7 branch.

@miss-islington
Copy link
Contributor

Thanks @mcepl for the PR, and @vstinner for merging it 🌮🎉.. I'm working now to backport this PR to: 2.7, 3.6, 3.7.
🐍🍒⛏🤖

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Jul 23, 2018
imaplib now allows MOVE command in IMAP4.uid() (RFC 6851:
IMAP MOVE Extension) and potentially as a name of supported
method of IMAP4 object.
(cherry picked from commit caa331d)

Co-authored-by: Matěj Cepl <[email protected]>
@bedevere-bot
Copy link

GH-8409 is a backport of this pull request to the 3.7 branch.

@bedevere-bot
Copy link

GH-8410 is a backport of this pull request to the 3.6 branch.

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Jul 23, 2018
imaplib now allows MOVE command in IMAP4.uid() (RFC 6851:
IMAP MOVE Extension) and potentially as a name of supported
method of IMAP4 object.
(cherry picked from commit caa331d)

Co-authored-by: Matěj Cepl <[email protected]>
@bedevere-bot
Copy link

GH-8411 is a backport of this pull request to the 2.7 branch.

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Jul 23, 2018
imaplib now allows MOVE command in IMAP4.uid() (RFC 6851:
IMAP MOVE Extension) and potentially as a name of supported
method of IMAP4 object.
(cherry picked from commit caa331d)

Co-authored-by: Matěj Cepl <[email protected]>
@mcepl mcepl deleted the 33336_legalize_move_command branch July 23, 2018 12:46
miss-islington added a commit that referenced this pull request Jul 23, 2018
imaplib now allows MOVE command in IMAP4.uid() (RFC 6851:
IMAP MOVE Extension) and potentially as a name of supported
method of IMAP4 object.
(cherry picked from commit caa331d)

Co-authored-by: Matěj Cepl <[email protected]>
vstinner pushed a commit that referenced this pull request Jul 23, 2018
imaplib now allows MOVE command in IMAP4.uid() (RFC 6851:
IMAP MOVE Extension) and potentially as a name of supported
method of IMAP4 object.
(cherry picked from commit caa331d)

Co-authored-by: Matěj Cepl <[email protected]>
miss-islington added a commit that referenced this pull request Jul 23, 2018
imaplib now allows MOVE command in IMAP4.uid() (RFC 6851:
IMAP MOVE Extension) and potentially as a name of supported
method of IMAP4 object.
(cherry picked from commit caa331d)

Co-authored-by: Matěj Cepl <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants