waccy-edgar
WACCY extension for SEC EDGAR filing parsing and pattern learning.
Status
This package provides fixture-first EDGAR/XBRL-shaped extraction, deterministic SEC companyfacts normalization, and the entry point for ExtractorRegistry discovery. Live SEC fetching is still kept separate from fixture normalization. The v0.1.0 work is tracked in:
- #6 Implement EDGAR extraction for comparable three-statement source data
- #14 Decide and implement EDGAR pattern-learning scope for v0.1.0
- v0.1.0 milestone
Installation
uv pip install waccy-edgar
Or install with the core platform:
uv pip install "waccy[edgar]"
Current Usage
from waccy.extraction import ExtractorRegistry
registry = ExtractorRegistry()
extractor = registry.get_extractor("edgar")()
print(extractor.name)
Companyfacts JSON can be normalized into WACCY fixture records before extraction:
from waccy_edgar import EdgarCompanyFactsNormalizer, EdgarExtractor
fixture = EdgarCompanyFactsNormalizer().to_fixture(companyfacts_json)
extracted = EdgarExtractor().extract({"fixture": fixture})
The normalizer selects annual 10-K facts, preserves fiscal-year and instant-fact provenance, emits FYyyyy periods, and carries partial-extraction diagnostics in fixture metadata.
Development
This package is part of the WACCY monorepo. See the main README for development setup.
Metadata
Release files for waccy-edgar 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| waccy_edgar-0.1.0.tar.gz | 5.9 kB | Without provenance | Details for waccy_edgar-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| waccy_edgar-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for waccy_edgar-0.1.0-py3-none-any.whl |
Total release size: 12.4 kB
Release files / waccy_edgar-0.1.0.tar.gz
| Download URL | waccy_edgar-0.1.0.tar.gz |
|---|---|
| Size | 5.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cf9387a93de76910133535866509ae018cf6e9a1d9843a8c6c4e8ac8b8b7a5c4
|
|
BLAKE2b-256 checksum How to use checksums |
0c56f0b2a75542565b9e6725a86f59e201e8e84c7a47f35b295dd3bbdfc21cbd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.11.13 {"installer":{"name":"uv","version":"0.11.13","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / waccy_edgar-0.1.0-py3-none-any.whl
| Download URL | waccy_edgar-0.1.0-py3-none-any.whl |
|---|---|
| Size | 6.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6bee3b8b4aee39422cfb1b27f567f30c485ead3e216dfc4f9dfd0d7a8970befb
|
|
BLAKE2b-256 checksum How to use checksums |
9fbb8ab89fdae2436f4c5cd335c2489399c9faa00a3d603353a0a645e8a7087e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.11.13 {"installer":{"name":"uv","version":"0.11.13","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for waccy-edgar 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.