Skip to main content

Recreate tox virtual environments when setup.cfg changes.

Project description

tox-recreate

Recreate tox virtual environments when setup.cfg changes.

tox-recreate causes tox to recreate its virtualenv's if your setup.cfg file has changed.

Normally tox will automatically trigger a recreation of the venv if the test deps in tox.ini have changed. But what about your package's requirements in the install_requires setting in setup.cfg? If those change tox won't automatically recreate the venv, you're expected to run tox --recreate yourself.

tox-recreate keeps track of the hash of your setup.cfg file and triggers tox to recreate your venvs if it changes.

Setting up Your tox-recreate Development Environment

First you'll need to install:

  • Git. On Ubuntu: sudo apt install git, on macOS: brew install git.
  • GNU Make. This is probably already installed, run make --version to check.
  • pyenv. Follow the instructions in pyenv's README to install it. The Homebrew method works best on macOS. The Basic GitHub Checkout method works best on Ubuntu. You don't need to set up pyenv's shell integration ("shims"), you can use pyenv without shims.

Then to set up your development environment:

git clone https://github.com/hypothesis/tox-recreate.git
cd tox-recreate
make help

Releasing a New Version of the Project

  1. First, to get PyPI publishing working you need to go to: https://github.com/organizations/hypothesis/settings/secrets/actions/PYPI_TOKEN and add tox-recreate to the PYPI_TOKEN secret's selected repositories.

  2. Now that the tox-recreate project has access to the PYPI_TOKEN secret you can release a new version by just creating a new GitHub release. Publishing a new GitHub release will automatically trigger a GitHub Actions workflow that will build the new version of your Python package and upload it to https://pypi.org/project/tox-recreate.

Changing the Project's Python Versions

To change what versions of Python the project uses:

  1. Change the Python versions in the cookiecutter.json file. For example:

    "python_versions": "3.10.4, 3.9.12",
    
  2. Re-run the cookiecutter template:

    make template
    
  3. Commit everything to git and send a pull request

Changing the Project's Python Dependencies

To change the production dependencies in the setup.cfg file:

  1. Change the dependencies in the .cookiecutter/includes/setuptools/install_requires file. If this file doesn't exist yet create it and add some dependencies to it. For example:

    pyramid
    sqlalchemy
    celery
    
  2. Re-run the cookiecutter template:

    make template
    
  3. Commit everything to git and send a pull request

To change the project's formatting, linting and test dependencies:

  1. Change the dependencies in the .cookiecutter/includes/tox/deps file. If this file doesn't exist yet create it and add some dependencies to it. Use tox's factor-conditional settings to limit which environment(s) each dependency is used in. For example:

    lint: flake8,
    format: autopep8,
    lint,tests: pytest-faker,
    
  2. Re-run the cookiecutter template:

    make template
    
  3. Commit everything to git and send a pull request

Testing Manually

To test it manually you can install your local development copy of tox-recreate into the local development environment of another tox-using project such as cookiecutter-pypackage-test:

  1. Install a local development copy of cookiecutter-pypackage-test in a temporary directory:

    git clone https://github.com/hypothesis/cookiecutter-pypackage-test.git /tmp/cookiecutter-pypackage-test
    
  2. Run cookiecutter-pypackage-test's make sure command to make sure that everything is working and to trigger tox to create its .tox/.tox venv:

    make --directory "/tmp/cookiecutter-pypackage-test" sure
    
  3. Uninstall the production copy of tox-recreate from cookiecutter-pypackage-test's .tox/.tox venv:

    /tmp/cookiecutter-pypackage-test/.tox/.tox/bin/pip uninstall tox-recreate
    
  4. Install your local development copy of tox-recreate into cookiecutter-pypackage-test's .tox/.tox venv:

    /tmp/cookiecutter-pypackage-test/.tox/.tox/bin/pip install -e .
    
  5. Now cookiecutter-pypackage-test commands will use your local development copy of tox-recreate:

    make --directory "/tmp/cookiecutter-pypackage-test" test
    

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

tox_recreate-0.0.3.tar.gz (15.9 kB view details)

Uploaded Source

Built Distribution

tox_recreate-0.0.3-py3-none-any.whl (5.2 kB view details)

Uploaded Python 3

File details

Details for the file tox_recreate-0.0.3.tar.gz.

File metadata

  • Download URL: tox_recreate-0.0.3.tar.gz
  • Upload date:
  • Size: 15.9 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/5.0.0 CPython/3.12.4

File hashes

Hashes for tox_recreate-0.0.3.tar.gz
Algorithm Hash digest
SHA256 1e2e927d1725ed69a9b98bb49dd91898d5284dae3dd9ae0ec71e4e2ef0ede910
MD5 58437baf4c787e6e2da6443002bc209e
BLAKE2b-256 a428bfc2fb7d494c09d93bf2729f7d4dd5cf4195487b7f5038c7605dbc12cda7

See more details on using hashes here.

File details

Details for the file tox_recreate-0.0.3-py3-none-any.whl.

File metadata

File hashes

Hashes for tox_recreate-0.0.3-py3-none-any.whl
Algorithm Hash digest
SHA256 398589183d0bac7a533d5afe7a531dfa490862f5b64edd30db868131805af36b
MD5 3fd4e0d61f1ad732a4501b7d074387d0
BLAKE2b-256 c0d306e8f69f04c3a507cca1acd07dceb43c86a2aceba37348e360f8bd22bfa7

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page