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

Add support for Python 3.8 #173

Merged
merged 12 commits into from
May 26, 2020
Merged

Add support for Python 3.8 #173

merged 12 commits into from
May 26, 2020

Conversation

921kiyo
Copy link
Contributor

@921kiyo 921kiyo commented May 22, 2020

Description

Kedro 0.16.* has been released, which supports Python 3.8. So we are also supporting Python 3.8 for Kedro-Viz plugins.

Development notes

Modified the e2e tests

Checklist

  • Read the contributing guidelines
  • Opened this PR as a 'Draft Pull Request' if it is work-in-progress
  • Updated the documentation to reflect the code changes
  • Added new entries to the RELEASE.md file
  • Added tests to cover my changes

Legal notice

  • I acknowledge and agree that, by checking this box and clicking "Submit Pull Request":

  • I submit this contribution under the Apache 2.0 license and represent that I am entitled to do so on behalf of myself, my employer, or relevant third parties, as applicable.

  • I certify that (a) this contribution is my original creation and / or (b) to the extent it is not my original creation, I am authorised to submit this contribution on behalf of the original creator(s) or their licensees.

  • I certify that the use of this contribution as authorised by the Apache 2.0 license does not violate the intellectual property rights of anyone else.

@@ -96,7 +104,7 @@ def call(cmd, verbose=False):
context.temp_dir = Path(tempfile.mkdtemp())


def after_scenario(context, feature):
Copy link
Contributor Author

Choose a reason for hiding this comment

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

feature arg was never used, so I removed it.

@921kiyo 921kiyo requested a review from mzjp2 May 22, 2020 13:50
@mzjp2
Copy link
Contributor

mzjp2 commented May 22, 2020

We need to pin kedro>=0.16 in requirements.txt, right?

cc @DmitriiDeriabinQB

@DmitriiDeriabinQB
Copy link
Contributor

We need to pin kedro>=0.16 in requirements.txt, right?

cc @DmitriiDeriabinQB

No, I don't think so. Earlier versions of Kedro won't install anyways if you're running Python 3.8.

Copy link
Contributor

@mzjp2 mzjp2 left a comment

Choose a reason for hiding this comment

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

Works for me, ran successfully on Python 3.8 locally :D

Copy link
Collaborator

@limdauto limdauto left a comment

Choose a reason for hiding this comment

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

LGTM! Although @DmitriiDeriabinQB suggested that maybe we should consider dropping pre-15 version of Kedro.

Copy link
Contributor

@DmitriiDeriabinQB DmitriiDeriabinQB left a comment

Choose a reason for hiding this comment

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

LGTM 👍

import tempfile
from pathlib import Path

from features.steps.sh_run import run
from features.steps.util import create_new_venv


def before_scenario(context, feature): # pylint: disable=unused-argument
def _should_exclude_scenario(scenario):
Copy link
Contributor

Choose a reason for hiding this comment

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

Nice! 👍

@921kiyo 921kiyo merged commit dd86d59 into develop May 26, 2020
@921kiyo 921kiyo deleted the feature/python3.8 branch May 26, 2020 09:28
@DmitriiDeriabinQB
Copy link
Contributor

LGTM! Although @DmitriiDeriabinQB suggested that maybe we should consider dropping pre-15 version of Kedro.

Yeah, I think that's the plan for the next release (3.4 or 4.0).

@richardwestenra richardwestenra mentioned this pull request May 26, 2020
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