Skip to content
This repository has been archived by the owner on Jun 24, 2021. It is now read-only.

JDK-8230778: Build the javafx.web module with Python 3 instead of Python 2 #579

Closed
ebourg opened this issue Sep 4, 2019 · 7 comments
Closed
Labels
bug Something isn't working documentation Updates or additions to documentation duplicate This issue or pull request already exists toolchain-upgrade

Comments

@ebourg
Copy link
Contributor

ebourg commented Sep 4, 2019

Python will be EOL on January 1st 2020 and the major Linux distributions are in the process of phasing it out. The javafx.web module relies on several Python 2 scripts to build and they don't work with Python 3. Converting them to Python 3 will be necessary to be able to build OpenFX on the upcoming Linux distributions.

@kevinrushforth
Copy link
Collaborator

I filed a pair of bugs in JBS to track this:

JDK-8230779: WebKit build fails with python3
JDK-8230778: Upgrade to python3 for building WebKit

If it is feasible, we should fix the build to allow WebKit to be built with either python2 or python3. This would be done ahead of actually switching the production builds to use python3.

@kevinrushforth kevinrushforth changed the title Build the javafx.web module with Python 3 instead of Python 2 JDK-8230778: Build the javafx.web module with Python 3 instead of Python 2 Sep 9, 2019
@kevinrushforth kevinrushforth added bug Something isn't working documentation Updates or additions to documentation toolchain-upgrade duplicate This issue or pull request already exists labels Sep 9, 2019
@kevinrushforth
Copy link
Collaborator

@ebourg thanks for reporting this. We can use the two JBS issues to track this further.

@ebourg
Copy link
Contributor Author

ebourg commented Sep 9, 2019

Thank you for forwarding the issue.

@shirishag75
Copy link

any update on this issue @kevinrushforth ?

@kevinrushforth
Copy link
Collaborator

This issue tracker is no longer being used. See the above comment as to where it is being tracked.

@kevinrushforth
Copy link
Collaborator

To answer your question though, there has not yet been any progress on this.

@ebourg
Copy link
Contributor Author

ebourg commented Apr 22, 2020

The OpenJDK issue tracker is closed to mere mortals unfortunately, I hope we'll still be able to use the GitHub one.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working documentation Updates or additions to documentation duplicate This issue or pull request already exists toolchain-upgrade
Projects
None yet
Development

No branches or pull requests

3 participants