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.
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
Acurl use Cython 3.0.8 #280
base: master
Are you sure you want to change the base?
Acurl use Cython 3.0.8 #280
Changes from all commits
6ee65ef
4c63ffa
c82883a
590e4a2
4393c9a
e6367af
dfbafce
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
OTOH, this function (and the one below it in this file) really can't raise, and so are valid
noexcept
candidates with no explanation needed.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, do we know why we are pinning to a specific version, especially a beta one? what are the conditions in the future under which we could remove the pin?
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.
eek -- the test should not be pinned to a different version than the main code, so it's good to change this (tho no pinning would be ideal).
it's been a while since i looked at this code, but IIRC, the tests install everything from setup.cfg as well as everything from the test-requirements.txt. so given that uvloop is already required by
setup.cfg
, we could delete it from here and avoid any future iterations of the different-pinning problem. WDYT?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.
I was getting errors due to it not the version of uvloop required for Cython 3. (This commit). Which is why I pinned it to version
0.21.0b1
. I'll put this PR back in drafts whilst I fix them etc.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.
ahhh, uvloop doesn't have a stable release for cython3 yet. that explains it. do we want to wait for upstream to cut a stable release? that should avoid us needing to do any pinning. if we don't want to wait, we can just stick a comment in explaining the situation, and Someone™ can remove the comment and the pin in the future....