| Port details |
- py-pyhamcrest Hamcrest matchers for Python
- 2.0.3 textproc
 =3      2.0.3Version of this port present on the latest quarterly branch. - Maintainer: ultima@FreeBSD.org
- Port Added: 2018-03-03 07:16:21
- Last Update: 2023-06-27 19:34:34
- Commit Hash: 3d9a815
- People watching this port, also watch:: qtkeychain-qt5, py39-treq, py311-Automat, linux-c7-atk, py39-beautifulsoup
- Also Listed In: python
- License: BSD3CLAUSE
- WWW:
- https://github.com/hamcrest/PyHamcrest
- Description:
- 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.
  ¦  ¦  ¦  ¦ 
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - There is no configure plist information for this port.
- Dependency lines:
-
- ${PYTHON_PKGNAMEPREFIX}PyHamcrest>0:textproc/py-pyhamcrest@${PY_FLAVOR}
- To install the port:
- cd /usr/ports/textproc/py-pyhamcrest/ && make install clean
- To add the package, run one of these commands:
- pkg install textproc/py-pyhamcrest
- pkg install py39-PyHamcrest
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 py39-PyHamcrest listed in the above command, you can pick from the names under the Packages section.- PKGNAME: py39-PyHamcrest
- Package flavors (<flavor>: <package>)
- distinfo:
- TIMESTAMP = 1641865846
SHA256 (hamcrest-PyHamcrest-V2.0.3_GH0.tar.gz) = 7e3738e73be4743b012f697aa4d2aab17cb3320196a95f56bbc09ae68a3b7f06
SIZE (hamcrest-PyHamcrest-V2.0.3_GH0.tar.gz) = 59353
Packages (timestamps in pop-ups are UTC):
- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Build dependencies:
-
- py39-setuptools>=63.1.0 : devel/py-setuptools@py39
- python3.9 : lang/python39
- Test dependencies:
-
- py39-hypothesis>=1.11 : devel/py-hypothesis@py39
- py39-pytest>=2.8 : devel/py-pytest@py39
- py39-mock>=0 : devel/py-mock@py39
- py39-pytest-cov>=0 : devel/py-pytest-cov@py39
- python3.9 : lang/python39
- Runtime dependencies:
-
- py39-setuptools>=63.1.0 : devel/py-setuptools@py39
- python3.9 : lang/python39
- There are no ports dependent upon this port
Configuration Options:- No options to configure
- Options name:
- textproc_py-pyhamcrest
- USES:
- python
- FreshPorts was unable to extract/find any pkg message
- Master Sites:
|
| Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
| Commit | Credits | Log message |
|---|
2.0.3
27 Jun 2023 19:34:34
 |
Rene Ladan (rene) |
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> |
07 Sep 2022 21:58:51
|
Stefan Eßer (se) |
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) |
2.0.3
07 Sep 2022 21:10:59
|
Stefan Eßer (se) |
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  ) |
2.0.3
20 Jul 2022 14:23:14
|
Tobias C. Berner (tcberner) |
textproc: remove 'Created by' lines
A big Thank You to the original contributors of these ports:
* "Choe, Cheng-Dae" whitekid
* -
* <glewis@FreeBSD.org>
* <koshy@india.hp.com>
* Aaron Dalton <aaron@FreeBSD.org>
* Aaron Dalton <aaron@daltons.ca>
* Aaron Straup Cope
* Aaron Straup Cope <ascope@cpan.org>
* Ache
* Adam Herzog <adam@herzogdesigns.com>
* Adam Weinberger <adamw@FreeBSD.org> (Only the first 15 lines of the commit message are shown above ) |
2.0.3
11 Jan 2022 02:29:32
|
Richard Gallamore (ultima) |
textproc/py-pyhamcrest: Updated to 2.0.3
Changes: https://github.com/hamcrest/PyHamcrest/blob/V2.0.3/CHANGELOG.rst |
2.0.2
06 Apr 2021 14:31:07
|
Mathieu Arnold (mat) |
Remove # $FreeBSD$ from Makefiles. |
2.0.2
28 Dec 2020 23:02:15
 |
antoine |
Drop python 2.7 support from a few ports
With hat: portmgr |
2.0.2
16 Apr 2020 01:57:59
|
ultima |
* Updated to 2.0.2
Changes: https://github.com/hamcrest/PyHamcrest/blob/master/CHANGES.txt |
1.10.1
17 Jan 2020 06:42:28
|
ultima |
Updated to 1.10.1
Changes: https://github.com/hamcrest/PyHamcrest/blob/V1.10.1/CHANGES.txt |
1.9.0_1
14 Feb 2019 19:45:33
|
ultima |
* 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 |
1.9.0
20 Jun 2018 17:05:44
|
mat |
Use PY_FLAVOR for dependencies.
FLAVOR is the current port's flavor, it should not be used outside of
this scope.
Sponsored by: Absolight |
1.9.0
03 Mar 2018 07:16:13
|
ultima |
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 |
As an Amazon Associate I earn from qualifying purchases.