Sha256: 5d930522032215c6329759d3a5170b0401ba411a3869f3923264ae3d5b627edc

Contents?: true

Size: 1.9 KB

Versions: 31

Compression:

Stored size: 1.9 KB

Contents

# Robot Name

Manage robot factory settings.

When robots come off the factory floor, they have no name.

The first time you boot them up, a random name is generated in the format
of two uppercase letters followed by three digits, such as RX837 or BC811.

Every once in a while we need to reset a robot to its factory settings,
which means that their name gets wiped. The next time you ask, it will
respond with a new random name.

The names must be random: they should not follow a predictable sequence.
Random names means a risk of collisions. Your solution must ensure that
every existing robot has a unique name.

## 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).

## Source

A debugging session with Paul Blackwell at gSchool. [http://gschool.it](http://gschool.it)

## 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/robot-name/README.md
trackler-2.2.1.104 tracks/python/exercises/robot-name/README.md
trackler-2.2.1.103 tracks/python/exercises/robot-name/README.md
trackler-2.2.1.102 tracks/python/exercises/robot-name/README.md
trackler-2.2.1.101 tracks/python/exercises/robot-name/README.md
trackler-2.2.1.100 tracks/python/exercises/robot-name/README.md
trackler-2.2.1.99 tracks/python/exercises/robot-name/README.md
trackler-2.2.1.98 tracks/python/exercises/robot-name/README.md
trackler-2.2.1.97 tracks/python/exercises/robot-name/README.md
trackler-2.2.1.96 tracks/python/exercises/robot-name/README.md
trackler-2.2.1.95 tracks/python/exercises/robot-name/README.md
trackler-2.2.1.94 tracks/python/exercises/robot-name/README.md
trackler-2.2.1.93 tracks/python/exercises/robot-name/README.md
trackler-2.2.1.92 tracks/python/exercises/robot-name/README.md
trackler-2.2.1.91 tracks/python/exercises/robot-name/README.md
trackler-2.2.1.90 tracks/python/exercises/robot-name/README.md
trackler-2.2.1.89 tracks/python/exercises/robot-name/README.md
trackler-2.2.1.88 tracks/python/exercises/robot-name/README.md
trackler-2.2.1.87 tracks/python/exercises/robot-name/README.md
trackler-2.2.1.86 tracks/python/exercises/robot-name/README.md