-
Notifications
You must be signed in to change notification settings - Fork 73
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
Allow non-default string types in all metadata calls #444
Conversation
39ebc02
to
1bdb37c
Compare
this PR includes 443 NotLike... but no test? perhaps you want that 1 commit and a test in a different PR? rest seems good if the tests are passing. |
Will do the separate PR, I think. NotLike is used in one of these new tests but it could use its own.... |
Ah. Okay. Yes. Let’s get it in first with its own test. Then this work… which can also use the NotLike. |
50d92a7
to
aa24314
Compare
Should be merged after #445 because one of the tests uses |
Still ready for review, though. |
tests pass. |
nothing jumps out as concerning to me. feels like it's squash time. |
aa24314
to
7517198
Compare
Ok, squashed. |
@alanking, thoughts? |
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.
Overall seems fine. I had a couple of thoughts, but they're not really big concerns
Changes look good. Please resolve open conversations and squash |
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.
Hmm... sorry for the back and forth. Just took a look at Codacy and it seems to raise a couple of valid points. And of course we will need to get #445 in before this, as you said before.
Yup, no biggie... will take care of those. |
7e36603
to
ca07ee2
Compare
Done with codacy improvements for now. NotLike will reappear once we merge #445 (and rebase this over it); and u"..." is necessary for testing under Python2. |
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.
Looks good. #445 is in now. Please squash and #.
This permits use of bytestring text fields when modifying metadata under Python3, as well as unicode fields under Python2. We also test that bytestring and unicode types act as they should in metadata queries.
ca07ee2
to
90ea1ca
Compare
Here we patch the ModAVUMetadata interface in the Python client to allow both Unicode and bytestring fields everywhere, regardless of which string type is the norm for the running Python interpreter.
Included also: