NumPy is the fundamental package for scientific computing with Python. It
contains among other things:
- a powerful N-dimensional array object
- sophisticated (broadcasting) functions
- tools for integrating C/C++ and Fortran code
- useful linear algebra, Fourier transform, and random number capabilities
Besides its obvious scientific uses, NumPy can also be used as an efficient
multi-dimensional container of generic data. Arbitrary data-types can be
defined. This allows NumPy to seamlessly and speedily integrate with a wide
variety of databases.
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-numpy listed in the above command, you can pick from the names under the Packages section.
===> The following configuration options are available for py311-numpy-2.4.6_1,1:
DOCS=on: Build and/or install documentation
====> Options available for the single BLASLIB: you have to select exactly one of them
BLIS=off: BLIS BLAS-like implementation
FLEXIBLAS=off: FlexiBLAS BLAS implementation
NETLIB=off: BLAS implementation from Netlib
OPENBLAS=on: OpenBLAS BLAS implementation
====> Use CPU-specific optimizations: you have to select exactly one of them
MIN=on: Minimum recommended CPU features (x86-64-v2 microarchitecture)
NATIVE=off: Use native optimization (-march=native)
NONE=off: Dispatched optimizations only (not recommended except old CPUs)
===> Use 'make config' to modify these settings
math/py-numpy: Revert "build for all Python versions (for graphics/blender)"
Reverted due to reversal of the devel/meson change.
This reverts commit 3a42e1635236292984846ff29946f902d387b10b.
math/py-numpy: add SIMD options
Per the 2.4 release notes, the default/minimum baseline for compiled
optimisations on amd64 and i386 is increased to the v2 microarchitecture.
Thus, those using CPUs without the full feature set from v2 will
encounter SIGILL when running numpy with the default/minimum baseline.
Add option to disable compiled optimisations, relying entirely on
dispatched code paths when available and applicable. Not recommended
except for very old CPUs. Also add native option.
PR: 295633, 295664
*: Revise USES=python:... version range constraints
and strip all lower bounds of 3.9 or 3.10 because they are implied now.
python:3.9-X -> python:-X
python:3.9+ -> python
python:3.10-X -> python:-X
python:3.10+ -> python
(options such as ,build preserved)
math/py-numpy: Revert "math/py-numpy: Migrate to PEP517"
This reverts commit 3f582fcf38bb0cee40f9346683490aceb3bda654.
The goal was to unblock package building ASAP while we investigate
Requested by: antoine
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.
*/*: bump PORTREVISION after OpenBLAS upgrade
Remark: this souldn’t be necessary, because the version of the library is the
same, but due to many changes between these releases, it is safer this way.
PR: 284314
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>
math/py-numpy: fix build on powerpc64le
In file included from numpy/core/src/umath/loops_comparison.dispatch.c.src:12:
In file included from numpy/core/src/common/simd/simd.h:63:
In file included from numpy/core/src/common/simd/vec/vec.h:105:
numpy/core/src/common/simd/vec/memory.h:113:1: error: call to 'vec_st' is
ambiguous
NPYV_IMPL_VEC_MEM(f64, f64)
^~~~~~~~~~~~~~~~~~~~~~~~~~~
numpy/core/src/common/simd/vec/memory.h:94:7: note: expanded from macro
'NPYV_IMPL_VEC_MEM'
{ npyv__storea((npyv_lanetype_##DW_CAST*)ptr, (npyv_##DW_CAST)vec); }
\
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
numpy/core/src/common/simd/vec/memory.h:42:36: note: expanded from macro
'npyv__storea'
#define npyv__storea(PTR, VEC) vec_st(VEC, 0, PTR)
^~~~~~
/usr/lib/clang/14.0.5/include/altivec.h:11130:37: note: candidate function
(Only the first 15 lines of the commit message are shown above )
math/py-numpy: fix runtime on powerpc64*
Currently powerpc64* is not properly detected by numpy, due to python
returning just "powerpc" as architecture name. This commit fixes architecture
detection with numpy and properly checks for CPU features on FreeBSD.
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 )
math: remove 'Created by' lines
A big Thank You to the original contributors of these ports:
* Aaron Dalton <aaron@FreeBSD.org>
* Aaron Dalton <aaron@daltons.ca>
* Alessando Sagratini <ale_sagra@hotmail.com>
* Alex Dupre <ale@FreeBSD.org>
* Alexey Dokuchaev <danfe@FreeBSD.org>
* Amarendra Godbole <amarendra.godbole@gmail.com>
* Anders Nordby <anders@FreeBSD.org>
* Andreas Fehlner (fehlner@gmx.de)
* Andrew L. Neporada <andrew@chg.ru>
* Andrey <gugu@zoo.rambler.ru>
* Andrey Zakhvatov
(Only the first 15 lines of the commit message are shown above )
Mk/bsd.default-versions.mk: chase the switch to Python 3.9
Following the rules of
<https://wiki.freebsd.org/Python#Steps_to_switch_the_Python_default_version>
PR: 261703
math/py-numpy: revert obsolete commit 507c189b28
The sched_getaffinity() function in the C library returned a different
error code than expected (i.e. other than returned by GLIBC) if the
requested CPU set size did not match the one expected by the system.
The error code has been changed from ERANGE to EINVAL as expected by
the wrapper for os.sched_getaffinity() in Python, obsoleting the patch
that commented out the failing function call in setup.py.
math/py-numpy: work around build issue on -CURRENT
A sched_getaffinity function has been added to -CURRENT and the
Python build detects it presence and provides a Python function
os.sched_getaffinity().
Apparently the C library function is not correctly wrapped and
returns an out of buounds result.
Comment out the call of os.sched_getaffinity() call until this
function works correctly in the Python interpreter.
No port revision bump, since this is just a temporary fix for the
broken build on -CURRENT.
Reported by: antoine
math/suitesparse: adapt dependency lines after modularization
Do not bump PORTREVISION, because this should not change the resulting
packages.
Note for maintainers: try to not depend on the whole suitesparse package,
especially if your port do not require GraphBLAS (the biggest one).
*: Bump a few ports after the Python 3.7 to 3.8 switchover
Bump the PORTREVISION of the following ports as the concurrent symlinks
change with a new default version of Python:
* devel/py-setuptools
* lang/cython
* math/py-numpy
This is a follow-up to 6cd3db2d03cc544c5893e41dbbacd2000fcbd35a .
PR: 253815
Approved by: kai (python, maintainer)
Bump 37 ports depending on math/openblas through USES=blaslapack:openblas
because after the recent math/openblas update the library name changed in
openblas
math/py-numpy: improve patch to fix build with OpenBlas
This patch adds openblas to the list of cblas compatible libs instead
PR: 243497
Submitted by: John Hein <jcfyecrayz@liamekaens.com>
Fix math/openblas and bump dependent ports
* Fix build on i386 [1]
* Fix science/code_saturne build with new openblas [2]
* Avoid installing private headers [3]
* Prevent build from optimizing for host by correcting build confg [4]
* Bump portrevision of dependent ports [5]
This is correcting issues from r523749 [1][2][4] and r515970 [3]
PR: 231371
Reported by: build cluster [1]
Reported by: Dima Pasechnik <dimpase+freebsd@gmail.com> [2]
Reported by: many [5]
Reviewed by: mat, bapt
Approved by: implicit, since this is a build fix
math/py-numpy: switch to OpenBLAS by default
Besides being faster consistently using the same BLAS implementation
should improve stability in case of accidental ABI mismatch.
PR: 240937
Approved by: maintainer timeout (2 weeks)
MFH: 2019Q4
Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.
PR: 238330
Related to revision 499061 bump ports with USES=fortran to have them
benefit from the improved situation where libgcc_s is only used when
absolutely necessary.
Suggested by: tijl
Bump PORTREVISION for ports depending on the canonical version of GCC
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.
PR: 231590
Update to 1.15.1
- Change MASTER_SITES to CHEESESHOP
- Use bsd.port.mk instead of bsd.port.pre.mk + bsd.port.post.mk
Changes: https://github.com/numpy/numpy/releases
PR: 231664
Exp-run by: antoine
math/py-numpy: update to 1.15.0
- update to 1.15
- convert to autoplist
- follow upstream change from nose test framework to pytest
Release notes:
https://github.com/numpy/numpy/releases/tag/v1.15.0
PR: 230094
Submitted by: wen
Exp-run by: antoine
Bump PORTREVISION for ports depending on the canonical version of GCC
in the ports tree (via Mk/bsd.default-versions.mk and lang/gcc) which
has now moved from GCC 6 to GCC 7 by default.
This includes ports
- featuring USE_GCC=yes or USE_GCC=any,
- featuring USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and those
- with USES=compiler specifying one of openmp, nestedfct, c11, c++0x,
c++11-lib, c++11-lang, c++14-lang, c++17-lang, or gcc-c++11-lib.
PR: 222542
exec_command.py states in comments it uses /bin/sh on POSIX for subprocess but
incorrectly uses shell from environment. This makes compiles fail when
compilation is done using the account 'nobody' which is default on pkg-fallout
runs.
PR: ports/225156
Submitted by: self
Reported by: self
Reviewed by: antoine
Approved by: antoine
Enhance USES=uniquefiles to be more generic.
This allows to have more complex renaming schemes. Until now, it could
only add a prefix or a suffix, but this was not working at all for man
pages, because it would give man/man1/pyfoo.1.gz-2.7 or
man/man1/pyfoo-1-2.7.gz. With this change, a man page will be correctly
renamed to man/man1/pyfoo-2.7.1.gz.
Unfix ports that were already handling man pages.
PR: 220214
Submitted by: Fukang Chen (previous patch)
Exp-run by: antoine
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D13444
Convert Python ports to FLAVORS.
Ports using USE_PYTHON=distutils are now flavored. They will
automatically get flavors (py27, py34, py35, py36) depending on what
versions they support.
There is also a USE_PYTHON=flavors for ports that do not use distutils
but need FLAVORS to be set. A USE_PYTHON=noflavors can be set if
using distutils but flavors are not wanted.
A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been
added to cope with Python ports that did not have the Python
PKGNAMEPREFIX but are flavored.
USES=python now also exports a PY_FLAVOR variable that contains the
(Only the first 15 lines of the commit message are shown above )
Bump PORTREVISION for ports depending on the canonical version of GCC
(via Mk/bsd.default-versions.mk and lang/gcc) which has moved from
GCC 5.4 to GCC 6.4 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c++11-lib, c++11-lang,
c++14-lang, c++0x, c11, or gcc-c++11-lib.
PR: 219275
Number of commits found: 193 (showing only 100 on this page)
