primeiro commit com exercicios de Exercism realizados até esta data
This commit is contained in:
@@ -0,0 +1,33 @@
|
||||
{
|
||||
"authors": [],
|
||||
"contributors": [
|
||||
"alirezaghey",
|
||||
"behrtam",
|
||||
"cmccandless",
|
||||
"Dog",
|
||||
"etrepum",
|
||||
"ikhadykin",
|
||||
"kytrinyx",
|
||||
"lowks",
|
||||
"Mofeywalker",
|
||||
"N-Parsons",
|
||||
"pheanex",
|
||||
"sjakobi",
|
||||
"tqa236",
|
||||
"yawpitch"
|
||||
],
|
||||
"files": {
|
||||
"solution": [
|
||||
"etl.py"
|
||||
],
|
||||
"test": [
|
||||
"etl_test.py"
|
||||
],
|
||||
"example": [
|
||||
".meta/example.py"
|
||||
]
|
||||
},
|
||||
"blurb": "Change the data format for scoring a game to more easily add other languages.",
|
||||
"source": "Based on an exercise by the JumpstartLab team for students at The Turing School of Software and Design.",
|
||||
"source_url": "https://turing.edu"
|
||||
}
|
||||
@@ -0,0 +1 @@
|
||||
{"track":"python","exercise":"etl","id":"ed5a9beebea74e5ca3dabd6602d2036a","url":"https://exercism.org/tracks/python/exercises/etl","handle":"sanctushck","is_requester":true,"auto_approve":false}
|
||||
@@ -0,0 +1,130 @@
|
||||
# Help
|
||||
|
||||
## Running the tests
|
||||
|
||||
We use [pytest][pytest: Getting Started Guide] as our website test runner.
|
||||
You will need to install `pytest` on your development machine if you want to run tests for the Python track locally.
|
||||
You should also install the following `pytest` plugins:
|
||||
|
||||
- [pytest-cache][pytest-cache]
|
||||
- [pytest-subtests][pytest-subtests]
|
||||
|
||||
Extended information can be found in our website [Python testing guide][Python track tests page].
|
||||
|
||||
|
||||
### Running Tests
|
||||
|
||||
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_).
|
||||
Test files usually end in `_test.py`, and are the same tests that run on the website when a solution is uploaded.
|
||||
|
||||
Linux/MacOS
|
||||
```bash
|
||||
$ cd {path/to/exercise-folder-location}
|
||||
```
|
||||
|
||||
Windows
|
||||
```powershell
|
||||
PS C:\Users\foobar> cd {path\to\exercise-folder-location}
|
||||
```
|
||||
|
||||
<br>
|
||||
|
||||
Next, run the `pytest` command in your terminal, replacing `{exercise_test.py}` with the name of the test file:
|
||||
|
||||
Linux/MacOS
|
||||
```bash
|
||||
$ python3 -m pytest -o markers=task {exercise_test.py}
|
||||
==================== 7 passed in 0.08s ====================
|
||||
```
|
||||
|
||||
Windows
|
||||
```powershell
|
||||
PS C:\Users\foobar> py -m pytest -o markers=task {exercise_test.py}
|
||||
==================== 7 passed in 0.08s ====================
|
||||
```
|
||||
|
||||
|
||||
### Common options
|
||||
- `-o` : override default `pytest.ini` (_you can use this to avoid marker warnings_)
|
||||
- `-v` : enable verbose output.
|
||||
- `-x` : stop running tests on first failure.
|
||||
- `--ff` : run failures from previous test before running other test cases.
|
||||
|
||||
For additional options, use `python3 -m pytest -h` or `py -m pytest -h`.
|
||||
|
||||
|
||||
### Fixing warnings
|
||||
|
||||
If you do not use `pytest -o markers=task` when invoking `pytest`, you might receive a `PytestUnknownMarkWarning` for tests that use our new syntax:
|
||||
|
||||
```bash
|
||||
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
|
||||
```
|
||||
|
||||
To avoid typing `pytest -o markers=task` for every test you run, you can use a `pytest.ini` configuration file.
|
||||
We have made one that can be downloaded from the top level of the Python track directory: [pytest.ini][pytest.ini].
|
||||
|
||||
You can also create your own `pytest.ini` file with the following content:
|
||||
|
||||
```ini
|
||||
[pytest]
|
||||
markers =
|
||||
task: A concept exercise task.
|
||||
```
|
||||
|
||||
Placing the `pytest.ini` file in the _root_ or _working_ directory for your Python track exercises will register the marks and stop the warnings.
|
||||
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].
|
||||
|
||||
Information on customizing pytest configurations can be found in the `pytest` documentation on [configuration file formats][pytest: configuration file formats].
|
||||
|
||||
|
||||
### Extending your IDE or Code Editor
|
||||
|
||||
Many IDEs and code editors have built-in support for using `pytest` and other code quality tools.
|
||||
Some community-sourced options can be found on our [Python track tools page][Python track tools page].
|
||||
|
||||
[Pytest: Getting Started Guide]: https://docs.pytest.org/en/latest/getting-started.html
|
||||
[Python track tools page]: https://exercism.org/docs/tracks/python/tools
|
||||
[Python track tests page]: https://exercism.org/docs/tracks/python/tests
|
||||
[pytest-cache]:http://pythonhosted.org/pytest-cache/
|
||||
[pytest-subtests]:https://github.com/pytest-dev/pytest-subtests
|
||||
[pytest.ini]: https://github.com/exercism/python/blob/main/pytest.ini
|
||||
[pytest: configuration file formats]: https://docs.pytest.org/en/6.2.x/customize.html#configuration-file-formats
|
||||
[pytest: marking test functions with attributes]: https://docs.pytest.org/en/6.2.x/mark.html#raising-errors-on-unknown-marks
|
||||
[pytest: working with custom markers]: https://docs.pytest.org/en/6.2.x/example/markers.html#working-with-custom-markers
|
||||
|
||||
## Submitting your solution
|
||||
|
||||
You can submit your solution using the `exercism submit etl.py` command.
|
||||
This command will upload your solution to the Exercism website and print the solution page's URL.
|
||||
|
||||
It's possible to submit an incomplete solution which allows you to:
|
||||
|
||||
- See how others have completed the exercise
|
||||
- Request help from a mentor
|
||||
|
||||
## Need to get help?
|
||||
|
||||
If you'd like help solving the exercise, check the following pages:
|
||||
|
||||
- The [Python track's documentation](https://exercism.org/docs/tracks/python)
|
||||
- The [Python track's programming category on the forum](https://forum.exercism.org/c/programming/python)
|
||||
- [Exercism's programming category on the forum](https://forum.exercism.org/c/programming/5)
|
||||
- The [Frequently Asked Questions](https://exercism.org/docs/using/faqs)
|
||||
|
||||
Should those resources not suffice, you could submit your (incomplete) solution to request mentoring.
|
||||
|
||||
Below are some resources for getting help if you run into trouble:
|
||||
|
||||
- [The PSF](https://www.python.org) hosts Python downloads, documentation, and community resources.
|
||||
- [The Exercism Community on Discord](https://exercism.org/r/discord)
|
||||
- [Python Community on Discord](https://pythondiscord.com/) is a very helpful and active community.
|
||||
- [/r/learnpython/](https://www.reddit.com/r/learnpython/) is a subreddit designed for Python learners.
|
||||
- [#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.
|
||||
- [Python Community Forums](https://discuss.python.org/)
|
||||
- [Free Code Camp Community Forums](https://forum.freecodecamp.org/)
|
||||
- [CodeNewbie Community Help Tag](https://community.codenewbie.org/t/help)
|
||||
- [Pythontutor](http://pythontutor.com/) for stepping through small code snippets visually.
|
||||
|
||||
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.
|
||||
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.
|
||||
@@ -0,0 +1,72 @@
|
||||
# ETL
|
||||
|
||||
Welcome to ETL on Exercism's Python Track.
|
||||
If you need help running the tests or submitting your code, check out `HELP.md`.
|
||||
|
||||
## Introduction
|
||||
|
||||
You work for a company that makes an online multiplayer game called Lexiconia.
|
||||
|
||||
To play the game, each player is given 13 letters, which they must rearrange to create words.
|
||||
Different letters have different point values, since it's easier to create words with some letters than others.
|
||||
|
||||
The game was originally launched in English, but it is very popular, and now the company wants to expand to other languages as well.
|
||||
|
||||
Different languages need to support different point values for letters.
|
||||
The point values are determined by how often letters are used, compared to other letters in that language.
|
||||
|
||||
For example, the letter 'C' is quite common in English, and is only worth 3 points.
|
||||
But in Norwegian it's a very rare letter, and is worth 10 points.
|
||||
|
||||
To make it easier to add new languages, your team needs to change the way letters and their point values are stored in the game.
|
||||
|
||||
## Instructions
|
||||
|
||||
Your task is to change the data format of letters and their point values in the game.
|
||||
|
||||
Currently, letters are stored in groups based on their score, in a one-to-many mapping.
|
||||
|
||||
- 1 point: "A", "E", "I", "O", "U", "L", "N", "R", "S", "T",
|
||||
- 2 points: "D", "G",
|
||||
- 3 points: "B", "C", "M", "P",
|
||||
- 4 points: "F", "H", "V", "W", "Y",
|
||||
- 5 points: "K",
|
||||
- 8 points: "J", "X",
|
||||
- 10 points: "Q", "Z",
|
||||
|
||||
This needs to be changed to store each individual letter with its score in a one-to-one mapping.
|
||||
|
||||
- "a" is worth 1 point.
|
||||
- "b" is worth 3 points.
|
||||
- "c" is worth 3 points.
|
||||
- "d" is worth 2 points.
|
||||
- etc.
|
||||
|
||||
As part of this change, the team has also decided to change the letters to be lower-case rather than upper-case.
|
||||
|
||||
~~~~exercism/note
|
||||
If you want to look at how the data was previously structured and how it needs to change, take a look at the examples in the test suite.
|
||||
~~~~
|
||||
|
||||
## Source
|
||||
|
||||
### Contributed to by
|
||||
|
||||
- @alirezaghey
|
||||
- @behrtam
|
||||
- @cmccandless
|
||||
- @Dog
|
||||
- @etrepum
|
||||
- @ikhadykin
|
||||
- @kytrinyx
|
||||
- @lowks
|
||||
- @Mofeywalker
|
||||
- @N-Parsons
|
||||
- @pheanex
|
||||
- @sjakobi
|
||||
- @tqa236
|
||||
- @yawpitch
|
||||
|
||||
### Based on
|
||||
|
||||
Based on an exercise by the JumpstartLab team for students at The Turing School of Software and Design. - https://turing.edu
|
||||
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
@@ -0,0 +1,5 @@
|
||||
def transform(legacy_data: dict[int, list[str]]) -> dict[str, int]:
|
||||
new_data: dict[str, int] = {}
|
||||
for key in legacy_data:
|
||||
new_data.update(dict.fromkeys("".join(legacy_data[key]).lower(), key))
|
||||
return new_data
|
||||
@@ -0,0 +1,66 @@
|
||||
# These tests are auto-generated with test data from:
|
||||
# https://github.com/exercism/problem-specifications/tree/main/exercises/etl/canonical-data.json
|
||||
# File last updated on 2023-07-19
|
||||
|
||||
import unittest
|
||||
|
||||
from etl import (
|
||||
transform,
|
||||
)
|
||||
|
||||
|
||||
class EtlTest(unittest.TestCase):
|
||||
def test_single_letter(self):
|
||||
legacy_data = {1: ["A"]}
|
||||
data = {"a": 1}
|
||||
self.assertEqual(transform(legacy_data), data)
|
||||
|
||||
def test_single_score_with_multiple_letters(self):
|
||||
legacy_data = {1: ["A", "E", "I", "O", "U"]}
|
||||
data = {"a": 1, "e": 1, "i": 1, "o": 1, "u": 1}
|
||||
self.assertEqual(transform(legacy_data), data)
|
||||
|
||||
def test_multiple_scores_with_multiple_letters(self):
|
||||
legacy_data = {1: ["A", "E"], 2: ["D", "G"]}
|
||||
data = {"a": 1, "d": 2, "e": 1, "g": 2}
|
||||
self.assertEqual(transform(legacy_data), data)
|
||||
|
||||
def test_multiple_scores_with_differing_numbers_of_letters(self):
|
||||
legacy_data = {
|
||||
1: ["A", "E", "I", "O", "U", "L", "N", "R", "S", "T"],
|
||||
2: ["D", "G"],
|
||||
3: ["B", "C", "M", "P"],
|
||||
4: ["F", "H", "V", "W", "Y"],
|
||||
5: ["K"],
|
||||
8: ["J", "X"],
|
||||
10: ["Q", "Z"],
|
||||
}
|
||||
data = {
|
||||
"a": 1,
|
||||
"b": 3,
|
||||
"c": 3,
|
||||
"d": 2,
|
||||
"e": 1,
|
||||
"f": 4,
|
||||
"g": 2,
|
||||
"h": 4,
|
||||
"i": 1,
|
||||
"j": 8,
|
||||
"k": 5,
|
||||
"l": 1,
|
||||
"m": 3,
|
||||
"n": 1,
|
||||
"o": 1,
|
||||
"p": 3,
|
||||
"q": 10,
|
||||
"r": 1,
|
||||
"s": 1,
|
||||
"t": 1,
|
||||
"u": 1,
|
||||
"v": 4,
|
||||
"w": 4,
|
||||
"x": 8,
|
||||
"y": 4,
|
||||
"z": 10,
|
||||
}
|
||||
self.assertEqual(transform(legacy_data), data)
|
||||
Reference in New Issue
Block a user