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.

Sign up for GitHub

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

Jump to bottom

[KED-1116] Python 3.8 support #124

Closed
Pet3ris opened this issue Oct 14, 2019 · 8 comments
Closed

[KED-1116] Python 3.8 support #124

Pet3ris opened this issue Oct 14, 2019 · 8 comments
Labels
Issue: Feature Request New feature or improvement to existing feature

Comments

@Pet3ris
Copy link

Pet3ris commented Oct 14, 2019

Description

What's the timeline for 3.8 support? Kedro is currently marked as <3.8, but I assume few problems exist to allow 3.8?

Context

New version of Python.

Possible Implementation

Possible Alternatives
@Pet3ris Pet3ris added the Issue: Feature Request New feature or improvement to existing feature label Oct 14, 2019
@921kiyo
Copy link
Contributor

921kiyo commented Oct 14, 2019 •
edited
Loading

@Pet3ris Thank you for opening the feature request! We will discuss it and the timeline internally :)

@lorenabalan lorenabalan changed the title Python 3.8 support [KED-1116] Python 3.8 support Oct 17, 2019
@DmitriiDeriabinQB
Copy link
Contributor

@Pet3ris We had a stab at it, and encountered some compatibility issues downstream. Specifically, numpy C-modules are not being installed properly on Python 3.8 on conda. We will keep track of it and get back you when we have any progress.

@lorenabalan
Copy link
Contributor

lorenabalan commented Dec 2, 2019 •
edited
Loading

Update: conda & numpy seem to be fine. Currently blocked by apache/arrow#5685

@lorenabalan lorenabalan mentioned this issue Dec 12, 2019
Closed
@Pet3ris
Copy link
Author

Pet3ris commented Jan 8, 2020

Have Arrow started building 3.8 wheels? See here: apache/arrow@6c6754a. Does this mean 3.8 is good to go?

@Pet3ris
Copy link
Author

Pet3ris commented Jan 8, 2020

FYI @921kiyo @DmitriiDeriabinQB @lorenabalan

@DmitriiDeriabinQB
Copy link
Contributor

The latest pyarrow version 0.15.1, unfortunately, does not come with Python 3.8 wheels, so running pip install pyarrow fails on 3.8 at the moment: "Best guess would be end of January but it may be sometime in February"

@lorenabalan lorenabalan mentioned this issue Jan 28, 2020
Closed
@lorenabalan
Copy link
Contributor

Hey guys, latest commit on develop aims to enable 3.8 compatibility fe48953 - feel free to have a play and let us know if you find any issues. Please note that pyspark is a known issue.

@lorenabalan
Copy link
Contributor

Thank you for the feature request! I am now closing this as Python 3.8 compatibility was enabled starting with version 0.16.0 released today.

This was referenced May 25, 2020
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue: Feature Request New feature or improvement to existing feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@Pet3ris @lorenabalan @921kiyo @DmitriiDeriabinQB