python_hangman 2.2.3

2.0.0

MVC pattern. The goal was to explicitly demonstrate an MVC pattern out of the scope of web development.

Idiomatic code. In this overhaul there’s a big emphasis on idiomatic code. The code should be describing its’ own intention with the clarity your grandmother could read.

1.0.0

Learning! This was a Test Driven Development(TDD) exercise.

Also, explored:

• Tox, test automation

• Travis CI

• Python version agnostic programming

• Setuptools

• Publishing on pip

• Coverage via coveralls

• Documentation with sphinx and ReadTheDocs

• Cookiecutter development

Model

The model is very simply the hangman game instance–hangman.model.Hangman. It’s a class. Every class should have “state” and the methods of that class should manage that state. In this case, the “state” is the current “state of the game”. The public API are for managing that state.

The entirety of the game logic is contained in hangman.model.Hangman. You could technically play the game in the python console by instantiating the class, submitting guesses with the method hangman.model.Hangman.guess and printing the game state.

For example:

>>> from hangman.model import Hangman
>>> game = Hangman(answer='hangman')
>>> game.guess('a')
hangman(status='_A___A_', misses=[], remaining_turns=10)

>>> game.guess('n').guess('z').guess('e')
hangman(status='_AN__AN', misses=['E', 'Z'], remaining_turns=8)

>>> game.status
'_AN__AN'

>>> game.misses
['E', 'Z']

>>> game.remaining_turns
8

View

hangman.view is a collection of stateless functions that represent the presentation layer. When called these functions handles printing the art to the console, and collecting input from the user.

Controller

In this program, the controller is actually the “game_loop”–hangman.controller.game_loop. I still think of it as a controller because the role it plays–communicating I/O from the view with the model-persistence layer.

The controller tells the view later what to print and what data to collect. It uses that information update the state of the game (model) and handle game events.

Next Release

• Stay Posted

2.2.0 (2015-18-05)

• Fixed max recursion issue with game loop.

• Updated requirements.

• Removed gratuitous docs – less is more.

• 2.2.1 Handle ctrl+d EOF to exit.

• 2.2.2 Fix broken coverage report.

• 2.2.3 Fix broken wheel

2.1.0 (2015-18-05)

• Updated docs, divided and automated in a more reasonable way.

• renamed the github repo to mirror pypi name.

• 2.1.1 Fix pypi’s rst render

2.0.0 (2015-12-05)

• Establishing a changelog.

• Massive refactoring, explicit MVC structure.

• Code is even more idiomatic!

• Created a FlashMessage utility.

• Removed poorly implemented classes in favor of stateless functions.

• Add, Remove support for py35, py32.

• 100% code coverage. (2 untestable, inconsequential lines ignored)