Fix code generation #2545
Merged
Fix code generation #2545
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Python 3.8 does not support the new syntax used in utils/run-unasync.py, but using Python 3.12 failed because tokenization of f-strings changed in Python 3.12 in a way that was not supported by unasync 0.5.0.
|
A documentation preview will be available soon. Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
github-actions bot
pushed a commit
that referenced
this pull request
May 3, 2024
Python 3.8 does not support the new syntax used in utils/run-unasync.py, but using Python 3.12 failed because tokenization of f-strings changed in Python 3.12 in a way that was not supported by unasync 0.5.0. (cherry picked from commit 2aef84e)
github-actions bot
pushed a commit
that referenced
this pull request
May 3, 2024
Python 3.8 does not support the new syntax used in utils/run-unasync.py, but using Python 3.12 failed because tokenization of f-strings changed in Python 3.12 in a way that was not supported by unasync 0.5.0. (cherry picked from commit 2aef84e)
pquentin
added a commit
that referenced
this pull request
May 3, 2024
Python 3.8 does not support the new syntax used in utils/run-unasync.py, but using Python 3.12 failed because tokenization of f-strings changed in Python 3.12 in a way that was not supported by unasync 0.5.0. (cherry picked from commit 2aef84e) Co-authored-by: Quentin Pradet <quentin.pradet@elastic.co>
pquentin
added a commit
that referenced
this pull request
May 3, 2024
Python 3.8 does not support the new syntax used in utils/run-unasync.py, but using Python 3.12 failed because tokenization of f-strings changed in Python 3.12 in a way that was not supported by unasync 0.5.0. (cherry picked from commit 2aef84e) Co-authored-by: Quentin Pradet <quentin.pradet@elastic.co>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Python 3.8 does not support the new syntax used in utils/run-unasync.py, but using Python 3.12 failed because tokenization of f-strings changed in Python 3.12 in a way that was not supported by unasync 0.5.0.