GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||
GeezerVison is showing github.com — bpo-43680: Remove undocumented io.OpenWrapper by vstinner · Pull Request #25114 · python/cpython Conversation
|
| (Contributed by Yurii Karabas, Andrew Svetlov, Yury Selivanov and Kyle Stanley | ||
| in :issue:`42392`.) | ||
|
|
||
| * Remove the undocumented ``io.OpenWrapper`` and ``_pyio.OpenWrapper`` |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
OpenWrapper itself is not purposed to be used in user code. The main effect is that it changes builtin open if Python implementation is used. It can affect PyPy or other implementations.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
_pyio is supposed to be a drop-in replacement for the io module, whereas _pyio.open and io.open behave differently.
See https://bugs.python.org/issue43682 which would make it possible to use _pyio.open as a method, rather than having to go through OpenWrapper.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Doc/whatsnew/3.10.rst
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
I wrote PR #25357 to only deprecate the class, rather than removing it. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.