summaryrefslogtreecommitdiff
path: root/math/py-numarray
AgeCommit message (Collapse)AuthorFilesLines
2012-09-11"user-destdir" is default these daysasau1-3/+1
2012-05-07Set BUILDLINK_ABI_DEPENDS correctly (with +=, not ?=)dholland1-2/+2
It turns out there were a lot of these.
2012-04-08All supported python versions in pkgsrc support eggs, so removewiz1-2/+2
${PLIST.eggfile} from PLISTs and support code from lang/python.
2011-10-25register egg-info.obache2-5/+5
Bump PKGREVISION.
2009-06-14Remove @dirrm entries from PLISTsjoerg1-15/+1
2009-03-20Simply and speed up buildlink3.mk files and processing.joerg1-13/+6
This changes the buildlink3.mk files to use an include guard for the recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS, BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of enter/exit marker, which can be used to reconstruct the tree and to determine first level includes. Avoiding := for large variables (BUILDLINK_ORDER) speeds up parse time as += has linear complexity. The include guard reduces system time by avoiding reading files over and over again. For complex packages this reduces both %user and %sys time to half of the former time.
2009-03-20Include pyversion.mk include the protected part of the buildlink3.mkjoerg1-3/+3
files, not over and over again.
2008-06-12Add DESTDIR support.joerg1-1/+3
2008-04-25Update PYTHON_VERSIONS_COMPATIBLEjoerg1-2/+1
- assume that Python 2.4 and 2.5 are compatible and allow checking for fallout. - remove PYTHON_VERSIONS_COMPATIBLE that are obsoleted by the 2.3+ default. Modify the others to deal with the removals.
2008-04-12Convert to use PLIST_VARS instead of manually passing "@comment "jlam2-6/+5
through PLIST_SUBST to the plist module.
2006-10-17update to 1.5.2drochner2-7/+10
This is a very modest release which primarily consists of bug fixes to numarray's implementation of the numpy array interface.
2006-07-08Change the format of BUILDLINK_ORDER to contain depth information as well,jlam1-2/+2
and add a new helper target and script, "show-buildlink3", that outputs a listing of the buildlink3.mk files included as well as the depth at which they are included. For example, "make show-buildlink3" in fonts/Xft2 displays: zlib fontconfig iconv zlib freetype2 expat freetype2 Xrender renderproto
2006-07-08Track information in a new variable BUILDLINK_ORDER that informs usjlam1-1/+2
of the order in which buildlink3.mk files are (recursively) included by a package Makefile.
2006-04-12Aligned the last line of the buildlink3.mk files with the first line, sorillig1-2/+2
that they look nicer.
2006-04-06Over 1200 files touched but no revisions bumped :)reed1-3/+3
RECOMMENDED is removed. It becomes ABI_DEPENDS. BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo. BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo. BUILDLINK_DEPENDS does not change. IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS which defaults to "yes". Added to obsolete.mk checking for IGNORE_RECOMMENDED. I did not manually go through and fix any aesthetic tab/spacing issues. I have tested the above patch on DragonFly building and packaging subversion and pkglint and their many dependencies. I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I have used IGNORE_RECOMMENDED for a long time). I have been an active user of IGNORE_RECOMMENDED since it was available. As suggested, I removed the documentation sentences suggesting bumping for "security" issues. As discussed on tech-pkg. I will commit to revbump, pkglint, pkg_install, createbuildlink separately. Note that if you use wip, it will fail! I will commit to pkgsrc-wip later (within day).
2006-03-08Let the package find BLAS routines on Mac OS X. This makes the package buildminskim2-2/+10
on Darwin.
2006-03-04Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where nojlam1-2/+2
developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers.
2006-02-15update to 1.5.1drochner3-8/+11
changes: -fix a NumArray Operator Optimization Bug -Better NumPy dtype Support. -more bugfixes
2006-02-07update to 1.5drochner4-9/+26
changes: -better interoperability with py-Numeric and scipy (uses "scipy newcore") -bugfixes -speed improvements
2006-02-05Recursive revision bump / recommended bump for gettext ABI change.joerg2-2/+4
2005-10-25remove sitecustomize - this doesn't belong heredrochner1-2/+1
should fix bulk-build error
2005-10-21update to 1.3.3drochner3-17/+42
changes: -many bugfixes -code cleanup, speedup
2005-04-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv1-2/+1
2005-02-23Add RMD160 digests in addition to SHA1 ones.agc1-1/+2
2005-02-09Update py-numarray to version 1.1.1markd4-10/+14
Support Python 2.4 1.1.1 changes: numarray-1.1.1 is a bugfix release to numarray-1.1. Notable bugs fixed include memory leaks in matrixmultiply and comparison ufuncs. 1.1 changes: I. ENHANCEMENTS CharArray eval() sped up Document memmap.py (memory mapping) Unsigned int type support limited Add kroenecker product II. BUGS FIXED / CLOSED max.reduce of byteswapped array numeric compatibility byteoffset matrixmultiply (a,b) leaves b transposed random_array.randint exceeds boundaries buffer not aligned on 8 byte boundary (Windows-98 broken) Object Array repr for >1000 elements Invalid sequences errors Segfault in array element deletion Incorrect handling of overlapping assignments in Numarray Weirdness with 'new' method searchsorted bug and fix randint bug fix patch a.is_c_array() mixed int/bool results argsort of string arrays III. CAUTIONS 1. This release is binary incompatible with numarray-1.0. Writers of C-extensions which directly reference the byteoffset field of the PyArrayObject should be aware that the data pointer is now the sum of byteoffset and the buffer base pointer. All C extensions which use the numarray C-API must be recompiled. This incompatibility was an unfortunate consequence of the fix for "numeric compatibility byteoffset".
2005-01-23Build Python with thread support by default and turn the existingrecht1-2/+2
python*-pth packages into meta-packages which will install the non-pth packages. Bump PKGREVISIONs on the non-pth versions to propagate the thread change, but leave the *-pth versions untouched to not affect existing installations. Sync all PYTHON_VERSIONS_AFFECTED lines in package Makefiles.
2004-07-09update to 1.0recht3-12/+18
important changes: - Ports of Numeric functions A bunch of Numeric functions were ported to numarray in the new libnumeric module. To get these import from numarray.numeric. Most notable among these are put, putmask, take, argmin, and argmax. Also added were sort, argsort, concatenate, repeat and resize. These are independent ports/implementations in C done for the purpose of best Numeric compatibility and small array performance. The numarray versions, which handle additional cases, still exist and are the default in numarray proper. - Faster matrix multiply The setup for numarray's matrix multiply was moved into C-code. This makes it faster for small matrices. - bug fixes For a complete list of changes see: http://sourceforge.net/project/shownotes.php?release_id=250453
2004-04-22add onedrochner1-0/+20
2004-04-21import the numarray-0.9 Python extension - a reimplemantation ofdrochner4-0/+292
py-Numeric
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-22 09:20:33 +0000