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

Remove iodide specific code #878

Merged
merged 1 commit into from Dec 30, 2020
Merged

Remove iodide specific code #878

merged 1 commit into from Dec 30, 2020

Conversation

dalcde
Copy link
Contributor

@dalcde dalcde commented Dec 17, 2020

Iodide is no longer actively maintained, and in any case it would make more sense for iodide-specific code to belong to iodide.

Iodide is no longer actively maintained, and in any case it would make
more sense for iodide-specific code to belong to iodide.
@rth
Copy link
Member

rth commented Dec 17, 2020

Yes, we can do that, but let's merge it after the 0.16 release to keep compatibility with iodide for one more version. It's not an immediate blocker for anything as far as I know.

@rth rth added this to the 0.17.0 milestone Dec 17, 2020
@dalcde dalcde merged commit 860974b into pyodide:master Dec 30, 2020
@dalcde dalcde deleted the iodide branch December 30, 2020 05:54
joemarshall pushed a commit to joemarshall/pyodide that referenced this pull request Jan 3, 2021
Iodide is no longer actively maintained, and in any case it would make
more sense for iodide-specific code to belong to iodide.
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.

None yet

2 participants