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

Expose that the python API is Python3.5+ only #616

Merged
merged 4 commits into from
Jan 8, 2019
Merged

Expose that the python API is Python3.5+ only #616

merged 4 commits into from
Jan 8, 2019

Conversation

TimZaman
Copy link
Contributor

@TimZaman TimZaman commented Jan 3, 2019

Adding these classifiers (many are the same as e.g. TensorFlow) makes sure pip/pypi index pick these up as being 3.5+ only, so that developers on Python 2 are not suprised when it fails on Python 3 syntax (e.g. typehints are only py 3.5+).


This change is Reviewable

Adding these classifiers (many are the same as e.g. TensorFlow) makes sure pip/pypi index pick these up as being 3.5+ only, so that developers on Python 2 are not suprised when it fails on Python 3 syntax (e.g. typehints are only py 3.5+).
@k8s-ci-robot
Copy link
Contributor

Hi @TimZaman. 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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.

1 similar comment
@k8s-ci-robot
Copy link
Contributor

Hi @TimZaman. 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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.

@yebrahim
Copy link
Contributor

yebrahim commented Jan 3, 2019

I think we're actually Python 3.6+ only. @qimingj @gaoning777 @Ark-kun

@TimZaman
Copy link
Contributor Author

TimZaman commented Jan 4, 2019

Thanks @yebrahim , reflected that in change. Tested 3.7 to work too.

@yebrahim
Copy link
Contributor

yebrahim commented Jan 4, 2019

Yup, >= 3.6. I'll let @qimingj or @gaoning777 take a look first though. Thanks @TimZaman.

@TimZaman
Copy link
Contributor Author

TimZaman commented Jan 5, 2019

@qimingj done, should be g2g. (Even if 3.5 doesn't work, at least with this MR we won't be bothering Python2 users with them reeling in a python3 package.)

@Ark-kun
Copy link
Contributor

Ark-kun commented Jan 5, 2019

I think we're actually Python 3.6+ only.

I thought we were 3.5+. 3.6+ is much better for me (variable typing).

@Ark-kun
Copy link
Contributor

Ark-kun commented Jan 5, 2019

We should probably just use python-requires in setup.py. See https://packaging.python.org/guides/distributing-packages-using-setuptools/#python-requires

@TimZaman
Copy link
Contributor Author

TimZaman commented Jan 5, 2019

That's fairly new, so we should do both:

  • added python_requires.

@Ark-kun
Copy link
Contributor

Ark-kun commented Jan 7, 2019

/ok-to-test

@TimZaman
Copy link
Contributor Author

TimZaman commented Jan 7, 2019

I think this one is g2g

@Ark-kun
Copy link
Contributor

Ark-kun commented Jan 8, 2019

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot assigned Ark-kun and unassigned Ark-kun Jan 8, 2019
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Ark-kun

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Ark-kun

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot merged commit 7c5c683 into kubeflow:master Jan 8, 2019
yebrahim pushed a commit to yebrahim/pipelines that referenced this pull request Jan 8, 2019
* Expose that the python API is Python3.5+ only

Adding these classifiers (many are the same as e.g. TensorFlow) makes sure pip/pypi index pick these up as being 3.5+ only, so that developers on Python 2 are not suprised when it fails on Python 3 syntax (e.g. typehints are only py 3.5+).

* Update setup.py

* Update setup.py

* Update setup.py
Linchin pushed a commit to Linchin/pipelines that referenced this pull request Apr 11, 2023
* There was a syntax error so we weren't GC'ing deployments

Fix: kubeflow#616
magdalenakuhn17 pushed a commit to magdalenakuhn17/pipelines that referenced this pull request Oct 22, 2023
* Export LoggerRequest, Fix local logger README

* Update B to Bytes in Logger struct
HumairAK pushed a commit to red-hat-data-services/data-science-pipelines that referenced this pull request Mar 11, 2024
* Update README.md

* Update README.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants