setuptools_hg
setuptools_hg is a plugin for setuptools/distribute to enable it to find files under the Mercurial version control system.
It uses the Mercurial Python library by default and falls back to use the command line programm hg(1). That’s especially useful inside virtualenvs that don’t have access to the system wide installed Mercurial lib (e.g. when created with --no-site-packages).
Usage
Here’s an example of a setup.py that uses setuptools_hg:
from setuptools import setup, find_packages
setup(
name="HelloWorld",
version="0.1",
packages=find_packages(),
setup_requires=["setuptools_hg"],
)
If you run this setup.py setuptools will automatically download setuptools_hg to the directory where the setup.py is located at (and won’t install it anywhere else) to get all package data files from the Mercurial repository.
Options
Set the HG_SETUPTOOLS_FORCE_CMD environment variable before running setup.py if you want to enforce the use of the hg command. “””
CHANGES
0.4
fix a bug if the current distribution is not versionned with mercurial. [kiorky]
fix https://bitbucket.org/jezdez/setuptools_hg/issue/5/using-hg-command-line-with-py3-does-not [kiorky]
Metadata
Release files for setuptools_hg 0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| setuptools_hg-0.4.tar.gz | 11.1 kB | Without provenance | Details for setuptools_hg-0.4.tar.gz |
Release files / setuptools_hg-0.4.tar.gz
| Download URL | setuptools_hg-0.4.tar.gz |
|---|---|
| Size | 11.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a41c3f9e7e503d760068aefd707ad82297a8d734078f478013b50be0dbe28f4e
|
|
BLAKE2b-256 checksum How to use checksums |
6701d1736a881ea8af3c9a9f18aa011a2fdd044789a86a9be4948697b42154e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for setuptools_hg 0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.