Skip to content

Contradictory terminology about native types #47

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Veedrac wants to merge 1 commit into from
Closed

Contradictory terminology about native types #47

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/whatsnew.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -247,9 +247,9 @@ Many small improvements and fixes have been made across the project. Some highli

- Improved compatibility with py2exe (`issue #31 <https://github.com/PythonCharmers/python-future/issues/31>`_).

- The ``future.utils.bytes_to_native_str`` function now returns a ``newbytes``
object on Py2. (`Issue #47
<https://github.com/PythonCharmers/python-future/issues/47>`_).
- The ``future.utils.bytes_to_native_str`` function now returns a ``native_str``
object and ``future.utils.native_str_to_bytes`` returns a ``newbytes`` on Py2.
(`Issue #47 <https://github.com/PythonCharmers/python-future/issues/47>`_).

- The backported ``http.client`` module and related modules use other new
backported modules such as ``email``. As a result they are more compliant
Expand Down