mirror of
https://github.com/Xevion/exercism.git
synced 2025-12-10 06:07:08 -06:00
111 lines
3.4 KiB
Markdown
111 lines
3.4 KiB
Markdown
# Tournament
|
|
|
|
Tally the results of a small football competition.
|
|
|
|
Based on an input file containing which team played against which and what the
|
|
outcome was, create a file with a table like this:
|
|
|
|
```text
|
|
Team | MP | W | D | L | P
|
|
Devastating Donkeys | 3 | 2 | 1 | 0 | 7
|
|
Allegoric Alaskans | 3 | 2 | 0 | 1 | 6
|
|
Blithering Badgers | 3 | 1 | 0 | 2 | 3
|
|
Courageous Californians | 3 | 0 | 1 | 2 | 1
|
|
```
|
|
|
|
What do those abbreviations mean?
|
|
|
|
- MP: Matches Played
|
|
- W: Matches Won
|
|
- D: Matches Drawn (Tied)
|
|
- L: Matches Lost
|
|
- P: Points
|
|
|
|
A win earns a team 3 points. A draw earns 1. A loss earns 0.
|
|
|
|
The outcome should be ordered by points, descending. In case of a tie, teams are ordered alphabetically.
|
|
|
|
###
|
|
|
|
Input
|
|
|
|
Your tallying program will receive input that looks like:
|
|
|
|
```text
|
|
Allegoric Alaskans;Blithering Badgers;win
|
|
Devastating Donkeys;Courageous Californians;draw
|
|
Devastating Donkeys;Allegoric Alaskans;win
|
|
Courageous Californians;Blithering Badgers;loss
|
|
Blithering Badgers;Devastating Donkeys;loss
|
|
Allegoric Alaskans;Courageous Californians;win
|
|
```
|
|
|
|
The result of the match refers to the first team listed. So this line
|
|
|
|
```text
|
|
Allegoric Alaskans;Blithering Badgers;win
|
|
```
|
|
|
|
Means that the Allegoric Alaskans beat the Blithering Badgers.
|
|
|
|
This line:
|
|
|
|
```text
|
|
Courageous Californians;Blithering Badgers;loss
|
|
```
|
|
|
|
Means that the Blithering Badgers beat the Courageous Californians.
|
|
|
|
And this line:
|
|
|
|
```text
|
|
Devastating Donkeys;Courageous Californians;draw
|
|
```
|
|
|
|
Means that the Devastating Donkeys and Courageous Californians tied.
|
|
|
|
## 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 tournament_test.py`
|
|
- Python 3.4+: `pytest tournament_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 tournament_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/tournament` 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.
|