Sha256: 2fe433357616ee97459451084f2336195f92ff0691ae95dec5afdaca1a20b2c8

Contents?: true

Size: 1.98 KB

Versions: 40

Compression:

Stored size: 1.98 KB

Contents

# {{ .Spec.Name }}

{{ .Spec.Description -}}
{{- with .Hints }}
{{ . }}
{{ end }}
## 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 {{ .Spec.SnakeCaseName }}_test.py`
- Python 3.3+: `pytest {{ .Spec.SnakeCaseName }}_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 {{ .Spec.SnakeCaseName }}_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/{{ .Spec.Slug }}` 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 the [help page](http://exercism.io/languages/python).
{{ with .Spec.Credits }}
## Source

{{ . }}
{{ end }}
## Submitting Incomplete Solutions

It's possible to submit an incomplete solution so you can see how others have completed the exercise.

Version data entries

40 entries across 40 versions & 1 rubygems

Version Path
trackler-2.2.1.151 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.150 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.149 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.148 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.147 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.146 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.145 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.144 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.143 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.142 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.141 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.140 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.139 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.138 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.137 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.136 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.135 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.134 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.133 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.132 tracks/python/config/exercise_readme.go.tmpl