Thanks!

@kartikanand : this change needs to be backported, can you try to cherry-pick the change to the 3.6 branch using "git cherry-pick -x "?
https://docs.python.org/3.6/library/enum.html

IHMO it's worth it to backport the change to Python 3.6. @kartikanand can you please try to cherry-pick the change to Python 3.6 using "git cherry-pick -x " ?

@Haypo It seems @Mariatta has already merged it in 3.6 - #367

@Haypo It seems @Mariatta has already merged it in 3.6 - #367

Oh right, @Mariatta just forgot to mention the bpo number in its PR and commit message. I updated the issue, thanks.

@berkerpeksag berkerpeksag removed the needs backport to 3.6 label an hour ago

Why did you remove the label? Are you using this label to check if the backport was done or not? I prefer to keep the label even if the change was already backported to 3.6.

Are you using this label to check if the backport was done or not?

Yes, this has been used to track backport statuses for a while. I suggest opening an issue at python/core-workflow to discuss this :)