On 29 October 2014 23:02, Ethan Furman <et...@stoneleaf.us> wrote: > On 10/29/2014 03:46 PM, Paul Moore wrote: >> >> On 29 October 2014 22:19, Ethan Furman <et...@stoneleaf.us> wrote: >>> >>> >>> - where one should be at when one starts the compile process >> >> >> I don't understand this. It's just "pip wheel foo" to build a wheel >> for foo (which will be downloaded), or "pip wheel ." or "python >> setup.py bdist_wheel" as you prefer for a local package. > > > Hmmm... That looks like it's for installing/compiling somebody else's > package. Is that last command sufficient to prepare one's own wheel for > uploading to PyPI, or there something else to do?
Oh, I see what you're thinking. I explicitly *don't* want to get into general packaging issues - they are covered elsewhere. The point here is that if you have the right compiler set up, you can read any generic packaging instructions and it doesn't matter whether there's C code involved. That's it. But yes, "python setup.py bdist_wheel" is how you build a wheel for upload. That's true whether your project includes C extensions or not. I'm also not expecting to explain to people how to build any dependencies (for example, PyYAML depends on the C compiler being able to find libyaml). That *is* harder on Windows than on Linux, because there's no "system location" equivalent to /usr/local/include and /usr/local/lib. But again, I consider this to be outside the scope of the document, because it's specific to the particular project you're building. Paul _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
