Kafka-based components for Scrapy, to allow Spider`s to read their next URL from a Kafka topic and an `ItemPipeline to store the JSON-ified Item back into a Kafka topic.
Please see the example directory for how to use this.
Contributors
Contributors to scrapy-kafka, listed alphabetically:
1 maintainer
Metadata
1 maintainer
Release files for scrapy-kafka 0.1.1
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 | |
|---|---|---|---|---|
| scrapy-kafka-0.1.1.tar.gz | 3.2 kB | Without provenance | Details |
Release files / scrapy-kafka-0.1.1.tar.gz
| Download URL | scrapy-kafka-0.1.1.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f18074c9eead57aef65a391645df3eae3026762c8eb6269987b9541bab287072
|
|
BLAKE2b-256 checksum How to use checksums |
aa0084390c023e9604b9f499c85f0d48bc63a8a963ecec55bcfe96e215a276ca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for scrapy-kafka 0.1.1
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.
