GitXplorerGitXplorer
p

typed_graphs

public
3 stars
0 forks
0 issues

Commits

List of commits on branch master.
Unverified
1d5985d69b975587af4d528ad5380380455e09a5

Update README

ppkch committed 8 years ago
Unverified
df7933f00def69cac3080381440a6d278c71271c

Make graph_generic.py standalone

ppkch committed 8 years ago
Unverified
c042cb2f43c20a4b7945309a57d2bfb53be76a01

Updates to improve coverage and logic

ppkch committed 8 years ago
Unverified
bfbfdeb1115a34d56c634e736d0cd1b343bca313

* Fix bug in ReversibleGraph

ppkch committed 8 years ago
Unverified
7c261ffb371c4559c4036f348256aa0ea609fb42

Add undirected graph

ppkch committed 8 years ago
Unverified
e3bcbdc35daa99b80419299a107aa46079444360

Added non-generic Graph and ReversibleGraph

ppkch committed 8 years ago

README

The README file for this repository.

Build Status Coverage Status MIT licensed

Type Annotated Graphs in Python

This is not a graph library! It is just the source code for a series of blog articles. It's not tested as extensively as a library should be, and it's also not optimized in any way.

If you do want to use it in your project, the most reasonable implementations are:

The blog posts are here:

They summarize my experience with type hints in a small project. I go through several iterations of graph representation and traversal, and discuss various design and type checking issues. I use python 3.6 and the latest version of mypy.

My workflow used to be:

  • push my code to this repo to run tests / type checker using Travis CI
  • push it to gist, from which it is directly embedded in the blog

It was a good way to test the code shown in the posts. Later, I needed to use this code myself, so I rearranged the folder structure as if it was a regular package. Unfortunately, it means I can't push the entire thing to gist any more.