diff --git a/.github/workflows/pylint.yml b/.github/workflows/pylint.yml
new file mode 100644
index 0000000..4e975a7
--- /dev/null
+++ b/.github/workflows/pylint.yml
@@ -0,0 +1,28 @@
+name: Pylint
+
+on:
+ push:
+ branches: [ main ]
+ pull_request:
+ branches: [ main ]
+
+jobs:
+ build:
+ runs-on: ubuntu-latest
+ strategy:
+ matrix:
+ python-version: ["3.12"]
+ steps:
+ - uses: actions/checkout@v4
+ - name: Set up Python ${{ matrix.python-version }}
+ uses: actions/setup-python@v3
+ with:
+ python-version: ${{ matrix.python-version }}
+ - name: Install dependencies
+ run: |
+ python -m pip install --upgrade pip
+ pip install pylint
+ pip install -r requirements.txt
+ - name: Analysing the code with pylint
+ run: |
+ python -m pylint --verbose $(find . -name "*.py" ! -path "*/.venv/*" ! -path "*/venv/*") --rcfile=.pylintrc
\ No newline at end of file
diff --git a/.github/workflows/pytest.yml b/.github/workflows/pytest.yml
new file mode 100644
index 0000000..c9c9d86
--- /dev/null
+++ b/.github/workflows/pytest.yml
@@ -0,0 +1,29 @@
+name: Pytest Workflow
+
+on:
+ push:
+ branches: [ main ]
+ pull_request:
+ branches: [ main ]
+
+jobs:
+ test:
+ runs-on: ubuntu-latest
+
+ steps:
+ - name: Checkout code
+ uses: actions/checkout@v4
+
+ - name: Set up Python 3.12
+ uses: actions/setup-python@v5
+ with:
+ python-version: '3.12'
+
+ - name: Install dependencies
+ run: |
+ python -m pip install --upgrade pip
+ pip install -r requirements.txt
+ pip install pytest
+
+ - name: Run pytest
+ run: pytest --verbose --ignore=solutions
\ No newline at end of file
diff --git a/.pylintrc b/.pylintrc
new file mode 100644
index 0000000..97d344e
--- /dev/null
+++ b/.pylintrc
@@ -0,0 +1,3 @@
+[MASTER]
+ignore=.venv
+ignore-paths=^(.*/|)solutions/.*$
\ No newline at end of file
diff --git a/README.md b/README.md
index 6fd8298..7770891 100644
--- a/README.md
+++ b/README.md
@@ -1,5 +1,22 @@
-# Exercism Python Track
+# [Exercism Python Track](https://exercism.io/my/tracks/python)
-Learn and master concepts to achieve fluency in Python.
+
+
+
+
+
+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 triangle.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.
\ No newline at end of file
diff --git a/triangle/README.md b/triangle/README.md
new file mode 100644
index 0000000..961c673
--- /dev/null
+++ b/triangle/README.md
@@ -0,0 +1,60 @@
+# Triangle
+
+Welcome to Triangle on Exercism's Python Track.
+If you need help running the tests or submitting your code, check out `HELP.md`.
+
+## Instructions
+
+Determine if a triangle is equilateral, isosceles, or scalene.
+
+An _equilateral_ triangle has all three sides the same length.
+
+An _isosceles_ triangle has at least two sides the same length.
+(It is sometimes specified as having exactly two sides the same length, but for the purposes of this exercise we'll say at least two.)
+
+A _scalene_ triangle has all sides of different lengths.
+
+## Note
+
+For a shape to be a triangle at all, all sides have to be of length > 0, and the sum of the lengths of any two sides must be greater than or equal to the length of the third side.
+
+In equations:
+
+Let `a`, `b`, and `c` be sides of the triangle.
+Then all three of the following expressions must be true:
+
+```text
+a + b ≥ c
+b + c ≥ a
+a + c ≥ b
+```
+
+See [Triangle Inequality][triangle-inequality]
+
+[triangle-inequality]: https://en.wikipedia.org/wiki/Triangle_inequality
+
+## Source
+
+### Contributed to by
+
+- @behrtam
+- @BethanyG
+- @cmccandless
+- @Dog
+- @ikhadykin
+- @kytrinyx
+- @lowks
+- @mpatibandla
+- @N-Parsons
+- @Nishant23
+- @pheanex
+- @rozuur
+- @sjakobi
+- @Stigjb
+- @tqa236
+- @xitanggg
+- @YuriyCherniy
+
+### Based on
+
+The Ruby Koans triangle project, parts 1 & 2 - https://web.archive.org/web/20220831105330/http://rubykoans.com
\ No newline at end of file
diff --git a/triangle/triangle.py b/triangle/triangle.py
new file mode 100644
index 0000000..6537e75
--- /dev/null
+++ b/triangle/triangle.py
@@ -0,0 +1,52 @@
+"""Determine if a triangle is equilateral, isosceles, or scalene."""
+
+
+def equilateral(sides: list) -> bool:
+ """
+ An equilateral triangle has all three sides the same length.
+ """
+ if all_sides_positive(sides) and no_inequality_violation(sides):
+ return sides[0] == sides[1] == sides[2]
+ return False
+
+
+def isosceles(sides: list) -> bool:
+ """
+ An isosceles triangle has at least two sides the same length.
+ (It is sometimes specified as having exactly two sides the same length,
+ but for the purposes of this exercise we'll say at least two.)
+ """
+ if all_sides_positive(sides) and no_inequality_violation(sides):
+ return sides[0] == sides[1] or sides[1] == sides[2] or sides[0] == sides[2]
+ return False
+
+
+def scalene(sides: list) -> bool:
+ """
+ A scalene triangle has all sides of different lengths.
+ """
+ if all_sides_positive(sides) and no_inequality_violation(sides):
+ return sides[0] != sides[1] and sides[1] != sides[2] and sides[0] != sides[2]
+ return False
+
+
+def no_inequality_violation(sides: list) -> bool:
+ """
+ Let a, b, and c be sides of the triangle.
+ Then all three of the following expressions must be true:
+
+ a + b ≥ c
+ b + c ≥ a
+ a + c ≥ b
+ """
+ return (sides[0] + sides[1] >= sides[2] and
+ sides[0] + sides[2] >= sides[1] and
+ sides[2] + sides[1] >= sides[0])
+
+
+def all_sides_positive(sides: list) -> bool:
+ """
+ No zeroes or negative numbers allowed.
+ All triangles should have 3 sides.
+ """
+ return all(side > 0 for side in sides) and len(sides) == 3
diff --git a/triangle/triangle_test.py b/triangle/triangle_test.py
new file mode 100644
index 0000000..9312b90
--- /dev/null
+++ b/triangle/triangle_test.py
@@ -0,0 +1,85 @@
+# pylint: disable=C0116, C0114, C0115
+
+# These tests are auto-generated with test data from:
+# https://github.com/exercism/problem-specifications/tree/main/exercises/triangle/canonical-data.json
+# File last updated on 2023-07-19
+
+import unittest
+
+from triangle import (
+ equilateral,
+ isosceles,
+ scalene,
+)
+
+
+# pylint: disable=C0116, C0114, C0115
+class EquilateralTriangleTest(unittest.TestCase):
+ def test_all_sides_are_equal(self):
+ self.assertIs(equilateral([2, 2, 2]), True)
+
+ def test_any_side_is_unequal(self):
+ self.assertIs(equilateral([2, 3, 2]), False)
+
+ def test_no_sides_are_equal(self):
+ self.assertIs(equilateral([5, 4, 6]), False)
+
+ def test_all_zero_sides_is_not_a_triangle(self):
+ self.assertIs(equilateral([0, 0, 0]), False)
+
+ def test_sides_may_be_floats(self):
+ self.assertIs(equilateral([0.5, 0.5, 0.5]), True)
+
+
+# pylint: disable=C0116
+class IsoscelesTriangleTest(unittest.TestCase):
+ def test_last_two_sides_are_equal(self):
+ self.assertIs(isosceles([3, 4, 4]), True)
+
+ def test_first_two_sides_are_equal(self):
+ self.assertIs(isosceles([4, 4, 3]), True)
+
+ def test_first_and_last_sides_are_equal(self):
+ self.assertIs(isosceles([4, 3, 4]), True)
+
+ def test_equilateral_triangles_are_also_isosceles(self):
+ self.assertIs(isosceles([4, 4, 4]), True)
+
+ def test_no_sides_are_equal(self):
+ self.assertIs(isosceles([2, 3, 4]), False)
+
+ def test_first_triangle_inequality_violation(self):
+ self.assertIs(isosceles([1, 1, 3]), False)
+
+ def test_second_triangle_inequality_violation(self):
+ self.assertIs(isosceles([1, 3, 1]), False)
+
+ def test_third_triangle_inequality_violation(self):
+ self.assertIs(isosceles([3, 1, 1]), False)
+
+ def test_sides_may_be_floats(self):
+ self.assertIs(isosceles([0.5, 0.4, 0.5]), True)
+
+
+# pylint: disable=C0116
+class ScaleneTriangleTest(unittest.TestCase):
+ def test_no_sides_are_equal(self):
+ self.assertIs(scalene([5, 4, 6]), True)
+
+ def test_all_sides_are_equal(self):
+ self.assertIs(scalene([4, 4, 4]), False)
+
+ def test_first_and_second_sides_are_equal(self):
+ self.assertIs(scalene([4, 4, 3]), False)
+
+ def test_first_and_third_sides_are_equal(self):
+ self.assertIs(scalene([3, 4, 3]), False)
+
+ def test_second_and_third_sides_are_equal(self):
+ self.assertIs(scalene([4, 3, 3]), False)
+
+ def test_may_not_violate_triangle_inequality(self):
+ self.assertIs(scalene([7, 3, 2]), False)
+
+ def test_sides_may_be_floats(self):
+ self.assertIs(scalene([0.5, 0.4, 0.6]), True)