Updated Fink Packages (Stable)
http://pdb.finkproject.org/pdb/
Updated Packages Released to the Stable Tree in the Last 5 Days.en-us2024-03-18T22:00:03-05:00fink-devel@lists.sourceforge.netfink-devel@lists.sourceforge.netFink Software2000-01-01T00:30:00-05:001hourlylibraw20-dev-0.20.2-3 (RAW library developer files)
http://pdb.finkproject.org/pdb/package.php/libraw20-dev?distribution=10.9-libcxx&version=0.20.2&revision=3
LibRaw is a library for reading RAW files obtained from digital photo
cameras (CRW/CR2, NEF, RAF, DNG, and others).
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
libraw20: bump jasper]]>2024-03-17T18:00:04-05:00coverage-py36-5.5-1 (Python code coverage for testing)
http://pdb.finkproject.org/pdb/package.php/coverage-py36?distribution=10.9-libcxx&version=5.5&revision=1
Coverage.py measures code coverage, typically during test
execution. It uses the code analysis tools and tracing hooks provided
in the Python standard library to determine which lines are
executable, and which have been executed.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
coverage-py: v7.4.4 for 38-310 and earlier releases for older py]]>2024-03-17T18:00:04-05:00libjasper1-bin-1.900.1-debian1-2.4+deb8u6-2 (OBSOLETE: use jasper-bin)
http://pdb.finkproject.org/pdb/package.php/libjasper1-bin?distribution=10.9-libcxx&version=1.900.1-debian1-2.4+deb8u6&revision=2
The JasPer Project is an open-source initiative to provide a free
software-based reference implementation of the codec specified in the
JPEG-2000 Part-1 standard (i.e., ISO/IEC 15444-1).
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
libjasper.1: mirror ancient tarballs in SF so they don't get lost.]]>2024-03-17T18:00:04-05:00coverage-py37-7.2.7-1 (Python code coverage for testing)
http://pdb.finkproject.org/pdb/package.php/coverage-py37?distribution=10.9-libcxx&version=7.2.7&revision=1
Coverage.py measures code coverage, typically during test
execution. It uses the code analysis tools and tracing hooks provided
in the Python standard library to determine which lines are
executable, and which have been executed.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
coverage-py: v7.4.4 for 38-310 and earlier releases for older py]]>2024-03-17T18:00:04-05:00libraw-bin-0.20.2-3 (Executables for libraw20 package)
http://pdb.finkproject.org/pdb/package.php/libraw-bin?distribution=10.9-libcxx&version=0.20.2&revision=3
LibRaw is a library for reading RAW files obtained from digital photo
cameras (CRW/CR2, NEF, RAF, DNG, and others).
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
libraw20: bump jasper]]>2024-03-17T18:00:04-05:00jasper-bin-1.900.1-debian1-2.4+deb8u6-2 (Library for manipulating JPEG-2000 images)
http://pdb.finkproject.org/pdb/package.php/jasper-bin?distribution=10.9-libcxx&version=1.900.1-debian1-2.4+deb8u6&revision=2
The JasPer Project is an open-source initiative to provide a free
software-based reference implementation of the codec specified in the
JPEG-2000 Part-1 standard (i.e., ISO/IEC 15444-1).
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
libjasper.1: mirror ancient tarballs in SF so they don't get lost.]]>2024-03-17T18:00:04-05:00gdl-1.0.4-2 (GNU Data Language)
http://pdb.finkproject.org/pdb/package.php/gdl?distribution=10.9-libcxx&version=1.0.4&revision=2&epoch=1
GDL is a free IDL (Interactive Data Language) compatible incremental
compiler. It features a full syntax compatibility with IDL
6.0. Overall more than 330 library routines are implemented.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
gdl: v1.0.4]]>2024-03-17T18:00:04-05:00eccodes-2.34.1-1 (Coding/encoding ECMWF files, C headers/docs)
http://pdb.finkproject.org/pdb/package.php/eccodes?distribution=10.9-libcxx&version=2.34.1&revision=1
ecCodes is a package developed by ECMWF which provides an application
programming interface and a set of tools for decoding and encoding messages
in the following formats:
- WMO FM-92 GRIB edition 1 and edition 2
- WMO FM-94 BUFR edition 3 and edition 4
- WMO GTS abbreviated header (only decoding).
A useful set of command line tools provide quick access to the messages. C,
Fortran 90 and Python interfaces provide access to the main ecCodes
functionality. ecCodes is an evolution of GRIB-API. It is designed to provide
the user with a simple set of functions to access data from several formats
with a key/value approach. For GRIB encoding and decoding, the GRIB-API
functionality is provided fully in ecCodes with only minor interface and
behaviour changes. Interfaces for C, Fortran 90 and Python are all maintained
as in GRIB-API. However, the GRIB-API Fortran 77 interface is no longer
available.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
eccodes: v2.34.1]]>2024-03-17T18:00:04-05:00coverage-py35-5.5-1 (Python code coverage for testing)
http://pdb.finkproject.org/pdb/package.php/coverage-py35?distribution=10.9-libcxx&version=5.5&revision=1
Coverage.py measures code coverage, typically during test
execution. It uses the code analysis tools and tracing hooks provided
in the Python standard library to determine which lines are
executable, and which have been executed.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
coverage-py: v7.4.4 for 38-310 and earlier releases for older py]]>2024-03-17T18:00:04-05:00coverage-py27-5.5-1 (Python code coverage for testing)
http://pdb.finkproject.org/pdb/package.php/coverage-py27?distribution=10.9-libcxx&version=5.5&revision=1
Coverage.py measures code coverage, typically during test
execution. It uses the code analysis tools and tracing hooks provided
in the Python standard library to determine which lines are
executable, and which have been executed.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
coverage-py: v7.4.4 for 38-310 and earlier releases for older py]]>2024-03-17T18:00:04-05:00coverage-py38-7.4.4-1 (Python code coverage for testing)
http://pdb.finkproject.org/pdb/package.php/coverage-py38?distribution=10.9-libcxx&version=7.4.4&revision=1
Coverage.py measures code coverage, typically during test
execution. It uses the code analysis tools and tracing hooks provided
in the Python standard library to determine which lines are
executable, and which have been executed.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
coverage-py: v7.4.4 for 38-310 and earlier releases for older py]]>2024-03-17T18:00:04-05:00libjasper.1-shlibs-1.900.1-debian1-2.4+deb8u6-2 (Library for manipulating JPEG-2000 images)
http://pdb.finkproject.org/pdb/package.php/libjasper.1-shlibs?distribution=10.9-libcxx&version=1.900.1-debian1-2.4+deb8u6&revision=2
The JasPer Project is an open-source initiative to provide a free
software-based reference implementation of the codec specified in the
JPEG-2000 Part-1 standard (i.e., ISO/IEC 15444-1).
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
libjasper.1: mirror ancient tarballs in SF so they don't get lost.]]>2024-03-17T18:00:04-05:00eccodes-shlibs-2.34.1-1 (Coding/decoding ECMWF files, C library)
http://pdb.finkproject.org/pdb/package.php/eccodes-shlibs?distribution=10.9-libcxx&version=2.34.1&revision=1
ecCodes is a package developed by ECMWF which provides an application
programming interface and a set of tools for decoding and encoding messages
in the following formats:
- WMO FM-92 GRIB edition 1 and edition 2
- WMO FM-94 BUFR edition 3 and edition 4
- WMO GTS abbreviated header (only decoding).
A useful set of command line tools provide quick access to the messages. C,
Fortran 90 and Python interfaces provide access to the main ecCodes
functionality. ecCodes is an evolution of GRIB-API. It is designed to provide
the user with a simple set of functions to access data from several formats
with a key/value approach. For GRIB encoding and decoding, the GRIB-API
functionality is provided fully in ecCodes with only minor interface and
behaviour changes. Interfaces for C, Fortran 90 and Python are all maintained
as in GRIB-API. However, the GRIB-API Fortran 77 interface is no longer
available.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
eccodes: v2.34.1]]>2024-03-17T18:00:04-05:00libraw20-shlibs-0.20.2-3 (RAW image format library)
http://pdb.finkproject.org/pdb/package.php/libraw20-shlibs?distribution=10.9-libcxx&version=0.20.2&revision=3
LibRaw is a library for reading RAW files obtained from digital photo
cameras (CRW/CR2, NEF, RAF, DNG, and others).
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
libraw20: bump jasper]]>2024-03-17T18:00:04-05:00coverage-py39-7.4.4-1 (Python code coverage for testing)
http://pdb.finkproject.org/pdb/package.php/coverage-py39?distribution=10.9-libcxx&version=7.4.4&revision=1
Coverage.py measures code coverage, typically during test
execution. It uses the code analysis tools and tracing hooks provided
in the Python standard library to determine which lines are
executable, and which have been executed.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
coverage-py: v7.4.4 for 38-310 and earlier releases for older py]]>2024-03-17T18:00:04-05:00ziproxy-3.3.2-1 (Non-caching compressing HTTP proxy)
http://pdb.finkproject.org/pdb/package.php/ziproxy?distribution=10.9-libcxx&version=3.3.2&revision=1
Non-caching compressing HTTP proxy
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
ziproxy: v3.3.2]]>2024-03-17T18:00:04-05:00eccodes-bin-2.34.1-1 (Coding/decoding ECMWF files, user programs)
http://pdb.finkproject.org/pdb/package.php/eccodes-bin?distribution=10.9-libcxx&version=2.34.1&revision=1
ecCodes is a package developed by ECMWF which provides an application
programming interface and a set of tools for decoding and encoding messages
in the following formats:
- WMO FM-92 GRIB edition 1 and edition 2
- WMO FM-94 BUFR edition 3 and edition 4
- WMO GTS abbreviated header (only decoding).
A useful set of command line tools provide quick access to the messages. C,
Fortran 90 and Python interfaces provide access to the main ecCodes
functionality. ecCodes is an evolution of GRIB-API. It is designed to provide
the user with a simple set of functions to access data from several formats
with a key/value approach. For GRIB encoding and decoding, the GRIB-API
functionality is provided fully in ecCodes with only minor interface and
behaviour changes. Interfaces for C, Fortran 90 and Python are all maintained
as in GRIB-API. However, the GRIB-API Fortran 77 interface is no longer
available.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
eccodes: v2.34.1]]>2024-03-17T18:00:04-05:00jiv-1.900.1-debian1-2.4+deb8u6-2 (OBSOLETE: use jasper-bin)
http://pdb.finkproject.org/pdb/package.php/jiv?distribution=10.9-libcxx&version=1.900.1-debian1-2.4+deb8u6&revision=2
The JasPer Project is an open-source initiative to provide a free
software-based reference implementation of the codec specified in the
JPEG-2000 Part-1 standard (i.e., ISO/IEC 15444-1).
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
libjasper.1: mirror ancient tarballs in SF so they don't get lost.]]>2024-03-17T18:00:04-05:00eccodes-fortran-2.34.1-1 (Coding/decoding ECMWF files, Fortran headers)
http://pdb.finkproject.org/pdb/package.php/eccodes-fortran?distribution=10.9-libcxx&version=2.34.1&revision=1
ecCodes is a package developed by ECMWF which provides an application
programming interface and a set of tools for decoding and encoding messages
in the following formats:
- WMO FM-92 GRIB edition 1 and edition 2
- WMO FM-94 BUFR edition 3 and edition 4
- WMO GTS abbreviated header (only decoding).
A useful set of command line tools provide quick access to the messages. C,
Fortran 90 and Python interfaces provide access to the main ecCodes
functionality. ecCodes is an evolution of GRIB-API. It is designed to provide
the user with a simple set of functions to access data from several formats
with a key/value approach. For GRIB encoding and decoding, the GRIB-API
functionality is provided fully in ecCodes with only minor interface and
behaviour changes. Interfaces for C, Fortran 90 and Python are all maintained
as in GRIB-API. However, the GRIB-API Fortran 77 interface is no longer
available.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
eccodes: v2.34.1]]>2024-03-17T18:00:04-05:00libjasper.1-1.900.1-debian1-2.4+deb8u6-2 (Library for manipulating JPEG-2000 images)
http://pdb.finkproject.org/pdb/package.php/libjasper.1?distribution=10.9-libcxx&version=1.900.1-debian1-2.4+deb8u6&revision=2
The JasPer Project is an open-source initiative to provide a free
software-based reference implementation of the codec specified in the
JPEG-2000 Part-1 standard (i.e., ISO/IEC 15444-1).
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
libjasper.1: mirror ancient tarballs in SF so they don't get lost.]]>2024-03-17T18:00:04-05:00eccodes-fortran-shlibs-2.34.1-1 (Coding/decoding ECMWF files, Fortran library)
http://pdb.finkproject.org/pdb/package.php/eccodes-fortran-shlibs?distribution=10.9-libcxx&version=2.34.1&revision=1
ecCodes is a package developed by ECMWF which provides an application
programming interface and a set of tools for decoding and encoding messages
in the following formats:
- WMO FM-92 GRIB edition 1 and edition 2
- WMO FM-94 BUFR edition 3 and edition 4
- WMO GTS abbreviated header (only decoding).
A useful set of command line tools provide quick access to the messages. C,
Fortran 90 and Python interfaces provide access to the main ecCodes
functionality. ecCodes is an evolution of GRIB-API. It is designed to provide
the user with a simple set of functions to access data from several formats
with a key/value approach. For GRIB encoding and decoding, the GRIB-API
functionality is provided fully in ecCodes with only minor interface and
behaviour changes. Interfaces for C, Fortran 90 and Python are all maintained
as in GRIB-API. However, the GRIB-API Fortran 77 interface is no longer
available.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
eccodes: v2.34.1]]>2024-03-17T18:00:04-05:00coverage-py310-7.4.4-1 (Python code coverage for testing)
http://pdb.finkproject.org/pdb/package.php/coverage-py310?distribution=10.9-libcxx&version=7.4.4&revision=1
Coverage.py measures code coverage, typically during test
execution. It uses the code analysis tools and tracing hooks provided
in the Python standard library to determine which lines are
executable, and which have been executed.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
coverage-py: v7.4.4 for 38-310 and earlier releases for older py]]>2024-03-17T18:00:04-05:00guile20-2.0.14-6 (Embedable Scheme interpreter)
http://pdb.finkproject.org/pdb/package.php/guile20?distribution=10.9-libcxx&version=2.0.14&revision=6
Embedable Scheme interpreter
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
guile2*: don't error out with incompatible function pointer types via Xcode 15
The issue only happens in a single file tests/, so just override the failure rather than try to fix it since upstream doesn't have anything about it.]]>2024-03-16T22:00:04-05:00guile22-2.2.7-6 (Embedable Scheme interpreter)
http://pdb.finkproject.org/pdb/package.php/guile22?distribution=10.9-libcxx&version=2.2.7&revision=6
Embedable Scheme interpreter
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
guile2*: don't error out with incompatible function pointer types via Xcode 15
The issue only happens in a single file tests/, so just override the failure rather than try to fix it since upstream doesn't have anything about it.]]>2024-03-16T22:00:04-05:00guile20-libs-2.0.14-6 (Scheme libraries and modules for guile20)
http://pdb.finkproject.org/pdb/package.php/guile20-libs?distribution=10.9-libcxx&version=2.0.14&revision=6
Scheme libraries and modules for guile20
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
guile2*: don't error out with incompatible function pointer types via Xcode 15
The issue only happens in a single file tests/, so just override the failure rather than try to fix it since upstream doesn't have anything about it.]]>2024-03-16T22:00:04-05:00guile22-libs-2.2.7-6 (Scheme libraries and modules for guile22)
http://pdb.finkproject.org/pdb/package.php/guile22-libs?distribution=10.9-libcxx&version=2.2.7&revision=6
Scheme libraries and modules for guile22
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
guile2*: don't error out with incompatible function pointer types via Xcode 15
The issue only happens in a single file tests/, so just override the failure rather than try to fix it since upstream doesn't have anything about it.]]>2024-03-16T22:00:04-05:00guile22-doc-2.2.7-6 (Texinfo files for guile22)
http://pdb.finkproject.org/pdb/package.php/guile22-doc?distribution=10.9-libcxx&version=2.2.7&revision=6
Texinfo files for guile22
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
guile2*: don't error out with incompatible function pointer types via Xcode 15
The issue only happens in a single file tests/, so just override the failure rather than try to fix it since upstream doesn't have anything about it.]]>2024-03-16T22:00:04-05:00guile20-doc-2.0.14-6 (Texinfo files for guile20)
http://pdb.finkproject.org/pdb/package.php/guile20-doc?distribution=10.9-libcxx&version=2.0.14&revision=6
Texinfo files for guile20
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
guile2*: don't error out with incompatible function pointer types via Xcode 15
The issue only happens in a single file tests/, so just override the failure rather than try to fix it since upstream doesn't have anything about it.]]>2024-03-16T22:00:04-05:00guile20-shlibs-2.0.14-6 (Shared libraries for guile20)
http://pdb.finkproject.org/pdb/package.php/guile20-shlibs?distribution=10.9-libcxx&version=2.0.14&revision=6
Shared libraries for guile20
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
guile2*: don't error out with incompatible function pointer types via Xcode 15
The issue only happens in a single file tests/, so just override the failure rather than try to fix it since upstream doesn't have anything about it.]]>2024-03-16T22:00:04-05:00guile22-shlibs-2.2.7-6 (Shared libraries for guile22)
http://pdb.finkproject.org/pdb/package.php/guile22-shlibs?distribution=10.9-libcxx&version=2.2.7&revision=6
Shared libraries for guile22
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
guile2*: don't error out with incompatible function pointer types via Xcode 15
The issue only happens in a single file tests/, so just override the failure rather than try to fix it since upstream doesn't have anything about it.]]>2024-03-16T22:00:04-05:00guile20-dev-2.0.14-6 (Development package for guile20)
http://pdb.finkproject.org/pdb/package.php/guile20-dev?distribution=10.9-libcxx&version=2.0.14&revision=6
Development package for guile20
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
guile2*: don't error out with incompatible function pointer types via Xcode 15
The issue only happens in a single file tests/, so just override the failure rather than try to fix it since upstream doesn't have anything about it.]]>2024-03-16T22:00:04-05:00guile22-dev-2.2.7-6 (Development package for guile22)
http://pdb.finkproject.org/pdb/package.php/guile22-dev?distribution=10.9-libcxx&version=2.2.7&revision=6
Development package for guile22
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
guile2*: don't error out with incompatible function pointer types via Xcode 15
The issue only happens in a single file tests/, so just override the failure rather than try to fix it since upstream doesn't have anything about it.]]>2024-03-16T22:00:04-05:00graphicsmagick1322-q32-shlibs-1.3.42-1 (Swiss army knife of image processing)
http://pdb.finkproject.org/pdb/package.php/graphicsmagick1322-q32-shlibs?distribution=10.9-libcxx&version=1.3.42&revision=1&epoch=1
GraphicsMagick is the swiss army knife of image processing. Comprised
of 337K lines of C and C++ code, it provides a robust and efficient
collection of tools and libraries which support reading, writing, and
manipulating an image in over 88 major formats including important
formats like DPX, GIF, JPEG, JPEG-2000, PNG, PDF, PNM, and TIFF.
GraphicsMagick supports huge images on systems that support large
files, and has been tested with gigapixel-size images. GraphicsMagick
can create new images on the fly, making it suitable for building
dynamic Web applications. GraphicsMagick may be used to resize, rotate,
sharpen, color reduce, or add special effects to an image and save the
result in the same or differing image format. Image processing
operations are available from the command line, as well as through C,
C++, Perl, Tcl, Ruby, or Windows COM programming interfaces. With some
modification, language extensions for ImageMagick may be used.
GraphicsMagick is originally derived from ImageMagick 5.5.2 but has
been completely independent of the ImageMagick project since then.
Since the fork from ImageMagick in 2002, many improvements have been
made (see news) by many authors using an open development model but
without breaking the API or utilities operation.
This package is built --with-quantum-depth=32. It will be slower and
use twice as much memory as "graphicsmagick" which is built
--with-quantum-depth=16. The higher bit-depth should only be needed for
scientific applications needing the highest accuracy. Quantum 16 is
fine for most uses and is the most optimized.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
graphicksmagick v1.3.42]]>2024-03-16T22:00:03-05:00graphicsmagick-imagemagick-compat-1.3.42-1 (ImageMagick compatible wrapper commands)
http://pdb.finkproject.org/pdb/package.php/graphicsmagick-imagemagick-compat?distribution=10.9-libcxx&version=1.3.42&revision=1&epoch=1
GraphicsMagick is the swiss army knife of image processing. Comprised
of 337K lines of C and C++ code, it provides a robust and efficient
collection of tools and libraries which support reading, writing, and
manipulating an image in over 88 major formats including important
formats like DPX, GIF, JPEG, JPEG-2000, PNG, PDF, PNM, and TIFF.
GraphicsMagick supports huge images on systems that support large
files, and has been tested with gigapixel-size images. GraphicsMagick
can create new images on the fly, making it suitable for building
dynamic Web applications. GraphicsMagick may be used to resize, rotate,
sharpen, color reduce, or add special effects to an image and save the
result in the same or differing image format. Image processing
operations are available from the command line, as well as through C,
C++, Perl, Tcl, Ruby, or Windows COM programming interfaces. With some
modification, language extensions for ImageMagick may be used.
GraphicsMagick is originally derived from ImageMagick 5.5.2 but has
been completely independent of the ImageMagick project since then.
Since the fork from ImageMagick in 2002, many improvements have been
made (see news) by many authors using an open development model but
without breaking the API or utilities operation.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
graphicksmagick v1.3.42]]>2024-03-16T22:00:03-05:00graphicsmagick-q32-1.3.42-1 (Swiss army knife of image processing)
http://pdb.finkproject.org/pdb/package.php/graphicsmagick-q32?distribution=10.9-libcxx&version=1.3.42&revision=1&epoch=1
GraphicsMagick is the swiss army knife of image processing. Comprised
of 337K lines of C and C++ code, it provides a robust and efficient
collection of tools and libraries which support reading, writing, and
manipulating an image in over 88 major formats including important
formats like DPX, GIF, JPEG, JPEG-2000, PNG, PDF, PNM, and TIFF.
GraphicsMagick supports huge images on systems that support large
files, and has been tested with gigapixel-size images. GraphicsMagick
can create new images on the fly, making it suitable for building
dynamic Web applications. GraphicsMagick may be used to resize, rotate,
sharpen, color reduce, or add special effects to an image and save the
result in the same or differing image format. Image processing
operations are available from the command line, as well as through C,
C++, Perl, Tcl, Ruby, or Windows COM programming interfaces. With some
modification, language extensions for ImageMagick may be used.
GraphicsMagick is originally derived from ImageMagick 5.5.2 but has
been completely independent of the ImageMagick project since then.
Since the fork from ImageMagick in 2002, many improvements have been
made (see news) by many authors using an open development model but
without breaking the API or utilities operation.
This package is built --with-quantum-depth=32. It will be slower and
use twice as much memory as "graphicsmagick" which is built
--with-quantum-depth=16. The higher bit-depth should only be needed for
scientific applications needing the highest accuracy. Quantum 16 is
fine for most uses and is the most optimized.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
graphicksmagick v1.3.42]]>2024-03-16T22:00:03-05:00graphicsmagick1322-q32-dev-1.3.42-1 (Swiss army knife of image processing)
http://pdb.finkproject.org/pdb/package.php/graphicsmagick1322-q32-dev?distribution=10.9-libcxx&version=1.3.42&revision=1&epoch=1
GraphicsMagick is the swiss army knife of image processing. Comprised
of 337K lines of C and C++ code, it provides a robust and efficient
collection of tools and libraries which support reading, writing, and
manipulating an image in over 88 major formats including important
formats like DPX, GIF, JPEG, JPEG-2000, PNG, PDF, PNM, and TIFF.
GraphicsMagick supports huge images on systems that support large
files, and has been tested with gigapixel-size images. GraphicsMagick
can create new images on the fly, making it suitable for building
dynamic Web applications. GraphicsMagick may be used to resize, rotate,
sharpen, color reduce, or add special effects to an image and save the
result in the same or differing image format. Image processing
operations are available from the command line, as well as through C,
C++, Perl, Tcl, Ruby, or Windows COM programming interfaces. With some
modification, language extensions for ImageMagick may be used.
GraphicsMagick is originally derived from ImageMagick 5.5.2 but has
been completely independent of the ImageMagick project since then.
Since the fork from ImageMagick in 2002, many improvements have been
made (see news) by many authors using an open development model but
without breaking the API or utilities operation.
This package is built --with-quantum-depth=32. It will be slower and
use twice as much memory as "graphicsmagick" which is built
--with-quantum-depth=16. The higher bit-depth should only be needed for
scientific applications needing the highest accuracy. Quantum 16 is
fine for most uses and is the most optimized.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
graphicksmagick v1.3.42]]>2024-03-16T22:00:03-05:00graphicsmagick1322-shlibs-1.3.42-1 (Swiss army knife of image processing)
http://pdb.finkproject.org/pdb/package.php/graphicsmagick1322-shlibs?distribution=10.9-libcxx&version=1.3.42&revision=1&epoch=1
GraphicsMagick is the swiss army knife of image processing. Comprised
of 337K lines of C and C++ code, it provides a robust and efficient
collection of tools and libraries which support reading, writing, and
manipulating an image in over 88 major formats including important
formats like DPX, GIF, JPEG, JPEG-2000, PNG, PDF, PNM, and TIFF.
GraphicsMagick supports huge images on systems that support large
files, and has been tested with gigapixel-size images. GraphicsMagick
can create new images on the fly, making it suitable for building
dynamic Web applications. GraphicsMagick may be used to resize, rotate,
sharpen, color reduce, or add special effects to an image and save the
result in the same or differing image format. Image processing
operations are available from the command line, as well as through C,
C++, Perl, Tcl, Ruby, or Windows COM programming interfaces. With some
modification, language extensions for ImageMagick may be used.
GraphicsMagick is originally derived from ImageMagick 5.5.2 but has
been completely independent of the ImageMagick project since then.
Since the fork from ImageMagick in 2002, many improvements have been
made (see news) by many authors using an open development model but
without breaking the API or utilities operation.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
graphicksmagick v1.3.42]]>2024-03-16T22:00:03-05:00graphicsmagick-1.3.42-1 (Swiss army knife of image processing)
http://pdb.finkproject.org/pdb/package.php/graphicsmagick?distribution=10.9-libcxx&version=1.3.42&revision=1&epoch=1
GraphicsMagick is the swiss army knife of image processing. Comprised
of 337K lines of C and C++ code, it provides a robust and efficient
collection of tools and libraries which support reading, writing, and
manipulating an image in over 88 major formats including important
formats like DPX, GIF, JPEG, JPEG-2000, PNG, PDF, PNM, and TIFF.
GraphicsMagick supports huge images on systems that support large
files, and has been tested with gigapixel-size images. GraphicsMagick
can create new images on the fly, making it suitable for building
dynamic Web applications. GraphicsMagick may be used to resize, rotate,
sharpen, color reduce, or add special effects to an image and save the
result in the same or differing image format. Image processing
operations are available from the command line, as well as through C,
C++, Perl, Tcl, Ruby, or Windows COM programming interfaces. With some
modification, language extensions for ImageMagick may be used.
GraphicsMagick is originally derived from ImageMagick 5.5.2 but has
been completely independent of the ImageMagick project since then.
Since the fork from ImageMagick in 2002, many improvements have been
made (see news) by many authors using an open development model but
without breaking the API or utilities operation.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
graphicksmagick v1.3.42]]>2024-03-16T22:00:03-05:00graphicsmagick1322-dev-1.3.42-1 (Swiss army knife of image processing)
http://pdb.finkproject.org/pdb/package.php/graphicsmagick1322-dev?distribution=10.9-libcxx&version=1.3.42&revision=1&epoch=1
GraphicsMagick is the swiss army knife of image processing. Comprised
of 337K lines of C and C++ code, it provides a robust and efficient
collection of tools and libraries which support reading, writing, and
manipulating an image in over 88 major formats including important
formats like DPX, GIF, JPEG, JPEG-2000, PNG, PDF, PNM, and TIFF.
GraphicsMagick supports huge images on systems that support large
files, and has been tested with gigapixel-size images. GraphicsMagick
can create new images on the fly, making it suitable for building
dynamic Web applications. GraphicsMagick may be used to resize, rotate,
sharpen, color reduce, or add special effects to an image and save the
result in the same or differing image format. Image processing
operations are available from the command line, as well as through C,
C++, Perl, Tcl, Ruby, or Windows COM programming interfaces. With some
modification, language extensions for ImageMagick may be used.
GraphicsMagick is originally derived from ImageMagick 5.5.2 but has
been completely independent of the ImageMagick project since then.
Since the fork from ImageMagick in 2002, many improvements have been
made (see news) by many authors using an open development model but
without breaking the API or utilities operation.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
graphicksmagick v1.3.42]]>2024-03-16T22:00:03-05:00libjasper7-4.2.2-1 (Library for manipulating JPEG-2000 images)
http://pdb.finkproject.org/pdb/package.php/libjasper7?distribution=10.9-libcxx&version=4.2.2&revision=1
The JasPer Project is an open-source initiative to provide a free
software-based reference implementation of the codec specified in the
JPEG-2000 Part-1 standard (i.e., ISO/IEC 15444-1).
commit log from Daniel Macks (dmacks@netspace.org):
libjasper: new upstream (new libN)]]>2024-03-16T14:00:03-05:00libjasper7-shlibs-4.2.2-1 (Library for manipulating JPEG-2000 images)
http://pdb.finkproject.org/pdb/package.php/libjasper7-shlibs?distribution=10.9-libcxx&version=4.2.2&revision=1
The JasPer Project is an open-source initiative to provide a free
software-based reference implementation of the codec specified in the
JPEG-2000 Part-1 standard (i.e., ISO/IEC 15444-1).
commit log from Daniel Macks (dmacks@netspace.org):
libjasper: new upstream (new libN)]]>2024-03-16T14:00:03-05:00lxml-py35-5.0.1-1 (Binding for the libxml2 and libxslt)
http://pdb.finkproject.org/pdb/package.php/lxml-py35?distribution=10.9-libcxx&version=5.0.1&revision=1
The C libraries libxml2 and libxslt have huge benefits:
* Standards-compliant XML support.
* Full-featured. (e.g. supports XPath)
* Actively maintained by XML experts.
* fast
lxml is a new Python binding for libxml2 and libxslt, completely
independent from these existing Python bindings. Its aim:
* Pythonic API.
* Documented.
* Use Python unicode strings in API.
* Safe (no segfaults).
* No manual memory management!
lxml aims to provide a Pythonic API by following as much as possible
the ElementTree API. We're trying to avoid having to invent too many
new APIs, or you having to learn new things -- XML is complicated
enough.
commit log from Daniel Macks (dmacks@netspace.org):
lxml-py: latest version available for each variant
Misc libxml and expat fixes
NB: -py34 still fails some self-tests related to libxml2; obviously
have some upstream patches available, but hard to cherry-pick for this
ancient version. I have no idea if these are test-bugs or actual
library bugs.]]>2024-03-16T12:00:06-05:00lxml-py39-5.1.0-1 (Binding for the libxml2 and libxslt)
http://pdb.finkproject.org/pdb/package.php/lxml-py39?distribution=10.9-libcxx&version=5.1.0&revision=1
The C libraries libxml2 and libxslt have huge benefits:
* Standards-compliant XML support.
* Full-featured. (e.g. supports XPath)
* Actively maintained by XML experts.
* fast
lxml is a new Python binding for libxml2 and libxslt, completely
independent from these existing Python bindings. Its aim:
* Pythonic API.
* Documented.
* Use Python unicode strings in API.
* Safe (no segfaults).
* No manual memory management!
lxml aims to provide a Pythonic API by following as much as possible
the ElementTree API. We're trying to avoid having to invent too many
new APIs, or you having to learn new things -- XML is complicated
enough.
commit log from Daniel Macks (dmacks@netspace.org):
lxml-py: latest version available for each variant
Misc libxml and expat fixes
NB: -py34 still fails some self-tests related to libxml2; obviously
have some upstream patches available, but hard to cherry-pick for this
ancient version. I have no idea if these are test-bugs or actual
library bugs.]]>2024-03-16T12:00:06-05:00lxml-py27-5.0.1-1 (Binding for the libxml2 and libxslt)
http://pdb.finkproject.org/pdb/package.php/lxml-py27?distribution=10.9-libcxx&version=5.0.1&revision=1
The C libraries libxml2 and libxslt have huge benefits:
* Standards-compliant XML support.
* Full-featured. (e.g. supports XPath)
* Actively maintained by XML experts.
* fast
lxml is a new Python binding for libxml2 and libxslt, completely
independent from these existing Python bindings. Its aim:
* Pythonic API.
* Documented.
* Use Python unicode strings in API.
* Safe (no segfaults).
* No manual memory management!
lxml aims to provide a Pythonic API by following as much as possible
the ElementTree API. We're trying to avoid having to invent too many
new APIs, or you having to learn new things -- XML is complicated
enough.
commit log from Daniel Macks (dmacks@netspace.org):
lxml-py: latest version available for each variant
Misc libxml and expat fixes
NB: -py34 still fails some self-tests related to libxml2; obviously
have some upstream patches available, but hard to cherry-pick for this
ancient version. I have no idea if these are test-bugs or actual
library bugs.]]>2024-03-16T12:00:06-05:00lxml-py34-4.3.5-1 (Binding for the libxml2 and libxslt)
http://pdb.finkproject.org/pdb/package.php/lxml-py34?distribution=10.9-libcxx&version=4.3.5&revision=1
The C libraries libxml2 and libxslt have huge benefits:
* Standards-compliant XML support.
* Full-featured. (e.g. supports XPath)
* Actively maintained by XML experts.
* fast
lxml is a new Python binding for libxml2 and libxslt, completely
independent from these existing Python bindings. Its aim:
* Pythonic API.
* Documented.
* Use Python unicode strings in API.
* Safe (no segfaults).
* No manual memory management!
lxml aims to provide a Pythonic API by following as much as possible
the ElementTree API. We're trying to avoid having to invent too many
new APIs, or you having to learn new things -- XML is complicated
enough.
commit log from Daniel Macks (dmacks@netspace.org):
lxml-py: latest version available for each variant
Misc libxml and expat fixes
NB: -py34 still fails some self-tests related to libxml2; obviously
have some upstream patches available, but hard to cherry-pick for this
ancient version. I have no idea if these are test-bugs or actual
library bugs.]]>2024-03-16T12:00:06-05:00lxml-py37-5.1.0-1 (Binding for the libxml2 and libxslt)
http://pdb.finkproject.org/pdb/package.php/lxml-py37?distribution=10.9-libcxx&version=5.1.0&revision=1
The C libraries libxml2 and libxslt have huge benefits:
* Standards-compliant XML support.
* Full-featured. (e.g. supports XPath)
* Actively maintained by XML experts.
* fast
lxml is a new Python binding for libxml2 and libxslt, completely
independent from these existing Python bindings. Its aim:
* Pythonic API.
* Documented.
* Use Python unicode strings in API.
* Safe (no segfaults).
* No manual memory management!
lxml aims to provide a Pythonic API by following as much as possible
the ElementTree API. We're trying to avoid having to invent too many
new APIs, or you having to learn new things -- XML is complicated
enough.
commit log from Daniel Macks (dmacks@netspace.org):
lxml-py: latest version available for each variant
Misc libxml and expat fixes
NB: -py34 still fails some self-tests related to libxml2; obviously
have some upstream patches available, but hard to cherry-pick for this
ancient version. I have no idea if these are test-bugs or actual
library bugs.]]>2024-03-16T12:00:06-05:00lxml-py38-5.1.0-1 (Binding for the libxml2 and libxslt)
http://pdb.finkproject.org/pdb/package.php/lxml-py38?distribution=10.9-libcxx&version=5.1.0&revision=1
The C libraries libxml2 and libxslt have huge benefits:
* Standards-compliant XML support.
* Full-featured. (e.g. supports XPath)
* Actively maintained by XML experts.
* fast
lxml is a new Python binding for libxml2 and libxslt, completely
independent from these existing Python bindings. Its aim:
* Pythonic API.
* Documented.
* Use Python unicode strings in API.
* Safe (no segfaults).
* No manual memory management!
lxml aims to provide a Pythonic API by following as much as possible
the ElementTree API. We're trying to avoid having to invent too many
new APIs, or you having to learn new things -- XML is complicated
enough.
commit log from Daniel Macks (dmacks@netspace.org):
lxml-py: latest version available for each variant
Misc libxml and expat fixes
NB: -py34 still fails some self-tests related to libxml2; obviously
have some upstream patches available, but hard to cherry-pick for this
ancient version. I have no idea if these are test-bugs or actual
library bugs.]]>2024-03-16T12:00:06-05:00lxml-py310-5.1.0-1 (Binding for the libxml2 and libxslt)
http://pdb.finkproject.org/pdb/package.php/lxml-py310?distribution=10.9-libcxx&version=5.1.0&revision=1
The C libraries libxml2 and libxslt have huge benefits:
* Standards-compliant XML support.
* Full-featured. (e.g. supports XPath)
* Actively maintained by XML experts.
* fast
lxml is a new Python binding for libxml2 and libxslt, completely
independent from these existing Python bindings. Its aim:
* Pythonic API.
* Documented.
* Use Python unicode strings in API.
* Safe (no segfaults).
* No manual memory management!
lxml aims to provide a Pythonic API by following as much as possible
the ElementTree API. We're trying to avoid having to invent too many
new APIs, or you having to learn new things -- XML is complicated
enough.
commit log from Daniel Macks (dmacks@netspace.org):
lxml-py: latest version available for each variant
Misc libxml and expat fixes
NB: -py34 still fails some self-tests related to libxml2; obviously
have some upstream patches available, but hard to cherry-pick for this
ancient version. I have no idea if these are test-bugs or actual
library bugs.]]>2024-03-16T12:00:06-05:00lxml-py36-5.1.0-1 (Binding for the libxml2 and libxslt)
http://pdb.finkproject.org/pdb/package.php/lxml-py36?distribution=10.9-libcxx&version=5.1.0&revision=1
The C libraries libxml2 and libxslt have huge benefits:
* Standards-compliant XML support.
* Full-featured. (e.g. supports XPath)
* Actively maintained by XML experts.
* fast
lxml is a new Python binding for libxml2 and libxslt, completely
independent from these existing Python bindings. Its aim:
* Pythonic API.
* Documented.
* Use Python unicode strings in API.
* Safe (no segfaults).
* No manual memory management!
lxml aims to provide a Pythonic API by following as much as possible
the ElementTree API. We're trying to avoid having to invent too many
new APIs, or you having to learn new things -- XML is complicated
enough.
commit log from Daniel Macks (dmacks@netspace.org):
lxml-py: latest version available for each variant
Misc libxml and expat fixes
NB: -py34 still fails some self-tests related to libxml2; obviously
have some upstream patches available, but hard to cherry-pick for this
ancient version. I have no idea if these are test-bugs or actual
library bugs.]]>2024-03-16T12:00:06-05:00pytest-mock-py36-1.10.4-1 (Thin-wrapper around the mock package)
http://pdb.finkproject.org/pdb/package.php/pytest-mock-py36?distribution=10.9-libcxx&version=1.10.4&revision=1
This plugin installs a mocker fixture which is a thin-wrapper around the
patching API provided by the mock package, but with the benefit of not
having to worry about undoing patches at the end of a test.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
pytest-mock-py: v3.12.0 and other earlier versions for lower pythons]]>2024-03-16T05:00:07-05:00pytest-mock-py27-1.10.4-1 (Thin-wrapper around the mock package)
http://pdb.finkproject.org/pdb/package.php/pytest-mock-py27?distribution=10.9-libcxx&version=1.10.4&revision=1
This plugin installs a mocker fixture which is a thin-wrapper around the
patching API provided by the mock package, but with the benefit of not
having to worry about undoing patches at the end of a test.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
pytest-mock-py: v3.12.0 and other earlier versions for lower pythons]]>2024-03-16T05:00:07-05:00pytest-mock-py39-3.12.0-1 (Thin-wrapper around the mock package)
http://pdb.finkproject.org/pdb/package.php/pytest-mock-py39?distribution=10.9-libcxx&version=3.12.0&revision=1
This plugin installs a mocker fixture which is a thin-wrapper around the
patching API provided by the mock package, but with the benefit of not
having to worry about undoing patches at the end of a test.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
pytest-mock-py: v3.12.0 and other earlier versions for lower pythons]]>2024-03-16T05:00:07-05:00pytest-mock-py35-1.10.4-1 (Thin-wrapper around the mock package)
http://pdb.finkproject.org/pdb/package.php/pytest-mock-py35?distribution=10.9-libcxx&version=1.10.4&revision=1
This plugin installs a mocker fixture which is a thin-wrapper around the
patching API provided by the mock package, but with the benefit of not
having to worry about undoing patches at the end of a test.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
pytest-mock-py: v3.12.0 and other earlier versions for lower pythons]]>2024-03-16T05:00:07-05:00sed-4.9-1 (The stream editor, GNU version)
http://pdb.finkproject.org/pdb/package.php/sed?distribution=10.9-libcxx&version=4.9&revision=1
Sed is a text stream editor that is commonly used
to process text from shell scripts and makefiles.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
sed 4.9]]>2024-03-16T05:00:07-05:00pytest-mock-py310-3.12.0-1 (Thin-wrapper around the mock package)
http://pdb.finkproject.org/pdb/package.php/pytest-mock-py310?distribution=10.9-libcxx&version=3.12.0&revision=1
This plugin installs a mocker fixture which is a thin-wrapper around the
patching API provided by the mock package, but with the benefit of not
having to worry about undoing patches at the end of a test.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
pytest-mock-py: v3.12.0 and other earlier versions for lower pythons]]>2024-03-16T05:00:07-05:00pytest-mock-py37-1.10.4-1 (Thin-wrapper around the mock package)
http://pdb.finkproject.org/pdb/package.php/pytest-mock-py37?distribution=10.9-libcxx&version=1.10.4&revision=1
This plugin installs a mocker fixture which is a thin-wrapper around the
patching API provided by the mock package, but with the benefit of not
having to worry about undoing patches at the end of a test.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
pytest-mock-py: v3.12.0 and other earlier versions for lower pythons]]>2024-03-16T05:00:07-05:00pytest-mock-py38-3.12.0-1 (Thin-wrapper around the mock package)
http://pdb.finkproject.org/pdb/package.php/pytest-mock-py38?distribution=10.9-libcxx&version=3.12.0&revision=1
This plugin installs a mocker fixture which is a thin-wrapper around the
patching API provided by the mock package, but with the benefit of not
having to worry about undoing patches at the end of a test.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
pytest-mock-py: v3.12.0 and other earlier versions for lower pythons]]>2024-03-16T05:00:07-05:00pytest-mock-py34-1.10.4-1 (Thin-wrapper around the mock package)
http://pdb.finkproject.org/pdb/package.php/pytest-mock-py34?distribution=10.9-libcxx&version=1.10.4&revision=1
This plugin installs a mocker fixture which is a thin-wrapper around the
patching API provided by the mock package, but with the benefit of not
having to worry about undoing patches at the end of a test.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
pytest-mock-py: v3.12.0 and other earlier versions for lower pythons]]>2024-03-16T05:00:07-05:00pytest-py36-6.2.5-3 (Cross-project testing tool for Python)
http://pdb.finkproject.org/pdb/package.php/pytest-py36?distribution=10.9-libcxx&version=6.2.5&revision=3
py.test is a command line tool to collect, run and report about
automated tests. It runs well on Linux, Windows and OSX and on many
versions of Python. It is used in many projects, ranging from
running 10 thousands of tests to a few inlined tests on a command line
script. You can also generate a no-dependency
py.test-equivalent standalone script that you can distribute along with
your application.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
preserve pytest-6.2.5 for py36]]>2024-03-15T05:00:07-05:00xmlschema-py38-3.0.1-1 (XML Schema validator and decoder)
http://pdb.finkproject.org/pdb/package.php/xmlschema-py38?distribution=10.9-libcxx&version=3.0.1&revision=1
This library arises from the needs of a solid Python layer for
processing XML Schema based files for MaX (Materials design at the
Exascale) European project. A significant problem is the encoding and
the decoding of the XML data files produced by different simulation
software. Another important requirement is the XML data validation, in
order to put the produced data under control. The lack of a suitable
alternative for Python in the schema-based decoding of XML data has led
to build this library. Obviously this library can be useful for other
cases related to XML Schema based processing, not only for the original
scope.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
xmlschema for py37]]>2024-03-15T05:00:07-05:00xmlschema-py37-2.5.1-1 (XML Schema validator and decoder)
http://pdb.finkproject.org/pdb/package.php/xmlschema-py37?distribution=10.9-libcxx&version=2.5.1&revision=1
This library arises from the needs of a solid Python layer for
processing XML Schema based files for MaX (Materials design at the
Exascale) European project. A significant problem is the encoding and
the decoding of the XML data files produced by different simulation
software. Another important requirement is the XML data validation, in
order to put the produced data under control. The lack of a suitable
alternative for Python in the schema-based decoding of XML data has led
to build this library. Obviously this library can be useful for other
cases related to XML Schema based processing, not only for the original
scope.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
xmlschema for py37]]>2024-03-15T05:00:07-05:00pytest-py39-7.4.4-1 (Cross-project testing tool for Python)
http://pdb.finkproject.org/pdb/package.php/pytest-py39?distribution=10.9-libcxx&version=7.4.4&revision=1
py.test is a command line tool to collect, run and report about
automated tests. It runs well on Linux, Windows and OSX and on many
versions of Python. It is used in many projects, ranging from
running 10 thousands of tests to a few inlined tests on a command line
script. You can also generate a no-dependency
py.test-equivalent standalone script that you can distribute along with
your application.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
pytest-py: v7.4.4]]>2024-03-15T05:00:07-05:00xmlschema-py310-3.0.1-1 (XML Schema validator and decoder)
http://pdb.finkproject.org/pdb/package.php/xmlschema-py310?distribution=10.9-libcxx&version=3.0.1&revision=1
This library arises from the needs of a solid Python layer for
processing XML Schema based files for MaX (Materials design at the
Exascale) European project. A significant problem is the encoding and
the decoding of the XML data files produced by different simulation
software. Another important requirement is the XML data validation, in
order to put the produced data under control. The lack of a suitable
alternative for Python in the schema-based decoding of XML data has led
to build this library. Obviously this library can be useful for other
cases related to XML Schema based processing, not only for the original
scope.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
xmlschema for py37]]>2024-03-15T05:00:07-05:00pytest-py310-7.4.4-1 (Cross-project testing tool for Python)
http://pdb.finkproject.org/pdb/package.php/pytest-py310?distribution=10.9-libcxx&version=7.4.4&revision=1
py.test is a command line tool to collect, run and report about
automated tests. It runs well on Linux, Windows and OSX and on many
versions of Python. It is used in many projects, ranging from
running 10 thousands of tests to a few inlined tests on a command line
script. You can also generate a no-dependency
py.test-equivalent standalone script that you can distribute along with
your application.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
pytest-py: v7.4.4]]>2024-03-15T05:00:07-05:00pytest-py37-7.4.4-1 (Cross-project testing tool for Python)
http://pdb.finkproject.org/pdb/package.php/pytest-py37?distribution=10.9-libcxx&version=7.4.4&revision=1
py.test is a command line tool to collect, run and report about
automated tests. It runs well on Linux, Windows and OSX and on many
versions of Python. It is used in many projects, ranging from
running 10 thousands of tests to a few inlined tests on a command line
script. You can also generate a no-dependency
py.test-equivalent standalone script that you can distribute along with
your application.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
pytest-py: v7.4.4]]>2024-03-15T05:00:07-05:00xmlschema-py39-3.0.1-1 (XML Schema validator and decoder)
http://pdb.finkproject.org/pdb/package.php/xmlschema-py39?distribution=10.9-libcxx&version=3.0.1&revision=1
This library arises from the needs of a solid Python layer for
processing XML Schema based files for MaX (Materials design at the
Exascale) European project. A significant problem is the encoding and
the decoding of the XML data files produced by different simulation
software. Another important requirement is the XML data validation, in
order to put the produced data under control. The lack of a suitable
alternative for Python in the schema-based decoding of XML data has led
to build this library. Obviously this library can be useful for other
cases related to XML Schema based processing, not only for the original
scope.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
xmlschema for py37]]>2024-03-15T05:00:07-05:00pytest-py38-7.4.4-1 (Cross-project testing tool for Python)
http://pdb.finkproject.org/pdb/package.php/pytest-py38?distribution=10.9-libcxx&version=7.4.4&revision=1
py.test is a command line tool to collect, run and report about
automated tests. It runs well on Linux, Windows and OSX and on many
versions of Python. It is used in many projects, ranging from
running 10 thousands of tests to a few inlined tests on a command line
script. You can also generate a no-dependency
py.test-equivalent standalone script that you can distribute along with
your application.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
pytest-py: v7.4.4]]>2024-03-15T05:00:07-05:00libcroco3-shlibs-0.6.12-1 (CSS parsing and manipulation library)
http://pdb.finkproject.org/pdb/package.php/libcroco3-shlibs?distribution=10.9-libcxx&version=0.6.12&revision=1
The Libcroco project is an effort to build a generic Cascading
Style Sheet (CSS) parsing and manipulation toolkit that can be
used by GNOME applications in need of CSS support.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
libcroc3: implicit-function-declaration fix]]>2024-03-14T05:00:05-05:00libcroco3-0.6.12-1 (CSS parsing and manipulation library)
http://pdb.finkproject.org/pdb/package.php/libcroco3?distribution=10.9-libcxx&version=0.6.12&revision=1
The Libcroco project is an effort to build a generic Cascading
Style Sheet (CSS) parsing and manipulation toolkit that can be
used by GNOME applications in need of CSS support.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
libcroc3: implicit-function-declaration fix]]>2024-03-14T05:00:05-05:00libcroco3-bin-0.6.12-1 (CSS parsing and manipulation library)
http://pdb.finkproject.org/pdb/package.php/libcroco3-bin?distribution=10.9-libcxx&version=0.6.12&revision=1
The Libcroco project is an effort to build a generic Cascading
Style Sheet (CSS) parsing and manipulation toolkit that can be
used by GNOME applications in need of CSS support.
commit log from Hanspeter Niederstrasser (nieder@users.sourceforge.net):
libcroc3: implicit-function-declaration fix]]>2024-03-14T05:00:05-05:00