Skip to content
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

Use cffi 1.17.0rc1 to test Python 3.13 support #8432

Closed

Conversation

edgarrmondragon
Copy link

@edgarrmondragon edgarrmondragon commented Jun 1, 2024

What do these changes do?

  • Use a prerelease of cffi to support testing with Python 3.13

Are there changes in behavior for the user?

Is it a substantial burden for the maintainers to support this?

Related issue number

Checklist

  • I think the code is well written
  • Unit tests for the changes exist
  • Documentation reflects the changes
  • If you provide code modification, please add yourself to CONTRIBUTORS.txt
    • The format is <Name> <Surname>.
    • Please keep alphabetical order, the file is sorted by names.
  • Add a new news fragment into the CHANGES/ folder
    • name it <issue_or_pr_num>.<type>.rst (e.g. 588.bugfix.rst)

    • if you don't have an issue number, change it to the pull request
      number after creating the PR

      • .bugfix: A bug fix for something the maintainers deemed an
        improper undesired behavior that got corrected to match
        pre-agreed expectations.
      • .feature: A new behavior, public APIs. That sort of stuff.
      • .deprecation: A declaration of future API removals and breaking
        changes in behavior.
      • .breaking: When something public is removed in a breaking way.
        Could be deprecated in an earlier release.
      • .doc: Notable updates to the documentation structure or build
        process.
      • .packaging: Notes for downstreams about unobvious side effects
        and tooling. Changes in the test invocation considerations and
        runtime assumptions.
      • .contrib: Stuff that affects the contributor experience. e.g.
        Running tests, building the docs, setting up the development
        environment.
      • .misc: Changes that are hard to assign to any of the above
        categories.
    • Make sure to use full sentences with correct case and punctuation,
      for example:

      Fixed issue with non-ascii contents in doctest text files
      -- by :user:`contributor-gh-handle`.

      Use the past tense or the present tense a non-imperative mood,
      referring to what's changed compared to the last released version
      of this project.

Copy link

codecov bot commented Jun 1, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.64%. Comparing base (8504b71) to head (9909716).
Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #8432   +/-   ##
=======================================
  Coverage   97.64%   97.64%           
=======================================
  Files         107      107           
  Lines       33067    33067           
  Branches     3885     3885           
=======================================
  Hits        32288    32288           
  Misses        562      562           
  Partials      217      217           
Flag Coverage Δ
CI-GHA 97.55% <ø> (ø)
OS-Linux 97.22% <ø> (ø)
OS-Windows 95.64% <ø> (ø)
OS-macOS 96.88% <ø> (ø)
Py-3.10.11 97.03% <ø> (-0.01%) ⬇️
Py-3.10.14 96.98% <ø> (ø)
Py-3.11.9 97.20% <ø> (ø)
Py-3.12.4 97.33% <ø> (ø)
Py-3.8.10 95.41% <ø> (ø)
Py-3.8.18 96.87% <ø> (ø)
Py-3.9.13 97.02% <ø> (ø)
Py-3.9.19 96.97% <ø> (ø)
Py-pypy7.3.16 96.54% <ø> (ø)
VM-macos 96.88% <ø> (ø)
VM-ubuntu 97.22% <ø> (ø)
VM-windows 95.64% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@@ -189,7 +189,7 @@ jobs:
pip-ci-${{ runner.os }}-${{ matrix.pyver }}-${{ matrix.no-extensions }}-
- name: Update pip, wheel, setuptools, build, twine
run: |
python -m pip install -U pip wheel setuptools build twine
python -m pip install -U pip wheel setuptools build twine cffi==0.17.0rc1
Copy link
Member

Choose a reason for hiding this comment

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

This seems redundant as the following step would do the same.

Copy link
Author

@edgarrmondragon edgarrmondragon Jun 1, 2024

Choose a reason for hiding this comment

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

Yeah, but pip (I think) has a dependency on cffi via cryptography so this step was failing on 3.13

Copy link
Member

Choose a reason for hiding this comment

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

Pip vendors all its deps so this would do nothing. Besides, all pip's deps are pure-python.

@edgarrmondragon edgarrmondragon changed the title Use cffi 0.17.0rc1 to test Python 3.13 support Use cffi 1.17.0rc1 to test Python 3.13 support Jun 1, 2024
@edgarrmondragon
Copy link
Author

It seems pycares is also causing issues

@Dreamsorcerer
Copy link
Member

Looks like uvloop is also failing to install currently. I suspect there's a good chance cffi will have made a stable release by the time that's sorted, so maybe not worth putting these changes in temporarily.

@bdraco
Copy link
Member

bdraco commented Aug 7, 2024

Looks like cffi 1.17.0 is now out

@Dreamsorcerer
Copy link
Member

I guess we close this then, as Dependabot will update it. Just waiting on uvloop now..

@edgarrmondragon edgarrmondragon deleted the cffi-prerelease branch August 7, 2024 12:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants