69 lines
2.5 KiB
Markdown
69 lines
2.5 KiB
Markdown
# Grains
|
|
|
|
Welcome to Grains on Exercism's Python Track.
|
|
If you need help running the tests or submitting your code, check out `HELP.md`.
|
|
|
|
## Instructions
|
|
|
|
Calculate the number of grains of wheat on a chessboard given that the number
|
|
on each square doubles.
|
|
|
|
There once was a wise servant who saved the life of a prince. The king
|
|
promised to pay whatever the servant could dream up. Knowing that the
|
|
king loved chess, the servant told the king he would like to have grains
|
|
of wheat. One grain on the first square of a chess board, with the number
|
|
of grains doubling on each successive square.
|
|
|
|
There are 64 squares on a chessboard (where square 1 has one grain, square 2 has two grains, and so on).
|
|
|
|
Write code that shows:
|
|
- how many grains were on a given square, and
|
|
- the total number of grains on the chessboard
|
|
|
|
## For bonus points
|
|
|
|
Did you get the tests passing and the code clean? If you want to, these
|
|
are some additional things you could try:
|
|
|
|
- Optimize for speed.
|
|
- Optimize for readability.
|
|
|
|
Then please share your thoughts in a comment on the submission. Did this
|
|
experiment make the code better? Worse? Did you learn anything from it?
|
|
|
|
## Exception messages
|
|
|
|
Sometimes it is necessary to [raise an exception](https://docs.python.org/3/tutorial/errors.html#raising-exceptions). When you do this, you should always 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. For situations where you know that the error source will be a certain type, you can choose to raise one of the [built in error types](https://docs.python.org/3/library/exceptions.html#base-classes), but should still include a meaningful message.
|
|
|
|
This particular exercise requires that you use the [raise statement](https://docs.python.org/3/reference/simple_stmts.html#the-raise-statement) to "throw" a `ValueError` when the square input is out of range. The tests will only pass if you both `raise` the `exception` and include a message with it.
|
|
|
|
To raise a `ValueError` with a message, write the message as an argument to the `exception` type:
|
|
|
|
```python
|
|
# when the square value is not in the acceptable range
|
|
raise ValueError("square must be between 1 and 64")
|
|
```
|
|
|
|
## Source
|
|
|
|
### Contributed to by
|
|
|
|
- @behrtam
|
|
- @BethanyG
|
|
- @cmccandless
|
|
- @denislooby
|
|
- @Dog
|
|
- @kytrinyx
|
|
- @lowks
|
|
- @MojitoMonday
|
|
- @N-Parsons
|
|
- @pheanex
|
|
- @sdublish
|
|
- @sjakobi
|
|
- @smalley
|
|
- @tqa236
|
|
- @yawpitch
|
|
|
|
### Based on
|
|
|
|
JavaRanch Cattle Drive, exercise 6 - http://www.javaranch.com/grains.jsp |