-
-
Notifications
You must be signed in to change notification settings - Fork 182
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
release py3 wheels #58
Comments
@jettify bump |
I will take a look, as far as i can tell we need to add |
You can also go back and upload wheels to old releases
On 22 Feb 2017 15:08, "Nikolay Novik" <notifications@github.com> wrote:
I will take a look, as far as i can tell we need to add bdist_wheel to our
deploy config.
https://docs.travis-ci.com/user/deployment/pypi/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#58 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAZQTDdRa6vaWGB6kif4kMipagB-V0Kwks5rfE9wgaJpZM4KCuZJ>
.
|
Configure bdist_wheel in travis fixes #58
@graingert could you please elaborate why we should do upload of wheel for old releases? Since package is pure python, i do not see huge advantage of wheel, but may be i miss something |
It's just something you can do. Makes stuff go faster for people on older versions |
ya, I'm not seeing a benefit of using wheels for this module. Wheels are typically for modules that need to compile source files so you don't need to install the development packages on the destination box. |
Can you at least ship a new release? |
We do not have any significant changes for new release... I can upload wheel for current version manually, each next release will have those automatically |
Either is fine |
Neato thanks |
No description provided.
The text was updated successfully, but these errors were encountered: