mirror of
https://github.com/Xevion/exercism.git
synced 2025-12-10 06:07:08 -06:00
64 lines
2.6 KiB
Markdown
64 lines
2.6 KiB
Markdown
# Sublist
|
|
|
|
Given two lists determine if the first list is contained within the second
|
|
list, if the second list is contained within the first list, if both lists are
|
|
contained within each other or if none of these are true.
|
|
|
|
Specifically, a list A is a sublist of list B if by dropping 0 or more elements
|
|
from the front of B and 0 or more elements from the back of B you get a list
|
|
that's completely equal to A.
|
|
|
|
Examples:
|
|
|
|
* A = [1, 2, 3], B = [1, 2, 3, 4, 5], A is a sublist of B
|
|
* A = [3, 4, 5], B = [1, 2, 3, 4, 5], A is a sublist of B
|
|
* A = [3, 4], B = [1, 2, 3, 4, 5], A is a sublist of B
|
|
* A = [1, 2, 3], B = [1, 2, 3], A is equal to B
|
|
* A = [1, 2, 3, 4, 5], B = [2, 3, 4], A is a superlist of B
|
|
* A = [1, 2, 4], B = [1, 2, 3, 4, 5], A is not a superlist of, sublist of or equal to B
|
|
|
|
## Exception messages
|
|
|
|
Sometimes it is necessary to raise an exception. When you do this, you should include a meaningful error message to
|
|
indicate what the source of the error is. This makes your code more readable and helps significantly with debugging. Not
|
|
every exercise will require you to raise an exception, but for those that do, the tests will only pass if you include
|
|
a message.
|
|
|
|
To raise a message with an exception, just write it as an argument to the exception type. For example, instead of
|
|
`raise Exception`, you should write:
|
|
|
|
```python
|
|
raise Exception("Meaningful message indicating the source of the error")
|
|
```
|
|
|
|
## Running the tests
|
|
|
|
To run the tests, run the appropriate command below ([why they are different](https://github.com/pytest-dev/pytest/issues/1629#issue-161422224)):
|
|
|
|
- Python 2.7: `py.test sublist_test.py`
|
|
- Python 3.4+: `pytest sublist_test.py`
|
|
|
|
Alternatively, you can tell Python to run the pytest module (allowing the same command to be used regardless of Python version):
|
|
`python -m pytest sublist_test.py`
|
|
|
|
### Common `pytest` options
|
|
|
|
- `-v` : enable verbose output
|
|
- `-x` : stop running tests on first failure
|
|
- `--ff` : run failures from previous test before running other test cases
|
|
|
|
For other options, see `python -m pytest -h`
|
|
|
|
## Submitting Exercises
|
|
|
|
Note that, when trying to submit an exercise, make sure the solution is in the `$EXERCISM_WORKSPACE/python/sublist` directory.
|
|
|
|
You can find your Exercism workspace by running `exercism debug` and looking for the line that starts with `Workspace`.
|
|
|
|
For more detailed information about running tests, code style and linting,
|
|
please see [Running the Tests](http://exercism.io/tracks/python/tests).
|
|
|
|
## Submitting Incomplete Solutions
|
|
|
|
It's possible to submit an incomplete solution so you can see how others have completed the exercise.
|