-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
feat(sdk): Accept newer typing-extensions
versions
#7632
Conversation
Hi @mai-nakagawa. Thanks for your PR. I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
typing-extensions
versiontyping-extensions
versions
Thanks for your contribution, @mai-nakagawa! I agree that broadening the pinned typing-extensions version is an improvement. I also agree that this is safe, so long developers ensure any typing-extension features they use also work on Python 3.7 (which is something we do for all other libraries). /test all |
It would be great to have this feature. We are currently blocked by this due to a compatibility issue. So, it would be awesome if everyone could have a pre-release with this change. Thank you @mai-nakagawa! |
@mai-nakagawa, could you please add a bullet in our release notes indicating that we're changing the version? After that, I think we should be good to merge and it will be included in our alpha.2 release. (cc: @jgoodman8) |
@connor-mccarthy Thanks for your review! Added a description to the release notes by 0faf033. |
/lgtm Thanks @mai-nakagawa! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: connor-mccarthy The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Thank you for the PR! I'm working on a project called |
There is a conflicting dependency in apache-airflow 2.3.0 - apache-airflow 1.23.0 -> rich '12.3.0' -> typing-extensions (>=4.0.0,<5.0); python_version < "3.9" - kfp 1.8.12 -> typing-extensions (<4,>=3.7.4); python_version < "3.9" This issue will be resolved when kfp releases a new version because kfp already changed the cap in kubeflow/pipelines#7632. PiperOrigin-RevId: 446074079
Awesome, @jiyongjung0! Really glad to hear that this is unblocking lots of different projects. |
There is a conflicting dependency in apache-airflow 2.3.0 - apache-airflow 1.23.0 -> rich '12.3.0' -> typing-extensions (>=4.0.0,<5.0); python_version < "3.9" - kfp 1.8.12 -> typing-extensions (<4,>=3.7.4); python_version < "3.9" This issue will be resolved when kfp releases a new version because kfp already changed the cap in kubeflow/pipelines#7632. PiperOrigin-RevId: 446074079
There is a conflicting dependency in apache-airflow 2.3.0 - apache-airflow 1.23.0 -> rich '12.3.0' -> typing-extensions (>=4.0.0,<5.0); python_version < "3.9" - kfp 1.8.12 -> typing-extensions (<4,>=3.7.4); python_version < "3.9" This issue will be resolved when kfp releases a new version because kfp already changed the cap in kubeflow/pipelines#7632. PiperOrigin-RevId: 446074079
There is a conflicting dependency in apache-airflow 2.3.0 - apache-airflow 1.23.0 -> rich '12.3.0' -> typing-extensions (>=4.0.0,<5.0); python_version < "3.9" - kfp 1.8.12 -> typing-extensions (<4,>=3.7.4); python_version < "3.9" This issue will be resolved when kfp releases a new version because kfp already changed the cap in kubeflow/pipelines#7632. PiperOrigin-RevId: 446074079
There is a conflicting dependency in apache-airflow 2.3.0 - apache-airflow 1.23.0 -> rich '12.3.0' -> typing-extensions (>=4.0.0,<5.0); python_version < "3.9" - kfp 1.8.12 -> typing-extensions (<4,>=3.7.4); python_version < "3.9" This issue will be resolved when kfp releases a new version because kfp already changed the cap in kubeflow/pipelines#7632. PiperOrigin-RevId: 446236647
* Accept newer typing-extensions versions * Add a description to the release notes.
There is a conflicting dependency in apache-airflow 2.3.0 - apache-airflow 1.23.0 -> rich '12.3.0' -> typing-extensions (>=4.0.0,<5.0); python_version < "3.9" - kfp 1.8.12 -> typing-extensions (<4,>=3.7.4); python_version < "3.9" This issue will be resolved when kfp releases a new version because kfp already changed the cap in kubeflow/pipelines#7632. PiperOrigin-RevId: 446236647 (cherry picked from commit 2df92b3) Co-authored-by: jiyongjung <jiyongjung@google.com>
Hi, @connor-mccarthy Is there a plan to release a new python package for kfp 1.x? It seems like the package wasn't released for two months and this PR wasn't included in any releases. |
Hi, @jiyongjung0. Looks like these changes were only applied to v2, but you're working with v1. I have a PR #7801 to mirror these changes in v1 and we can release once that is merged. |
* Accept newer typing-extensions versions * Add a description to the release notes.
Fixes #7631.
I think it's no problem that the SDK accepts newer
typing-extensions
versions because:typing-extensions 4.0.0
has some backwards-incompatible changes, however, these changes affect only Python 3.5 and older. See Removed in version 4.0.0 of typing-extensions for more in detail.typing-extensions 4.2.0
drops support Python 3.6 as per Release 4.2.0 of typing-extensions, however, it does not affect as the SDK drop support for python 3.6 by feat(sdk)!: drop support for python 3.6 #7303typing-extensions>=3.7.4,<5
but changed totyping-extensions>=3.7.4,<4
by feat(sdk)!: drop support for python 3.6 #7303. But I assume it didn't have to. I presume the change was made because there is a following statement intyping-extensions PyPI
: