Sha256: 2433e4e7edf25782e2a422b2f75c551aeac2f3e2e70114f4a8171f9a4d220df9

Contents?: true

Size: 1.98 KB

Versions: 28

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.4+: `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

28 entries across 28 versions & 1 rubygems

Version Path
trackler-2.2.1.180 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.179 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.178 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.177 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.176 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.175 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.174 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.173 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.172 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.171 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.170 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.169 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.167 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.166 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.165 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.164 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.163 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.162 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.161 tracks/python/config/exercise_readme.go.tmpl
trackler-2.2.1.160 tracks/python/config/exercise_readme.go.tmpl