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 #170

Closed
Legrandin opened this issue Oct 15, 2019 · 9 comments
Closed

Add support for Python 3.8 #170

Legrandin opened this issue Oct 15, 2019 · 9 comments

Comments

@Legrandin
Copy link

Legrandin commented Oct 15, 2019

Python 3.8 was released on October 14th, 2019.

Can it be added to cibuildwheel?

@YannickJadoul
Copy link
Member

YannickJadoul commented Oct 15, 2019

Yessss, thanks for the reminder! Should be reasonably quick to implement, though it depends a bit on the Python versions AppVeyor and Azure are offering.

@YannickJadoul
Copy link
Member

@Legrandin, see #172 to follow progress :)

So far, it seems that Azure Pipelines and AppVeyor do not support Python 3.8 on Windows, yet.

@joerick
Copy link
Contributor

joerick commented Nov 4, 2019

Fixed in #180. Release should be within the next couple weeks...!

@joerick joerick closed this as completed Nov 4, 2019
@MuellerSeb
Copy link
Contributor

Fixed in #180. Release should be within the next couple weeks...!

Are there any news on when to release it?

@YannickJadoul
Copy link
Member

YannickJadoul commented Nov 6, 2019

@MuellerSeb In the meanwhile, pip install git+https://github.com/joerick/cibuildwheel.git should work, though?

@MuellerSeb
Copy link
Contributor

@MuellerSeb In the meanwhile, pip install git+https://github.com/joerick/cibuildwheel.git should work, though?

Since I want to use it in CI, I'll wait for the next official release, to stick to one version.

@joerick
Copy link
Contributor

joerick commented Nov 7, 2019

I want to be sure that #175 isn't a problem and merge #169 before release... so I can't give an exact date, but within a couple weeks :)

@MuellerSeb
Copy link
Contributor

I'm cool with that. Thanks for your great work!

@YannickJadoul
Copy link
Member

@joerick In principle, the docs don't need to be ready before release, right? Commits to README on the master will show up immediately on GitHub, and the readthedocs can build independently of a release?

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

No branches or pull requests

4 participants