Skip to content

Conversation

vstinner
Copy link
Member

@vstinner vstinner commented Sep 12, 2017

https://bugs.python.org/issue30923

@serhiy-storchaka
Copy link
Member

Usually we don't backport changes that just silence compiler warnings.

@skrah
Copy link
Contributor

skrah commented Sep 12, 2017

It's a double edged sword: If we don't backport, other backports become more difficult because of conflicts. Technically we should take out _codecs_iso2022.c, but I assume that @Haypo has given it another thorough look.

@vstinner
Copy link
Member Author

Usually we don't backport changes that just silence compiler warnings.

IMHO the change is simple enough to justify a backport. I would like to fix these warnings to be able to detect more serious warnings.

Technically we should take out _codecs_iso2022.c, but I assume that @Haypo has given it another thorough look.

I read it and it seems safe.

@vstinner vstinner merged commit c0e7736 into python:3.6 Sep 12, 2017
@miss-islington
Copy link
Contributor

Thanks, @Haypo!

@vstinner vstinner deleted the fall_through36 branch September 12, 2017 23:09
@vstinner
Copy link
Member Author

Thanks for the review @skrah.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants