Skip to content

Latest commit

 

History

History
73 lines (39 loc) · 2.65 KB

README.md

File metadata and controls

73 lines (39 loc) · 2.65 KB

Exercism Python Track

Build Status Requirements Status Join the chat at https://gitter.im/exercism/python

Exercism exercises in Python

Contributing Guide

Please see the contributing guide

Working on the Exercises

We welcome both improvements to the existing exercises and new exercises. A list of missing exercise can be found here: http://exercism.io/languages/python/todo

Conventions

  • We use minimalistic stub files for all exercises (#272).
  • We use unittest (Python Standard Library) and no 3rd-party-framework.
  • We use the parameter order self.assertEqual(actual, expected) (#440).

Testing

All exercises must be compatible with Python versions 2.7 and 3.3 upwards.

To test a single exercise (e.g., with Python 2.7):

python2.7 test/check-exercises.py [exercise-name]

To test all exercises (e.g., with Python 3):

python3 test/check-exercises.py

Code Style

The Python code in this repo is meant to follow the PEP8 style guide (a stylized version http://pep8.org).

This repo uses flake8 with default settings to enforce the coding standard.

CI build

This repo uses travis-ci in the following configuration: travis.yml

It will check automatically the code style, the problem configuration and runns the unittests with all supported Python versions.

Pull Requests

We ❤️ pull requests! We even 💖 them if they contain well written commit messages!

Please write the first line of your commit message in the following style:

exercise-name: Changes some things

If there are more details to add, put those into the body of the commit message.

If you're interested, Tim Pope even has an entire blog post on good commit messages.

If you're new to Git take a look at this short guide.

Python icon

The Python logo is an unregistered trademark. We are using a derived logo with the permission of the Python Software Foundation.