If you’re interested in getting involved in the development of Modin, but aren’t sure
where start, take a look at the issues tagged Good first issue or Documentation.
These are issues that would be good for getting familiar with the codebase and better
understanding some of the more complex components of the architecture. There is
documentation here about the architecture that you will want to review in order to get
started.

We recommend doing development in a virtualenv, though this decision is ultimately
yours. You will want to run the following in order to install all of the required
dependencies for running the tests and formatting the code:

If you find yourself fixing a bug or adding a new feature, don’t forget to add a test to
the test suite to verify its correctness! More on testing and the layout of the tests
can be found in our testing documentation. We ask that you follow the existing
structure of the tests for ease of maintenance.

To run the entire test suite, run the following from the project root:

pytest modin/pandas/test

The test suite is very large, and may take a long time if you run every test. If you’ve
only modified a small amount of code, it may be sufficient to run a single test or some
subset of the test suite. In order to run a specific test run: