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

Improve documentation #33

Merged
merged 8 commits into from
Feb 25, 2014
Merged

Improve documentation #33

merged 8 commits into from
Feb 25, 2014

Conversation

LilyFoote
Copy link
Collaborator

Add Advantages of wheels and Other Resources sections. Split information about creating wheels into Pure Python and C extensions subsections. Add link to pull-requests on github to encourage more active participation.

I have tried to cover the suggestions made in issue #29 by @zzzeek. I have also included suggestions from #22 and #16.

<p><strong>Warning: </strong>If your project has optional C extensions, it is recommended not to publish a universal wheel, because pip will prefer the wheel over a source installation.</p>
<h3>C extensions</h3>
<p>PyPI currently only allows uploading platform-specific wheels for Windows and Mac&nbsp;OS&nbsp;X. It is still useful to create wheels for these platforms, as it avoids the need for your users to compile the package when installing.</p>
<p>You will need to have access to the platform you are building for.</p>
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would like to expand on this with more detail.

<p>You can also <a href="https://github.com/meshy/pythonwheels/pulls/">submit a pull-request</a>.</p>
<h2>Other resources</h2>
<p>The <a href="https://python-packaging-user-guide.readthedocs.org/en/latest/">Python Packaging User Guide</a> is aiming to be the authoritative guide for python packaging and installation. It is still a work in progress, so some information may be missing.</p>
<p><a href="https://pypip.in/wheel.html">PyPI Pins</a> has a pin you can use to display your wheel compatibility: <img src="https://pypip.in/wheel/blackhole/badge.png" alt="Wheel Status"></p>
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From #27.

@ncoghlan
Copy link

Looks good to me - thanks for putting this together!

@meshy
Copy link
Owner

meshy commented Feb 24, 2014

This all looks great, @Ian-Foote. Thank-you very much for putting so much effort into this.

If it's ok, I would like to ask you to make one change before I merge. Would it be possible to include the link to the "authoritative resource" even more prominently? Specifically, if it could be moved to the bottom of the "What is this list" section, that would be amazing. I'm thinking that the copy should make it absolutely clear that pythonwheels.com is not the official website for python wheels by saying something like:

This is not the official website for wheels, just a nice visual way to measure adoption. To see the authoritative guide, see the Python Packaging User Guide.

Thank-you! Charlie.

@LilyFoote
Copy link
Collaborator Author

@meshy I'm happy to do that if the Python Packaging User Guide is considered sufficiently ready. @qwcode Thoughts?

@ncoghlan
Copy link

Yeah, PPUG is already the best available resource - the CPython docs link to it from the disclaimers at the top of the distribution, installation and extension building guides.

It also has a a nice new URL at http://packaging.python.org (although the old URL still works)

@meshy
Copy link
Owner

meshy commented Feb 25, 2014

Great stuff! Thanks!

meshy added a commit that referenced this pull request Feb 25, 2014
@meshy meshy merged commit 72ca598 into meshy:master Feb 25, 2014
@LilyFoote LilyFoote deleted the wheel_docs branch February 25, 2014 08:44
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.

5 participants