Skip to content

Conversation

@iscai-msft
Copy link
Contributor

@iscai-msft iscai-msft commented Mar 18, 2022

Right now we're more stringent about content input, we expect it to be str / bytes or an iterable / asynciterable. This impacts storage live tests and is also incorrect because we should allow inputs with just a read() proeprty. I'm switching my code to be more like the pipeline transport code here and duck-typing instead.

Also at the same time, saw a gap to get rid of some py2/py3 code, so did some code unification as well

Running against live storage: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1443919&view=results. Will not see all tests passing, @jalauzon-msft is fixing the other failed tests in main right now, but should see the failing stream tests pass

Copy link
Member

@xiangyan99 xiangyan99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we still need both rest and rest_py3?

@iscai-msft
Copy link
Contributor Author

@xiangyan99 no, I want to refactor that later in a separate PR

@iscai-msft iscai-msft merged commit dbad6c1 into main Mar 18, 2022
@iscai-msft iscai-msft deleted the fix_stream branch March 18, 2022 21:40
rakshith91 pushed a commit to rakshith91/azure-sdk-for-python that referenced this pull request Apr 7, 2022
rakshith91 pushed a commit to rakshith91/azure-sdk-for-python that referenced this pull request Apr 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants