Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(12)

Unified Diff: Doc/whatsnew/3.3.rst

Issue 15573: Support unknown formats in memoryview comparisons
Patch Set: Created 7 years, 7 months ago
Use n/p to move between diff chunks; N/P to move between comments. Please Sign in to add in-line comments.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « Doc/library/stdtypes.rst ('k') | Lib/test/test_buffer.py » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
--- a/Doc/whatsnew/3.3.rst
+++ b/Doc/whatsnew/3.3.rst
@@ -127,7 +127,6 @@
and the view is read-only. (Contributed by Antoine Pitrou in
:issue:`13411`)
-
* Arbitrary slicing of any 1-D arrays type is supported. For example, it
is now possible to reverse a memoryview in O(1) by using a negative step.
@@ -143,6 +142,12 @@
now returns an integer (in accordance with the struct module syntax).
For returning a bytes object the view must be cast to 'c' first.
+* memoryview comparisons now use the logical structure of the operands
+ and compare all array elements by value. All format strings in struct
+ module syntax are supported. Views with unrecognised format strings
+ are still permitted, but will always compare as unequal, regardless
+ of view contents.
+
* For further changes see `Build and C API Changes`_ and `Porting C code`_ .
.. _pep-393:
« no previous file with comments | « Doc/library/stdtypes.rst ('k') | Lib/test/test_buffer.py » ('j') | no next file with comments »

RSS Feeds Recent Issues | This issue
This is Rietveld 894c83f36cb7+