Index: head/textproc/Makefile
===================================================================
--- head/textproc/Makefile
+++ head/textproc/Makefile
@@ -1338,6 +1338,7 @@
     SUBDIR += py-pyes
     SUBDIR += py-pygments
     SUBDIR += py-pygtail
+    SUBDIR += py-pyhamcrest
     SUBDIR += py-pyhwp
     SUBDIR += py-pyphen
     SUBDIR += py-pyscss
Index: head/textproc/py-pyhamcrest/Makefile
===================================================================
--- head/textproc/py-pyhamcrest/Makefile
+++ head/textproc/py-pyhamcrest/Makefile
@@ -0,0 +1,23 @@
+# Created by: Richard Gallamore <ultima@FreeBSD.org>
+# $FreeBSD$
+
+PORTNAME=	PyHamcrest
+DISTVERSION=	1.9.0
+CATEGORIES=	textproc python
+MASTER_SITES=	CHEESESHOP
+PKGNAMEPREFIX=	${PYTHON_PKGNAMEPREFIX}
+
+MAINTAINER=	ultima@FreeBSD.org
+COMMENT=	Hamcrest matchers for Python
+
+LICENSE=	BSD3CLAUSE
+LICENSE_FILE=	${WRKSRC}/LICENSE.txt
+
+RUN_DEPENDS=	${PYTHON_PKGNAMEPREFIX}six>=1.4:devel/py-six@${FLAVOR}
+
+USES=		python:2.7-3.4
+USE_PYTHON=	autoplist distutils
+
+NO_ARCH=	yes
+
+.include <bsd.port.mk>
Index: head/textproc/py-pyhamcrest/distinfo
===================================================================
--- head/textproc/py-pyhamcrest/distinfo
+++ head/textproc/py-pyhamcrest/distinfo
@@ -0,0 +1,3 @@
+TIMESTAMP = 1513497017
+SHA256 (PyHamcrest-1.9.0.tar.gz) = 8ffaa0a53da57e89de14ced7185ac746227a8894dbd5a3c718bf05ddbd1d56cd
+SIZE (PyHamcrest-1.9.0.tar.gz) = 376623
Index: head/textproc/py-pyhamcrest/pkg-descr
===================================================================
--- head/textproc/py-pyhamcrest/pkg-descr
+++ head/textproc/py-pyhamcrest/pkg-descr
@@ -0,0 +1,19 @@
+PyHamcrest is a framework for writing matcher objects, allowing you
+to declaratively define "match" rules. There are a number of
+situations where matchers are invaluable, such as UI validation, or
+data filtering, but it is in the area of writing flexible tests that
+matchers are most commonly used. This tutorial shows you how to use
+PyHamcrest for unit testing.
+
+When writing tests it is sometimes difficult to get the balance right
+between overspecifying the test (and making it brittle to changes),
+and not specifying enough (making the test less valuable since it
+continues to pass even when the thing being tested is broken). Having
+a tool that allows you to pick out precisely the aspect under test
+and describe the values it should have, to a controlled level of
+precision, helps greatly in writing tests that are "just right." Such
+tests fail when the behavior of the aspect under test deviates from
+the expected behavior, yet continue to pass when minor, unrelated
+changes to the behaviour are made.
+
+WWW: https://github.com/hamcrest/PyHamcrest