-
Notifications
You must be signed in to change notification settings - Fork 1.1k
PYTHON-5289 Validate ignored bits are 0 on write for bson.BinaryVector #2397
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.
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
base: master
Are you sure you want to change the base?
PYTHON-5289 Validate ignored bits are 0 on write for bson.BinaryVector #2397
Conversation
…s will sync up with specifications when pull/1812 is merged.
Failing tests are unrelated. |
@@ -522,6 +530,12 @@ def as_vector(self) -> BinaryVector: | |||
dtype_format = "B" | |||
format_string = f"<{n_values}{dtype_format}" | |||
unpacked_uint8s = list(struct.unpack_from(format_string, self, position)) | |||
if padding and n_values and unpacked_uint8s[-1] & (1 << padding) - 1 != 0: | |||
warnings.warn( | |||
"Vector has a padding P, but bits in the final byte lower than P are non-zero. In the next major version, they must be zero.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So in the next major version, this warning will become an error to match the behavior in from_vector
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. We make the significant change (exception not warning) in the next major change and document in changelog and api. The ticket for that is PYTHON-5280 and has 5.0 as its fix version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add "pymongo version 5.0" rather than "the next major version". This helps should them the version (5.0) and that the warning is coming from pymongo.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any docs or changelog we need to update here?
except Exception as exc: | ||
self.assertIsInstance(exc, ValueError) | ||
else: | ||
self.fail("Failed to raise an exception.") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This assertion should use assertRaises.
@@ -522,6 +530,12 @@ def as_vector(self) -> BinaryVector: | |||
dtype_format = "B" | |||
format_string = f"<{n_values}{dtype_format}" | |||
unpacked_uint8s = list(struct.unpack_from(format_string, self, position)) | |||
if padding and n_values and unpacked_uint8s[-1] & (1 << padding) - 1 != 0: | |||
warnings.warn( | |||
"Vector has a padding P, but bits in the final byte lower than P are non-zero. In the next major version, they must be zero.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add "pymongo version 5.0" rather than "the next major version". This helps should them the version (5.0) and that the warning is coming from pymongo.
This is the implementation of the spec changes applied in specifications/pull/1812.