CLI for the Hypothesis development environment
Project description
hdev
The CLI for the Hypothesis development environment.
Installation & Upgrading
The instructions below use pipx to
install hdev
. pipx
will install hdev
in its own isolated virtualenv at
~/.local/pipx/venvs/hdev
and add it to your PATH
, without sudo
. You can
easily uninstall it again with pipx uninstall hdev
. It won't touch your
system Python environment at all.
Installing on macOS
Install Homebrew and then run:
brew install pipx
pipx ensurepath
pipx install hdev
Installing on Linux
python3 -m pip install --user pipx
python3 -m pipx ensurepath
pipx install hdev
Upgrading (on either macOS or Linux)
To upgrade hdev to the latest version:
pipx upgrade hdev
Usage
usage: hdev [-h] [--project-dir PROJECT_DIR] [--debug] {alembic,clean,deps,python_version,requirements,run,template} ...
positional arguments:
{alembic,clean,deps,python_version,requirements,run,template}
alembic Run alembic commands to create and execute DB migrations.
clean Clean a project directory
deps Get dependency information
python_version Dump the versions of Python in various formats
requirements Compiles .txt requirements file based on the existing .in files using pip-tools
run Run a custom command defined in the pyproject.toml file
template Update the local project template
optional arguments:
-h, --help show this help message and exit
--project-dir PROJECT_DIR
Path of the project's root. Defaults to .
--debug Enable debugging info
Configuration
hdev
is configured within your project's pyproject.toml
file with the following options:
[tool.hdev.clean]
# File and directory patterns relative to the root to remove.
# These support shell expansions and patterns
files=[]
dirs=[]
# File and directory names which will be removed anywhere they
# are found. These support shell expansions and patterns
file_names=[]
dir_names=[]
[tool.hdev.run]
# Add a custom command runnable with `hdev run custom`
mycommand.command = "echo hello"
mycommand.help = "Say hello!"
You can choose to not use any configuration, in that case hdev
provides
sensible default for most Hypothesis projects.
Hacking
Installing hdev in a development environment
You will need
-
- Follow the instructions in the pyenv README to install it
- On macOS: the Homebrew method works best on macOS
- On Ubuntu: follow the Basic GitHub Checkout method
-
Graphviz [optional]
- This is only needed for the
hdev deps --graph
command - On macOS:
brew install graphviz
- On Ubuntu:
sudo apt install graphviz
- This is only needed for the
Clone the git repo
git clone https://github.com/hypothesis/hdev.git
This will download the code into a hdev
directory
in your current working directory. You need to be in the
hdev
directory for the rest of the installation
process:
cd hdev
Run the tests
make test
That's it! You’ve finished setting up your hdev
development environment. Run make help
to see all the commands that're
available for linting, code formatting, packaging, etc.
Updating the Cookiecutter scaffolding
This project was created from the https://github.com/hypothesis/h-cookiecutter-pypackage/ template. If h-cookiecutter-pypackage itself has changed since this project was created, and you want to update this project with the latest changes, you can "replay" the cookiecutter over this project. Run:
make template
This will change the files in your working tree, applying the latest updates from the h-cookiecutter-pypackage template. Inspect and test the changes, do any fixups that are needed, and then commit them to git and send a pull request.
If you want make template
to skip certain files, never changing them, add
these files to "options.disable_replay"
in
.cookiecutter.json
and commit that to git.
If you want make template
to update a file that's listed in disable_replay
simply delete that file and then run make template
, it'll recreate the file
for you.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.