devel/py-importlib-metadata: Update version 9.0.1=>9.1.0 Changelog: https://github.com/python/importlib_metadata/releases/tag/v9.1.02b8f0b7c53
Port details
devel/py-importlib-metadata9.0.1
Read metadata from Python packages
- Maintainer
- bofh@FreeBSD.org
- Packages
- py312-importlib-metadata 9.0.1
- Upstream
- Higher version available: 10.1.0
- CPE
- none, CVEs only via VuXML
- WWW
- https://github.com/python/importlib_metadata
- Links
- cgit · VuXML
Unaddressed (0) · The CVE record lists this version as affected, no VuXML entry names the CVE
None. There is no CVE without a VuXML entry for this version.
VuXML only (0) · listed, port not fixed yet
None.
pkg audit reports nothing for this version.Fixed (0)
No VuXML entries for this package.
Commits (58)
devel/py-importlib-metadata: Update version 9.0.0=>9.0.1 Changelog: https://github.com/python/importlib_metadata/releases/tag/v9.0.16b1866b8dd
devel/py-importlib-metadata: Update version 8.9.0=>9.0.0 Changelog: https://github.com/python/importlib_metadata/releases/tag/v9.0.00764ec4708
devel/py-importlib-metadata: Update version 8.8.0=>8.9.0 Changelog: https://github.com/python/importlib_metadata/releases/tag/v8.9.02388792e97
devel/py-importlib-metadata: Update version 8.7.1=>8.8.0 Changelog: https://github.com/python/importlib_metadata/releases/tag/v8.8.0ad27741439
devel/py-importlib-metadata: Update version 8.7.0=>8.7.1 Changelog: https://github.com/python/importlib_metadata/releases/tag/v8.7.1b964d07922
devel/py-importlib-metadata: Update version 8.6.1=>8.7.0 Changelog: https://github.com/python/importlib_metadata/releases/tag/v8.7.0f4750b690b
devel/py-importlib-metadata: Update version 8.6.0=>8.6.1 Changelog: https://github.com/python/importlib_metadata/releases/tag/v8.6.1316da0b990
devel/py-importlib-metadata: Update version 8.5.0=>8.6.0 Changelog: https://github.com/python/importlib_metadata/releases/tag/v8.6.04201b5c896
devel/py-importlib-metadata: Update version 8.4.0 => 8.5.0 Changelog: https://github.com/python/importlib_metadata/releases/tag/v8.5.00062358458
devel/py-importlib-metadata: Update version 8.3.0=>8.4.0 Changelog: https://github.com/python/importlib_metadata/releases/tag/v8.4.0d374b2932c
devel/py-importlib-metadata: Update version 8.2.0=>8.3.0 Changelog: https://github.com/python/importlib_metadata/releases/tag/v8.3.0902a72a314
devel/py-importlib-metadata: Update version 8.1.0=>8.2.0 Changelog: https://github.com/python/importlib_metadata/releases/tag/v8.2.00334fba7b6
devel/py-importlib-metadata: Update version 8.0.0=>8.1.0 Changelog: https://github.com/python/importlib_metadata/releases/tag/v8.1.0267ace101c
devel/py-importlib-metadata: Update version 7.2.1=>8.0.0 In case any of the consumers are broken with the new major version please use the previous major version devel/py-importlib-metadata7 Changelog: https://github.com/python/importlib_metadata/releases/tag/v8.0.000e79413e1
devel/py-importlib-metadata: Update version 7.2.0=>7.2.1 Changelog: https://github.com/python/importlib_metadata/releases/tag/v7.2.12ebbec92e7
devel/py-importlib-metadata: Update version 7.1.0=>7.2.0 Changelog: https://github.com/python/importlib_metadata/releases/tag/v7.2.0c2f351e0f6
devel/py-importlib-metadata: Update version 7.0.2=>7.1.0 Changelog: https://github.com/python/importlib_metadata/releases/tag/v7.1.0ad265d230d
*: Mark TESTING_UNSAFE1328b38bfb
devel/py-importlib-metadata: Update version 7.0.1=>7.0.2 Changelog: https://github.com/python/importlib_metadata/releases/tag/v7.0.202c83e380b
devel/py-setuptools-scm: update to 8.0.4
Directory and PORTNAME changed to match normalised name in release
tarball; consumers updated to match.
Although setuptools itself is specified as a run dependency in the
Python package metadata, it is currently left out here to prevent
environment pollution until at least PR 270510 is committed.
Additionally, this version of setuptools-scm requires setuptools>=61,
which means this version is only meant for USE_PYTHON=pep517 ports
as all USE_PYTHON=distutils ports will switch to devel/py-setuptools58
also after PR 270510. science/py-emmet-core is switched to
devel/py-setuptools_scm7 accordingly, as it specifies setuptools-scm<8.
devel/py-{flit-scm,hatch-vcs} have ${PY_SETUPTOOLS} added to
RUN_DEPENDS to compensate.
Further details: https://wiki.freebsd.org/Python/setuptools
Reported by: yuri
Co-authored by: matthew
Exp-run by: antoine (earlier iteration)
Approved by: yuri (science/py-emmet-core, previous iteration)
PR: 272134
Differential Revision: https://reviews.freebsd.org/D392885d4139f8bddevel/py-importlib-metadata: Update version 7.0.0=>7.0.1 Changelog: https://github.com/python/importlib_metadata/releases/tag/v7.0.133b96dca2e
devel/py-importlib-metadata: Update version 6.8.0=>7.0.0 Changelog: https://github.com/python/importlib_metadata/releases/tag/v7.0.0659be85740
devel/py-setuptools: convert individual consumers to ${PY_SETUPTOOLS}
Currently a no-op, but in the future outputs the correct setuptools
port depending on whether USES_PYTHON=distutils is specified.
With hat: python
PR: 270510, 2703589a80a6ee5edevel/py-importlib-metadata: Update version 6.7.0=>6.8.0 Changelog: https://github.com/python/importlib_metadata/releases/tag/v6.8.0e8fb223838
devel/py-importlib-metadata: Utilize USE_PYTHON=pep517 Reported by: vishwin092d07b918
devel/py-importlib-metadata: Update version 6.6.0=>6.7.0 Changelog: https://github.com/python/importlib_metadata/releases/tag/v6.7.0f2f3efc265
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>3d9a815d9cdevel/py-importlib-metadata: Update version 6.4.1=>6.6.0 Changelog: https://github.com/python/importlib_metadata/releases/tag/v6.6.0902f44345e
devel/py-importlib-metadata: Update version 6.3.0=>6.4.1 Changelog: https://github.com/python/importlib_metadata/releases/tag/v6.4.16aaac4b3d4
devel/py-importlib-metadata: Update version 6.0.0=>6.3.0 Changelog: https://github.com/python/importlib_metadata/releases/tag/v6.3.0e0097b98a1
*/*: Adopt ports from swills@2c2dd85355
all: return swills' ports to the pools after safeeping his ports bit. With hat: portmgr-secretary4f538db960
USE_PYTHON=pep517: bump PORTREVISION1730e97e04
devel/py-importlib-metadata: Fix circular dependency problem ... introduced by USE_PYTHON=pep517. PR: 269363 Reported by: John Hein <jcfyecrayz@liamekaens.com>d6583d67b6
devel/py-importlib-metadata: add explicit setuptools BUILD_DEPENDS Per PEP-518 [0], for projects using setuptools as the build backend, both setuptools and wheel are to be specified, as wheel is a plugin for setuptools to support the format at all. Additionally, wheel itself will soon [1] not depend on setuptools, but rather the dependency tree will reverse. With hat: python Approved by: mentors (implicit), swills (maintainer, implicit) References: https://peps.python.org/pep-0518/#build-system-table [0] https://github.com/pypa/wheel/pull/501 [1]471747153a
Revert "Mk/Uses/python.mk: Fix USE_PYTHON=pep517: always compile and install bytecode" Despite installer's default behaviour to compile and install bytecode, we are not doing so going forward at stage/package time. [0] During initial development and qualification of PEP-517 framework support, compiling and installing bytecode at stage/package time was considered, but was found problematic, fragile and ultimately unreliable, both currently and historically (with USE_PYTHON=distutils), due to our fixed plist requirement. While the living binary distribution format (wheel) specification [1] says to compile bytecode, that is in the pure Python package management context (pip, etc); nuance always exists when interacting with "system" package management. Additionally, "bytecode is an implementation detail of the CPython interpreter. No guarantees are made that bytecode will not be added, removed, or changed between versions of Python," thus "should not be considered to work across Python VMs or Python releases." [2] This is important to ensuring correctness for those ports specifying NO_ARCH. Instead of compiling and installing bytecode at stage/package time, there is a WIP, review D34739, that compiles and installs bytecode at install time instead, using triggers. The aforementioned build_fs_violations will be investigated. This reverts commit de6965254c3a007efcf697c3d455b54d2aeb2383. With hat: python Approved by: tcberner (mentor, portmgr) Reference: https://wiki.freebsd.org/Python/PEP-517 [0] https://packaging.python.org/en/latest/specifications/binary-distribution-format/ [1] https://docs.python.org/3/library/dis.html [2]f5890bd3cb
Mk/Uses/python.mk: Fix USE_PYTHON=pep517: always compile and install bytecode
- While I'm here, use long options for easier reading [1][2]
- Bump PORTREVISION of dependent ports (USE_PYTHON=pep517) for package change
It fixes build_fs_violation of dependent ports in poudriere (with -t flag).
It is also the default behavior of installer [2].
from py-sphinx log:
=>> Checking for staging violations... done
=>> Error: Filesystem touched during stage (files must install to ${STAGEDIR}):
extra: usr/local/lib/python3.9/site-packages/importlib_metadata/__pycache__
=>> Cleaning up wrkdir
from installer documentation:
--compile-bytecode
Possible choices: 0, 1, 2
generate bytecode for the specified optimization level(s) (default=0, 1)
--no-compile-bytecode
don’t generate bytecode for installed modules
Default: False
With hat: python
Reference: https://pypa-build.readthedocs.io/en/stable/ [1]
https://installer.pypa.io/en/stable/cli/installer/ [2]de6965254cdevel/py-importlib-metadata: Update 4.8.1 → 6.0.0 Remove upper limitation on version in devel/py-poetry because it doesn't change tests outcome. This unbreaks devel/py-jupyterlab and also opens path for several other ports that depend on the newest devel/py-importlib-metadata versions. PR: 269125 Approved by: portmgr (unbreak devel/py-jupyterlab)89168e9675
*/*: rename CHEESESHOP to PYPI in MASTER_SITES PR: 267994 Differential revision: D37518 Approved by: bapt77d68471ad
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)fb16dfecae
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. This commit implements such a proposal and moves one of the WWW: entries of each pkg-descr file into the respective port's Makefile. A heuristic attempts to identify the most relevant URL in case there is more than one WWW: entry in some pkg-descr file. URLs that are not moved into the Makefile are prefixed with "See also:" instead of "WWW:" in the pkg-descr files in order to preserve them. There are 1256 ports that had no WWW: entries in pkg-descr files. These ports will not be touched in this commit. The portlint port has been adjusted to expect a WWW entry in each port Makefile, and to flag any remaining "WWW:" lines in pkg-descr files as deprecated. Approved by: portmgr (tcberner)b7f05445c0
devel/py-importlib-metadata: update to 4.8.103c761c56b
devel/py-importlib-metadata: Update WWW Approved by: portmgr (blanket)07f5023b0e
devel/py-importlib-metadata: Add NO_ARCH Approved by: portmgr (blanket)dcec01f018
devel/py-importlib-metadata: update to 4.7.1 PR: 255237 Reported by: yuri3cda2f536f
Mk: switch PYTHON_REL to 5 digits to support python 3.10.x PR: 255013 Differential Revision: https://reviews.freebsd.org/D29418 Exp-run by: antoine Approved by: wen@, no objection from python@ or portmgr@0729af4255
One more small cleanup, forgotten yesterday. Reported by: lwhsucf118ccf87
Remove # $FreeBSD$ from Makefiles.305f148f48
devel/py-importlib-metadata: Fix RUN_DEPENDS for Python < 3.8
* Python < 3.8 also needs devel/py-typing-extensions for runtime.
* Bump PORTREVISION due changed dependencies.
Approved by: portmgr ("just fix it")32d5fa9388