-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Support packaging as .whl files #1172
Conversation
@@ -32,7 +32,7 @@ def build_package(path_to_package, dist_dir): | |||
print_heading('Building {}'.format(path_to_package)) | |||
path_to_setup = os.path.join(path_to_package, 'setup.py') | |||
set_version(path_to_setup) | |||
cmd_success = exec_command('python setup.py sdist -d {}'.format(dist_dir), cwd=path_to_package) | |||
cmd_success = exec_command('python setup.py sdist bdist_wheel -d {}'.format(dist_dir), cwd=path_to_package) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a question, is it worthwhile to produce both packages?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes they recommend creating both and uploading both.
LGTM |
9df5c5a
to
f6da85d
Compare
I've verifying the change a bit more before merging. |
4eafe70
to
f378046
Compare
- Update package-verify and nightly-build to use bdist_wheel also
f378046
to
81fa6f2
Compare
When publishing on PyPI, we should publish both .tar.gz and .whl files.
Add setup.cfg files