2.0.3_1textprocΣ=1 2.0.3_1Version of this port present on the latest quarterly branch.upstream: v2.1.0A newer version was found upstream by portscout, first on 2026-06-20.
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.
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above. NOTE: This is a Python port. Instead of py311-PyHamcrest listed in the above command, you can pick from the names under the Packages section.
python: bump all USE_PYTHON=distutils consumers after RUN_DEPENDS removal
Any missed ports, feel free to bump.
Any ports that need setuptools at runtime can have the devel/py-setuptools
manually added back to RUN_DEPENDS, but understand that this practice
is deprecated; see CHANGES for details.
all: remove explicit versions in USES=python for "3.x+"
The logic in USES=python will automatically convert this to 3.8+ by
itself.
Adjust two ports that only had Python 3.7 mentioned but build fine
on Python 3.8 too.
finance/quickfix: mark BROKEN with PYTHON
libtool: compile: c++ -DHAVE_CONFIG_H -I. -I../.. -I -I. -I.. -I../.. -I../C++
-DLIBICONV_PLUG -DPYTHON_MAJOR_VERSION=3 -Wno-unused-variable
-Wno-maybe-uninitialized -O2 -pipe -DLIBICONV_PLUG -fstack-protector-strong
-fno-strict-aliasing -DLIBICONV_PLUG -Wall -ansi
-Wno-unused-command-line-argument -Wpointer-arith -Wwrite-strings
-Wno-overloaded-virtual -Wno-deprecated-declarations -Wno-deprecated -std=c++0x
-MT _quickfix_la-QuickfixPython.lo -MD -MP -MF
.deps/_quickfix_la-QuickfixPython.Tpo -c QuickfixPython.cpp -fPIC -DPIC -o
.libs/_quickfix_la-QuickfixPython.o
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean
'-Wno-uninitialized'? [-Wunknown-warning-option]
QuickfixPython.cpp:175:11: fatal error: 'Python.h' file not found
^~~~~~~~~~
1 warning and 1 error generated.
Reviewed by: portmgr, vishwin, yuri
Differential Revision: <https://reviews.freebsd.org/D40568>
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
* Revision bump for distfile change
* Changed MASTER_SITES to GitHub, GitHub includes test suite
* Added test target and depends, added for testing newer versions of python
PR: 235585
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
Differential Revision: https://reviews.freebsd.org/D13520
