Skip to content

Latest commit

 

History

History
137 lines (103 loc) · 4.54 KB

CONTRIBUTING.md

File metadata and controls

137 lines (103 loc) · 4.54 KB
Raw

Contributing to JupyterHub

Welcome! As a Jupyter project, you can follow the Jupyter contributor guide.

Make sure to also follow Project Jupyter's Code of Conduct for a friendly and welcoming collaborative environment.

Setting up a development environment

JupyterHub requires Python >= 3.5 and nodejs.

As a Python project, a development install of JupyterHub follows standard practices for the basics (steps 1-2).

  1. clone the repo

    git clone https://github.com/jupyterhub/jupyterhub

  2. do a development install with pip

    cd jupyterhub
python3 -m pip install --editable .

  3. install the development requirements, which include things like testing tools

    python3 -m pip install -r dev-requirements.txt

  4. install configurable-http-proxy with npm:

    npm install -g configurable-http-proxy

  5. set up pre-commit hooks for automatic code formatting, etc.

    pre-commit install

    You can also invoke the pre-commit hook manually at any time with

    pre-commit run

Contributing

JupyterHub has adopted automatic code formatting so you shouldn't need to worry too much about your code style. As long as your code is valid, the pre-commit hook should take care of how it should look. You can invoke the pre-commit hook by hand at any time with:

pre-commit run

which should run any autoformatting on your code and tell you about any errors it couldn't fix automatically. You may also install black integration into your text editor to format code automatically.

If you have already committed files before setting up the pre-commit hook with pre-commit install, you can fix everything up using pre-commit run --all-files. You need to make the fixing commit yourself after that.

Testing

It's a good idea to write tests to exercise any new features, or that trigger any bugs that you have fixed to catch regressions.

You can run the tests with:

pytest -v

in the repo directory. If you want to just run certain tests, check out the pytest docs for how pytest can be called. For instance, to test only spawner-related things in the REST API:

pytest -v -k spawn jupyterhub/tests/test_api.py

The tests live in jupyterhub/tests and are organized roughly into:

  1. test_api.py tests the REST API
  2. test_pages.py tests loading the HTML pages

and other collections of tests for different components. When writing a new test, there should usually be a test of similar functionality already written and related tests should be added nearby.

The fixtures live in jupyterhub/tests/conftest.py. There are fixtures that can be used for JupyterHub components, such as:

  • app: an instance of JupyterHub with mocked parts
  • auth_state_enabled: enables persisting auth_state (like authentication tokens)
  • db: a sqlite in-memory DB session
  • io_loop: a Tornado event loop
  • event_loop: a new asyncio event loop
  • user: creates a new temporary user
  • admin_user: creates a new temporary admin user
  • single user servers
    • cleanup_after: allows cleanup of single user servers between tests
  • mocked service
    • MockServiceSpawner: a spawner that mocks services for testing with a short poll interval
    • mockservice: mocked service with no external service url
    • mockservice_url: mocked service with a url to test external services

And fixtures to add functionality or spawning behavior:

  • admin_access: grants admin access
  • no_patience: sets slow-spawning timeouts to zero
  • slow_spawn: enables the SlowSpawner (a spawner that takes a few seconds to start)
  • never_spawn: enables the NeverSpawner (a spawner that will never start)
  • bad_spawn: enables the BadSpawner (a spawner that fails immediately)
  • slow_bad_spawn: enables the SlowBadSpawner (a spawner that fails after a short delay)

To read more about fixtures check out the pytest docs for how to use the existing fixtures, and how to create new ones.

When in doubt, feel free to ask.