| Port details |
- py-flexparser Parsing made fun ... using typing
- 0.4 devel
 =0      Package not present on quarterly.This port was created during this quarter. It will be in the next quarterly branch but not the current one. - Maintainer: sunpoet@FreeBSD.org
- Port Added: 2026-05-21 15:06:11
- Last Update: 2026-05-21 14:45:42
- Commit Hash: 01e754c
- Also Listed In: python
- License: BSD3CLAUSE
- WWW:
- https://github.com/hgrecco/flexparser
- Description:
- Why write another parser? I have asked myself the same question while working on
this project. It is clear that there are excellent parsers out there, but I
wanted to experiment with another way of writing them.
The idea is quite simple. You write a class for every type of content (called
here ParsedStatement) you need to parse. Each class should have a from_string
constructor. We used the typing module extensively to make the output structure
easy to use and less error-prone.
  ¦  ¦  ¦  ¦ 
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - There is no configure plist information for this port.
- USE_RC_SUBR (Service Scripts)
- no SUBR information found for this port
- Dependency lines:
-
- ${PYTHON_PKGNAMEPREFIX}flexparser>0:devel/py-flexparser@${PY_FLAVOR}
- To install the port:
- cd /usr/ports/devel/py-flexparser/ && make install clean
- To add the package, run one of these commands:
- pkg install devel/py-flexparser
- pkg install py311-flexparser
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above.
NOTE: This is a Python port. Instead of py311-flexparser listed in the above command, you can pick from the names under the Packages section.- PKGNAME: py311-flexparser
- Package flavors (<flavor>: <package>)
- distinfo:
- TIMESTAMP = 1779222882
SHA256 (flexparser-0.4.tar.gz) = 266d98905595be2ccc5da964fe0a2c3526fbbffdc45b65b3146d75db992ef6b2
SIZE (flexparser-0.4.tar.gz) = 31799
Packages (timestamps in pop-ups are UTC):
- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Build dependencies:
-
- py311-setuptools>=61 : devel/py-setuptools@py311
- py311-setuptools-scm>=3.4.3 : devel/py-setuptools-scm@py311
- py311-wheel>=0 : devel/py-wheel@py311
- python3.11 : lang/python311
- py311-build>=0 : devel/py-build@py311
- py311-installer>=0 : devel/py-installer@py311
- Test dependencies:
-
- python3.11 : lang/python311
- Runtime dependencies:
-
- py311-typing-extensions>=0 : devel/py-typing-extensions@py311
- python3.11 : lang/python311
- This port is required by:
- for Run
-
- devel/py-datasette
- devel/py-pint
Configuration Options:- No options to configure
- Options name:
- devel_py-flexparser
- USES:
- python
- FreshPorts was unable to extract/find any pkg message
- Master Sites:
|
Number of commits found: 1
| Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
| Commit | Credits | Log message |
|---|
0.4
21 May 2026 14:45:42
 |
Po-Chuan Hsieh (sunpoet) |
devel/py-flexparser: Add py-flexparser 0.4
Why write another parser? I have asked myself the same question while working on
this project. It is clear that there are excellent parsers out there, but I
wanted to experiment with another way of writing them.
The idea is quite simple. You write a class for every type of content (called
here ParsedStatement) you need to parse. Each class should have a from_string
constructor. We used the typing module extensively to make the output structure
easy to use and less error-prone. |
Number of commits found: 1
|
As an Amazon Associate I earn from qualifying purchases.