python-wheel

I'd like to distribute a whole virtualenv, or a bunch of Python wheels of exact versions with their runtime dependencies, for example: pycurl pycurl.so libcurl.so libz.so libssl.so libcrypto.so libgssapi_krb5.so libkrb5.so libresolv.so I suppose I could rely on the system to have libssl.so installed, but surely not libcurl.so of the correct version and probably not Kerberos. What is the easiest way to package one library in a wheel with all the run-time dependency? Or is that a fool's errand and I should package entire virtualenv? How to do that reliably? P.S. compiling on the fly is not an

I have Python wheel file: psutil-5.4.5-cp26-none-linux_x86_64.whl How can I list the dependencies this wheel has? As previously mentioned, .whl files are just ZIP archives. You can just open them and poke around in the METADATA file. There is a tool, however, that can make this manual process a bit easier. You can use pkginfo , which can be installed by just using pip. $ pip install pkginfo $ pkginfo -f 'requires_dist' psutil-5.4.5-cp27-none-win32.whl requires_dist: ["enum34; extra == 'enum'"] I just tried to unzip (not gunzip) a wheel package I had lying around. The packagename-version.dist

Suppose I have a native shared library (.dll or .so), built independently of any Python mechanism, and a Python module using ctypes to interface to the library. Is there a way that I can build those into a .whl package? If so, how? Assuming this is possible, I think I'd need the wheel package installed and to use python setup.py bdist_wheel but what would my setup.py need to look like? I'd like to do this so I can upload Wheels for various platforms into a private package index and be able to pip install the appropriate one for the platform I'm on. Eric Smith Edit : Updated for newer versions

PEP 427 describes the move to .whl files from .egg for Python packaging. In the comparisons section of the PEP, there is point 6: Wheel is a reference to the other Python. I don't understand this point, what are they trying to say? .egg is a reference to the snake variety of python, .whl is a reference to Monty Python's "wheel of cheese" 来源： https://stackoverflow.com/questions/21113163/wheel-is-a-reference-to-the-other-python

This is a truly popular question here at SO, but none of the many answers I have looked at, clearly explain what this error really mean, and why it occurs. One source of confusion, is that when (for example) you do pip install pycparser , you first get the error: Failed building wheel for pycparser which is then followed by the message that the package was: Successfully installed pycparser-2.19 . # pip3 install pycparser Collecting pycparser Using cached https://files.pythonhosted.org/packages/68/9e/49196946aee219aead1290e00d1e7fdeab8567783e83e1b9ab5585e6206a/pycparser-2.19.tar.gz Building

Is it possible to install a Python wheel without using pip ? I always have issues with installing with pip , so I usually install libraries manually by copying and pasting. I'm wondering if there is a way to do wheel files in a similar manner. It is. Actually .whl files are just zip archives, so you can just extract their content and play with libraries path variable to make it work. Yet it is really bad practice. I'm assuming you have internet access , but you don't have a working pip installation . Download the pip wheel: wget https://files.pythonhosted.org/packages/0f/74

I want to create package for python that embeds and uses an external library ( .so ) on Linux using the cffi module. Is there standard way to include .so file into python package? The package will be used only internally and won't be published to pypi. I think Wheel packages are the best option - they would create platform specific package with all files ready to be copied so there will be no need to build anything on target environments. You can use auditwheel to inject the external libraries into the wheel: auditwheel repair: copies these external shared libraries into the wheel itself, and