{{ message }}
bpo-16135: Cleanup: Code rot left over from OS/2 support#4147
Merged
vstinner merged 1 commit intoOct 27, 2017
Merged
Conversation
Contributor
Sorry, something went wrong.
…ant since removal of OS/2 support.
vstinner
approved these changes
Oct 27, 2017
vstinner
left a comment
vstinner
left a comment
Member
There was a problem hiding this comment.
LGTM.
Sorry, something went wrong.
Member
|
Merged, thanks. |
Sorry, something went wrong.
Contributor
Author
|
Thanks! |
Sorry, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.
Originally extracted from #4137, this removes the last remaining references to the
PYCC_VACPPmacro, which relates to supporting compiling with VisualAge C++ on OS/2. OS/2 support was removed in Python 3.4 as prescribed by PEP-11. These last bits still survived.Don't know if I need an issue on bpo for this as well...
@Haypo
https://bugs.python.org/issue16135