Skip to content

Commit ca75432

Browse files
authored
Merge pull request #196 from ikostan/main
Resistor Color
2 parents 4b526f1 + ef71d3f commit ca75432

File tree

6 files changed

+300
-0
lines changed

6 files changed

+300
-0
lines changed
Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
{
2+
"authors": [
3+
"gabriel376"
4+
],
5+
"contributors": [
6+
"cmccandless",
7+
"Dog",
8+
"tqa236",
9+
"yawpitch"
10+
],
11+
"files": {
12+
"solution": [
13+
"resistor_color.py"
14+
],
15+
"test": [
16+
"resistor_color_test.py"
17+
],
18+
"example": [
19+
".meta/example.py"
20+
]
21+
},
22+
"blurb": "Convert a resistor band's color to its numeric representation.",
23+
"source": "Maud de Vries, Erik Schierboom",
24+
"source_url": "https://github.com/exercism/problem-specifications/issues/1458"
25+
}
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
{"track":"python","exercise":"resistor-color","id":"ac537788be404478985a630c5bd4cf3f","url":"https://exercism.org/tracks/python/exercises/resistor-color","handle":"myFirstCode","is_requester":true,"auto_approve":false}

resistor-color/HELP.md

Lines changed: 130 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,130 @@
1+
# Help
2+
3+
## Running the tests
4+
5+
We use [pytest][pytest: Getting Started Guide] as our website test runner.
6+
You will need to install `pytest` on your development machine if you want to run tests for the Python track locally.
7+
You should also install the following `pytest` plugins:
8+
9+
- [pytest-cache][pytest-cache]
10+
- [pytest-subtests][pytest-subtests]
11+
12+
Extended information can be found in our website [Python testing guide][Python track tests page].
13+
14+
15+
### Running Tests
16+
17+
To run the included tests, navigate to the folder where the exercise is stored using `cd` in your terminal (_replace `{exercise-folder-location}` below with your path_).
18+
Test files usually end in `_test.py`, and are the same tests that run on the website when a solution is uploaded.
19+
20+
Linux/MacOS
21+
```bash
22+
$ cd {path/to/exercise-folder-location}
23+
```
24+
25+
Windows
26+
```powershell
27+
PS C:\Users\foobar> cd {path\to\exercise-folder-location}
28+
```
29+
30+
<br>
31+
32+
Next, run the `pytest` command in your terminal, replacing `{exercise_test.py}` with the name of the test file:
33+
34+
Linux/MacOS
35+
```bash
36+
$ python3 -m pytest -o markers=task {exercise_test.py}
37+
==================== 7 passed in 0.08s ====================
38+
```
39+
40+
Windows
41+
```powershell
42+
PS C:\Users\foobar> py -m pytest -o markers=task {exercise_test.py}
43+
==================== 7 passed in 0.08s ====================
44+
```
45+
46+
47+
### Common options
48+
- `-o` : override default `pytest.ini` (_you can use this to avoid marker warnings_)
49+
- `-v` : enable verbose output.
50+
- `-x` : stop running tests on first failure.
51+
- `--ff` : run failures from previous test before running other test cases.
52+
53+
For additional options, use `python3 -m pytest -h` or `py -m pytest -h`.
54+
55+
56+
### Fixing warnings
57+
58+
If you do not use `pytest -o markers=task` when invoking `pytest`, you might receive a `PytestUnknownMarkWarning` for tests that use our new syntax:
59+
60+
```bash
61+
PytestUnknownMarkWarning: Unknown pytest.mark.task - is this a typo? You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/stable/mark.html
62+
```
63+
64+
To avoid typing `pytest -o markers=task` for every test you run, you can use a `pytest.ini` configuration file.
65+
We have made one that can be downloaded from the top level of the Python track directory: [pytest.ini][pytest.ini].
66+
67+
You can also create your own `pytest.ini` file with the following content:
68+
69+
```ini
70+
[pytest]
71+
markers =
72+
task: A concept exercise task.
73+
```
74+
75+
Placing the `pytest.ini` file in the _root_ or _working_ directory for your Python track exercises will register the marks and stop the warnings.
76+
More information on pytest marks can be found in the `pytest` documentation on [marking test functions][pytest: marking test functions with attributes] and the `pytest` documentation on [working with custom markers][pytest: working with custom markers].
77+
78+
Information on customizing pytest configurations can be found in the `pytest` documentation on [configuration file formats][pytest: configuration file formats].
79+
80+
81+
### Extending your IDE or Code Editor
82+
83+
Many IDEs and code editors have built-in support for using `pytest` and other code quality tools.
84+
Some community-sourced options can be found on our [Python track tools page][Python track tools page].
85+
86+
[Pytest: Getting Started Guide]: https://docs.pytest.org/en/latest/getting-started.html
87+
[Python track tools page]: https://exercism.org/docs/tracks/python/tools
88+
[Python track tests page]: https://exercism.org/docs/tracks/python/tests
89+
[pytest-cache]:http://pythonhosted.org/pytest-cache/
90+
[pytest-subtests]:https://github.com/pytest-dev/pytest-subtests
91+
[pytest.ini]: https://github.com/exercism/python/blob/main/pytest.ini
92+
[pytest: configuration file formats]: https://docs.pytest.org/en/6.2.x/customize.html#configuration-file-formats
93+
[pytest: marking test functions with attributes]: https://docs.pytest.org/en/6.2.x/mark.html#raising-errors-on-unknown-marks
94+
[pytest: working with custom markers]: https://docs.pytest.org/en/6.2.x/example/markers.html#working-with-custom-markers
95+
96+
## Submitting your solution
97+
98+
You can submit your solution using the `exercism submit resistor_color.py` command.
99+
This command will upload your solution to the Exercism website and print the solution page's URL.
100+
101+
It's possible to submit an incomplete solution which allows you to:
102+
103+
- See how others have completed the exercise
104+
- Request help from a mentor
105+
106+
## Need to get help?
107+
108+
If you'd like help solving the exercise, check the following pages:
109+
110+
- The [Python track's documentation](https://exercism.org/docs/tracks/python)
111+
- The [Python track's programming category on the forum](https://forum.exercism.org/c/programming/python)
112+
- [Exercism's programming category on the forum](https://forum.exercism.org/c/programming/5)
113+
- The [Frequently Asked Questions](https://exercism.org/docs/using/faqs)
114+
115+
Should those resources not suffice, you could submit your (incomplete) solution to request mentoring.
116+
117+
Below are some resources for getting help if you run into trouble:
118+
119+
- [The PSF](https://www.python.org) hosts Python downloads, documentation, and community resources.
120+
- [The Exercism Community on Discord](https://exercism.org/r/discord)
121+
- [Python Community on Discord](https://pythondiscord.com/) is a very helpful and active community.
122+
- [/r/learnpython/](https://www.reddit.com/r/learnpython/) is a subreddit designed for Python learners.
123+
- [#python on Libera.chat](https://www.python.org/community/irc/) this is where the core developers for the language hang out and get work done.
124+
- [Python Community Forums](https://discuss.python.org/)
125+
- [Free Code Camp Community Forums](https://forum.freecodecamp.org/)
126+
- [CodeNewbie Community Help Tag](https://community.codenewbie.org/t/help)
127+
- [Pythontutor](http://pythontutor.com/) for stepping through small code snippets visually.
128+
129+
Additionally, [StackOverflow](http://stackoverflow.com/questions/tagged/python) is a good spot to search for your problem/question to see if it has been answered already.
130+
If not - you can always [ask](https://stackoverflow.com/help/how-to-ask) or [answer](https://stackoverflow.com/help/how-to-answer) someone else's question.

resistor-color/README.md

Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,61 @@
1+
# Resistor Color
2+
3+
Welcome to Resistor Color on Exercism's Python Track.
4+
If you need help running the tests or submitting your code, check out `HELP.md`.
5+
6+
## Instructions
7+
8+
If you want to build something using a Raspberry Pi, you'll probably use _resistors_.
9+
For this exercise, you need to know two things about them:
10+
11+
- Each resistor has a resistance value.
12+
- Resistors are small - so small in fact that if you printed the resistance value on them, it would be hard to read.
13+
14+
To get around this problem, manufacturers print color-coded bands onto the resistors to denote their resistance values.
15+
Each band has a position and a numeric value.
16+
17+
The first 2 bands of a resistor have a simple encoding scheme: each color maps to a single number.
18+
19+
In this exercise you are going to create a helpful program so that you don't have to remember the values of the bands.
20+
21+
These colors are encoded as follows:
22+
23+
- black: 0
24+
- brown: 1
25+
- red: 2
26+
- orange: 3
27+
- yellow: 4
28+
- green: 5
29+
- blue: 6
30+
- violet: 7
31+
- grey: 8
32+
- white: 9
33+
34+
The goal of this exercise is to create a way:
35+
36+
- to look up the numerical value associated with a particular color band
37+
- to list the different band colors
38+
39+
Mnemonics map the colors to the numbers, that, when stored as an array, happen to map to their index in the array:
40+
Better Be Right Or Your Great Big Values Go Wrong.
41+
42+
More information on the color encoding of resistors can be found in the [Electronic color code Wikipedia article][e-color-code].
43+
44+
[e-color-code]: https://en.wikipedia.org/wiki/Electronic_color_code
45+
46+
## Source
47+
48+
### Created by
49+
50+
- @gabriel376
51+
52+
### Contributed to by
53+
54+
- @cmccandless
55+
- @Dog
56+
- @tqa236
57+
- @yawpitch
58+
59+
### Based on
60+
61+
Maud de Vries, Erik Schierboom - https://github.com/exercism/problem-specifications/issues/1458

resistor-color/resistor_color.py

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
"""
2+
Utilities for working with the 10-color resistor code.
3+
4+
Mnemonics map the colors to the numbers, that, when stored
5+
as an array, happen to map to their index in the array:
6+
Better Be Right Or Your Great Big Values Go Wrong.
7+
"""
8+
9+
# pylint: disable=duplicate-code
10+
COLORS: tuple = (
11+
"black",
12+
"brown",
13+
"red",
14+
"orange",
15+
"yellow",
16+
"green",
17+
"blue",
18+
"violet",
19+
"grey",
20+
"white",
21+
)
22+
23+
24+
def color_code(color: str) -> int:
25+
"""
26+
Return the numeric code (0-9) for a resistor color.
27+
28+
:param color: Color name.
29+
:type color: str
30+
:returns: Index in the standard 10-color sequence
31+
(0 for 'black' through 9 for 'white').
32+
:rtype: int
33+
:raises ValueError: If color is not a valid resistor color.
34+
"""
35+
return COLORS.index(color)
36+
37+
38+
def colors() -> list:
39+
"""
40+
Return all valid resistor colors in ascending code order.
41+
42+
:returns: List of color names in order from 'black' (0) to 'white' (9).
43+
:rtype: list
44+
"""
45+
return list(COLORS)
Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
# pylint: disable=C0301, C0114, C0115, C0116, R0904
2+
# These tests are auto-generated with test data from:
3+
# https://github.com/exercism/problem-specifications/tree/main/exercises/resistor-color/canonical-data.json
4+
# File last updated on 2023-07-19
5+
6+
import unittest
7+
8+
from resistor_color import (
9+
color_code,
10+
colors,
11+
)
12+
13+
14+
# pylint: disable=duplicate-code
15+
class ResistorColorTest(unittest.TestCase):
16+
def test_black(self):
17+
self.assertEqual(color_code("black"), 0)
18+
19+
def test_white(self):
20+
self.assertEqual(color_code("white"), 9)
21+
22+
def test_orange(self):
23+
self.assertEqual(color_code("orange"), 3)
24+
25+
def test_colors(self):
26+
expected = [
27+
"black",
28+
"brown",
29+
"red",
30+
"orange",
31+
"yellow",
32+
"green",
33+
"blue",
34+
"violet",
35+
"grey",
36+
"white",
37+
]
38+
self.assertEqual(colors(), expected)

0 commit comments

Comments
 (0)