CVE and update status of the FreeBSD ports tree3,864 unaddressed CVEs in 671 portsAll times are CET
Port details

devel/py-isoduration 20.11.0_1

Operations with ISO 8601 durations

Port info

Maintainer
sunpoet@FreeBSD.org
Packages
latest: 20.11.0_1
Upstream
up to date
Last update
to 20.11.0_1 · 8296a2d586
Quarterly
2026Q4: 20.11.0_1
WWW
https://github.com/bolsote/isoduration
Links
cgit · VuXML

Install

Package
# pkg install py312-isoduration
installs 20.11.0_1 from latest; from quarterly (2026Q4) 20.11.0_1
Port
# cd /usr/ports/devel/py-isoduration && make install clean
Size
20 KiB download · 75 KiB installed
Depends on
devel/py-arrow 1.4.0, lang/python312 3.12.15
License
ISCL

Packages by version and architecture

latest

FreeBSD versionamd64aarch64i386
FreeBSD 1620.11.0_120.11.0_1–
FreeBSD 1520.11.0_120.11.0_1–
FreeBSD 1420.11.0_120.11.0_120.11.0_1

quarterly (2026Q4)

FreeBSD versionamd64aarch64i386
FreeBSD 1520.11.0_120.11.0_1–
FreeBSD 1420.11.0_120.11.0_120.11.0_1

version as in the ports tree (latest) or the most common one (quarterly) · different version · ✗ not built · – no packages for this platform. Package sets that have not been rebuilt for 60 days are left out.

Unaddressed and VuXML only (0)

No unaddressed CVE and nothing reported by pkg audit for the packaged version 20.11.0_1.

Fixed (0)

No VuXML entries for this package.

Problem reports (0) · open in Bugzilla, most recently changed first

None.

Commits (3)

Po-Chuan Hsieh (sunpoet) · 20.11.0_1
devel/py-isoduration: Convert to USE_PYTHON=pep517

- Bump PORTREVISION for package change
8296a2d586
Rene Ladan (rene) · 20.11.0
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>
3d9a815d9c
Po-Chuan Hsieh (sunpoet) · 20.11.0
devel/py-isoduration: Add py-isoduration 20.11.0

ISO 8601 is most commonly known as a way to exchange datetimes in textual
format. A lesser known aspect of the standard is the representation of
durations. They have a shape similar to this:
    P3Y6M4DT12H30M5S
This string represents a duration of 3 years, 6 months, 4 days, 12 hours, 30
minutes, and 5 seconds.

The state of the art of ISO 8601 duration handling in Python is more or less
limited to what's offered by isodate. What we are trying to achieve here is to
address the shortcomings of isodate (as described in their own Limitations
section), and a few of our own annoyances with their interface, such as the lack
of uniformity in their handling of types, and the use of regular expressions for
parsing.
66e0f308ab