| Port details |
- py-check-wheel-contents Check your wheels have the right contents
- 0.6.2 devel
 =0      0.6.1Version of this port present on the latest quarterly branch. - Maintainer: sunpoet@FreeBSD.org
- Port Added: 2025-02-20 08:18:08
- Last Update: 2025-05-25 09:52:31
- Commit Hash: c3b665d
- Also Listed In: python
- License: MIT
- WWW:
- https://github.com/jwodder/check-wheel-contents
- Description:
- Getting the right files into your wheel is tricky, and sometimes we mess up and
publish a wheel containing __pycache__ directories or tests/. Do we have to
manually check the contents of every wheel we build before uploading it to PyPI?
How about letting this program check for you? Just run check-wheel-contents on
your wheel, and it'll fail and notify you if any of several common errors &
mistakes are detected. The errors are described below, along with common causes
and corresponding fixes.
  ¦  ¦  ¦  ¦ 
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - There is no configure plist information for this port.
- Dependency lines:
-
- ${PYTHON_PKGNAMEPREFIX}check-wheel-contents>0:devel/py-check-wheel-contents@${PY_FLAVOR}
- To install the port:
- cd /usr/ports/devel/py-check-wheel-contents/ && make install clean
- To add the package, run one of these commands:
- pkg install devel/py-check-wheel-contents
- pkg install py311-check-wheel-contents
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above.
NOTE: This is a Python port. Instead of py311-check-wheel-contents listed in the above command, you can pick from the names under the Packages section.- PKGNAME: py311-check-wheel-contents
- Package flavors (<flavor>: <package>)
- py311: py311-check-wheel-contents
- distinfo:
- TIMESTAMP = 1747715354
SHA256 (check_wheel_contents-0.6.2.tar.gz) = f4a01d2b5bb62a91781cf4b5c0f472fcb41a0790027a34de05ca69b552717d32
SIZE (check_wheel_contents-0.6.2.tar.gz) = 585951
Packages (timestamps in pop-ups are UTC):
- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Build dependencies:
-
- py311-hatchling>=0 : devel/py-hatchling@py311
- python3.11 : lang/python311
- py311-build>=0 : devel/py-build@py311
- py311-installer>=0 : devel/py-installer@py311
- Test dependencies:
-
- python3.11 : lang/python311
- Runtime dependencies:
-
- python3.11 : lang/python311
- There are no ports dependent upon this port
Configuration Options:- No options to configure
- Options name:
- devel_py-check-wheel-contents
- USES:
- python:3.10+
- FreshPorts was unable to extract/find any pkg message
- Master Sites:
|
Number of commits found: 2
| Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
| Commit | Credits | Log message |
|---|
0.6.2
25 May 2025 09:52:31
 |
Po-Chuan Hsieh (sunpoet) |
devel/py-check-wheel-contents: Update to 0.6.2
- Add GitHub to MASTER_SITES
Changes: https://github.com/jwodder/check-wheel-contents/releases |
0.6.1
20 Feb 2025 07:26:51
|
Po-Chuan Hsieh (sunpoet) |
devel/py-check-wheel-contents: Add py-check-wheel-contents 0.6.1
Getting the right files into your wheel is tricky, and sometimes we mess up and
publish a wheel containing __pycache__ directories or tests/. Do we have to
manually check the contents of every wheel we build before uploading it to PyPI?
How about letting this program check for you? Just run check-wheel-contents on
your wheel, and it'll fail and notify you if any of several common errors &
mistakes are detected. The errors are described below, along with common causes
and corresponding fixes. |
Number of commits found: 2
|
As an Amazon Associate I earn from qualifying purchases.