69

In order to stage python project within our corporation I need to make an installable distribution.

This should include:

  • An egg or whl for my project
  • An egg or whl for every dependency of the project
  • (optionally) produce a requirements.txt file listing all the installable components for this release

Is there an easy plug in, (e.g. an alternative to bdist_wheel) that will not only compile one wheel but also that project's components?

Obviously I can script this, but I was hoping that there might be a short-cut that builds the package + dependencies in fewer steps.

This needs to work on Python 2.7 on Windows + Linux.

Martijn Pieters
  • 889,049
  • 245
  • 3,507
  • 2,997
Salim Fadhley
  • 4,511
  • 7
  • 33
  • 59

3 Answers3

79

You will need to create a setup.py file for your package. Make sure you have the latest setuptools and pip installed. Then run the following:

python setup.py bdist_wheel

This will create a wheel file for your package. This assumes you don't have C/C++ headers, DLLs, etc. If you do, then you'll probably have a lot more work to do.

To get dependencies, you will want to create a requirements.txt file and run the following:

pip wheel -r requirements.txt

If your package isn't on PyPI, then you'll have to manually copy your package's wheel file into the wheel folder that this command creates. For more information see the following excellent article:

Mike Driscoll
  • 31,394
  • 6
  • 39
  • 83
56

With the latest pip and wheel, you can simply run

pip wheel .

within your project folder, even if your application isn't on PyPi. All wheels will be stored in the current directory (.).

To change the output directory (to for example, ./wheels), you may use the -w / --wheel-dir option:

pip wheel . -w wheels

All the options available are listed at the pip documentation.

np8
  • 14,736
  • 8
  • 50
  • 67
jtpereyda
  • 5,465
  • 8
  • 46
  • 67
  • 2
    It search my local packages on pypi so it fails. Instead, I run `python setup.py bdist_wheel` first, then run `pip wheel -r requirements.txt` for pypi packages. – guneysus Oct 04 '16 at 11:44
  • 1
    I just tried it and it writes the wheel files to your working directory by default (not ./wheelhouse). Also, any idea how to specify the name of the output file? I'm not seeing anything in the docs. – weberc2 Jul 16 '19 at 19:58
  • This gives me a million wheels. How do I get one big wheel file? – rjurney Apr 28 '21 at 17:37
2

With poetry you can define your dependencies and metadata about your project in a file in the root of your project, called pyproject.toml:

[tool.poetry]
name = "my-project"
version = "0.1.0"
description = "some longer description"
authors = ["Some Author <some@author.io>"]

[tool.poetry.dependencies]
python = "*"

[tool.poetry.dev-dependencies]
pytest = "^3.4"

To build your project as a wheel, execute poetry build

$ poetry build

Building my-project (0.1.0)
- Building sdist
- Built my-project-0.1.0.tar.gz

- Building wheel
- Built my-project-0.1.0-py3-none-any.whl

a dist/ folder is created with a wheel for your project.

Vincent Claes
  • 1,949
  • 2
  • 22
  • 43
  • Something's fishy here... a 6 year old question has a 2 month old answer as its accepted answer? – Klaas van Schelven Apr 14 '21 at 18:42
  • the OP can switch the correct answer https://meta.stackexchange.com/a/120569/874594 – Vincent Claes Apr 15 '21 at 13:38
  • this will still not add all the specified dependencies in the created wheel file. the individual dependencies will be downloaded when its installed. – rh979 May 06 '21 at 05:09
  • @rh979 a wheel is not meant to have all dependencies. Subsequently you could do `pip install path/to/wheel.whl --target /path/to/some/folder` and zip the contents of the 'folder' to have all your dependencies in the zip archive and ship that to the environment where you want to run your code. – Vincent Claes May 06 '21 at 07:27