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

Require typing_extensions for py<3.8 only #484

Merged
merged 1 commit into from
Jul 27, 2020

Conversation

mgorny
Copy link
Contributor

@mgorny mgorny commented Jul 27, 2020

What do these changes do?

They make it possible to run on py3.8+ without external typing_extensions. This also fixes support for py3.9 where typing_extensions don't work (yet).

Are there changes in behavior for the user?

Nope.

Related issue number

Nope.

Checklist

  • I think the code is well written
  • Unit tests for the changes exist
  • Documentation reflects the changes
  • Add a new news fragment into the CHANGES folder
    • name it <issue_id>.<type> (e.g. 588.bugfix)
    • if you don't have an issue_id change it to the pr id after creating the PR
    • ensure type is one of the following:
      • .feature: Signifying a new feature.
      • .bugfix: Signifying a bug fix.
      • .doc: Signifying a documentation improvement.
      • .removal: Signifying a deprecation or removal of public API.
      • .misc: A ticket has been closed, but it is not of interest to users.
    • Make sure to use full sentences with correct case and punctuation, for example: Fix issue with non-ascii contents in doctest text files.

@psf-chronographer psf-chronographer bot added the bot:chronographer:provided There is a change note present in this PR label Jul 27, 2020
All the names imported from typing_extensions are available already
in Python 3.8, so there is no need to use the additional dependency
there.  Furthermore, typing_extensions currently do not support
Python 3.9, effectively blocking yarl from doing so.  To solve this,
use external typing_extensions only for py<3.8, and just use builtin
typing in 3.8+.
@codecov
Copy link

codecov bot commented Jul 27, 2020

Codecov Report

Merging #484 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #484   +/-   ##
=======================================
  Coverage   99.57%   99.57%           
=======================================
  Files           4        4           
  Lines         708      708           
  Branches      157      157           
=======================================
  Hits          705      705           
  Misses          3        3           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b73957c...2f2f1a0. Read the comment docs.

@webknjaz webknjaz merged commit c6b6be3 into aio-libs:master Jul 27, 2020
@webknjaz
Copy link
Member

@mgorny thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bot:chronographer:provided There is a change note present in this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants