devel/py-requirements-detector: Update to 1.6.0 Changes: https://github.com/prospector-dev/requirements-detector/commits/master22879ca8c0
Port details
devel/py-requirements-detector 1.6.0
Find and list requirements of a Python project
Port info
- Maintainer
- sunpoet@FreeBSD.org
- Packages
- latest: 1.6.0
- Upstream
- up to date
- Last update
- to 1.6.0 · 22879ca8c0
- Quarterly
- 2026Q4: 1.6.0
- WWW
- https://github.com/prospector-dev/requirements-detector
- Links
- cgit · VuXML
Install
- Package
# pkg install py312-requirements-detectorinstalls 1.6.0 fromlatest; fromquarterly(2026Q4) 1.6.0- Port
# cd /usr/ports/devel/py-requirements-detector && make install clean- Size
- 46 KiB download · 221 KiB installed
- Depends on
- devel/py-astroid 4.1.2, devel/py-packaging 26.3, devel/py-semver 3.1.0, lang/python312 3.12.15
- License
- MIT
Packages by version and architecture
latest
| FreeBSD version | amd64 | aarch64 | i386 |
|---|---|---|---|
| FreeBSD 16 | 1.6.0 | 1.6.0 | – |
| FreeBSD 15 | 1.6.0 | 1.6.0 | – |
| FreeBSD 14 | 1.6.0 | 1.6.0 | 1.6.0 |
quarterly (2026Q4)
| FreeBSD version | amd64 | aarch64 | i386 |
|---|---|---|---|
| FreeBSD 15 | 1.6.0 | 1.6.0 | – |
| FreeBSD 14 | 1.6.0 | 1.6.0 | 1.6.0 |
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 1.6.0.Fixed (0)
No VuXML entries for this package.
Problem reports (0) · open in Bugzilla, most recently changed first
None.
Commits (11)
devel/py-requirements-detector: Update to 1.5.0 Changes: https://github.com/prospector-dev/requirements-detector/commits/masterd7a9df05d5
devel/py-requirements-detector: Allow build with py-astroid 4.0.0+ - Bump PORTREVISION for package change597087d2c4
devel/py-requirements-detector: Update to 1.4.0 Changes: https://github.com/prospector-dev/requirements-detector/commits/master0790761898
devel/py-requirements-detector: Update to 1.3.2 Changes: https://github.com/prospector-dev/requirements-detector/commits/master6d316a8292
devel/py-requirements-detector: Update to 1.3.1 - Update WWW Changes: https://github.com/prospector-dev/requirements-detector/commits/master23dde5ff50
devel/py-requirements-detector: Allow build with py-astroid 3.* - Bump PORTREVISION for package changefba609184f
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-requirements-detector: Update to 1.2.2 Changes: https://github.com/landscapeio/requirements-detector/commits/mastera9bfe775eb
devel/py-requirements-detector: Update to 1.2.1 Changes: https://github.com/landscapeio/requirements-detector/commits/master50e53d3367
devel/py-requirements-detector: Add py-requirements-detector 1.1.0
Requirements Detector is a simple Python tool which attempts to find and list
the requirements of a Python project.
When run from the root of a Python project, it will try to ascertain which
libraries and the versions of those libraries that the project depends on.
It uses the following methods in order, in the root of the project:
1. Parse setup.py (if this is successful, the remaining steps are skipped)
2. Parse pyproject.yoml (if a tool.poetry.dependencies section is found, the
remaining steps are skipped)
3. Parse requirements.txt or requirements.pip
4. Parse all *.txt and *.pip files inside a folder called requirements
5. Parse all files in the root folder matching *requirements*.txt or reqs.txt
(so for example, pip_requirements.txt would match, as would
requirements_common.txt)d17af72d4f