Official low-level client for Elasticsearch. It's goal is to provide common
ground for all Elasticsearch-related code in Python; because of this it tries
to be opinion-free and very extendable.
port moved to textproc/py-elasticsearch6 on 2026-06-30 REASON: Has expired: 5.x reached EoL, last version was in 2018 - use textproc/py-elasticsearch 9.3.0 instead
textproc/py-elasticsearch5: Remove expired port
2026-06-30 textproc/py-elasticsearch5: 5.x reached EoL, last version was in 2018
- use textproc/py-elasticsearch 9.3.0 instead
textproc/py-elasticsearch5: Deprecate - 5.x reached EoL, last version was in
2018
In such cases, I usually update to the latest version in the branch
(5.5.2 => 5.5.5) and only then deprecate the port, but here there is no
point in this - this is a very old branch, the latest version of which
was released in 2018, no one in the tree depends on it, and the ports
have the latest version 9.3.0 in the port textproc/py-elasticsearch.
Deprecate with expiration date 2026-06-30.
Approved by: elastic (maintainer, implicit - inactive for more than 6 months)
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 )
*/*: Remove redundant '-[0-9]*' from CONFLICTS
The conflict checks compare the patterns first against the package
names without version (as reported by "pkg query "%n"), then - if
there was no match - agsinst the full package names including the
version (as reported by "pkg query "%n-%v").
Many CONFLICTS definitions used patterns like "bash-[0-9]*" to filter
for the bash package in any version. But that pattern is functionally
identical with just "bash".
Approved by: portmgr (blanket)
textproc/py-elasticsearch5: Prepare for urllib3 >= 1.25
* Backport a patch from the 7.x branch of upstream repository that fixes a
possible runtime issue with urllib3 1.25 [1] since that release verifies
SSL certificates by default.
Disabling SSL certificate verification via "verify_certs" in elasticsearch
won't work then as expected thus set "cert_reqs=CERT_NONE" explicitly to
restore that behavior.
PR: 241875, 229322 [1]
Approved by: maintainer timeout (elastic, 14 days)
MFH: 2019Q4
Create textproc/py-elasticsearch5
The 5.x version of the py-elasticsearch module is still required in
situations where the newer 6.x module is not backwards compatible.