Sha256: ad7e0ff5c7b8616ad2d883fdb82290a470dd3bd49dadcc9d0c92d79dfff0da41

Contents?: true

Size: 1.96 KB

Versions: 31

Compression:

Stored size: 1.96 KB

Contents

# Error Handling

Implement various kinds of error handling and resource management.

An important point of programming is how to handle errors and close
resources even if errors occur.

This exercise requires you to handle various errors. Because error handling
is rather programming language specific you'll have to refer to the tests
for your track to see what's exactly required.

## Hints

For the `filelike_objects_are_closed_on_exception` function, the `filelike_object`
will be an instance of a custom `FileLike` class defined in the test suite. This
class implements the following methods:
- `open` and `close`, for explicit opening and closing.
- `__enter__` and `__exit__`, for implicit opening and closing.
- `do_something`, which may or may not throw an `Exception`.


## 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 shold write:

```python
raise Exception("Meaningful message indicating the source of the error")
```


## Submitting Exercises

Note that, when trying to submit an exercise, make sure the solution is in the `exercism/python/<exerciseName>` directory.

For example, if you're submitting `bob.py` for the Bob exercise, the submit command would be something like `exercism submit <path_to_exercism_dir>/python/bob/bob.py`.

For more detailed information about running tests, code style and linting,
please see the [help page](http://exercism.io/languages/python).


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

Version data entries

31 entries across 31 versions & 1 rubygems

Version Path
trackler-2.2.1.105 tracks/python/exercises/error-handling/README.md
trackler-2.2.1.104 tracks/python/exercises/error-handling/README.md
trackler-2.2.1.103 tracks/python/exercises/error-handling/README.md
trackler-2.2.1.102 tracks/python/exercises/error-handling/README.md
trackler-2.2.1.101 tracks/python/exercises/error-handling/README.md
trackler-2.2.1.100 tracks/python/exercises/error-handling/README.md
trackler-2.2.1.99 tracks/python/exercises/error-handling/README.md
trackler-2.2.1.98 tracks/python/exercises/error-handling/README.md
trackler-2.2.1.97 tracks/python/exercises/error-handling/README.md
trackler-2.2.1.96 tracks/python/exercises/error-handling/README.md
trackler-2.2.1.95 tracks/python/exercises/error-handling/README.md
trackler-2.2.1.94 tracks/python/exercises/error-handling/README.md
trackler-2.2.1.93 tracks/python/exercises/error-handling/README.md
trackler-2.2.1.92 tracks/python/exercises/error-handling/README.md
trackler-2.2.1.91 tracks/python/exercises/error-handling/README.md
trackler-2.2.1.90 tracks/python/exercises/error-handling/README.md
trackler-2.2.1.89 tracks/python/exercises/error-handling/README.md
trackler-2.2.1.88 tracks/python/exercises/error-handling/README.md
trackler-2.2.1.87 tracks/python/exercises/error-handling/README.md
trackler-2.2.1.86 tracks/python/exercises/error-handling/README.md