This small module provides the means to consistently collect and process data from Twitter’s streaming API.
The authors of this module have no association with Twitter Inc., and offer no warranty or guarantee of continued interoperability with the services offered by Twitter Inc..
This module is licensed under a 3-clause BSD license:
Copyright (c) 2009-2010, Robert Escriva, Rensselaer Polytechnic Institute
All rights reserved.
Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
* Neither the name of this project nor the names of its contributors
may be used to endorse or promote products derived from this software
without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
If you’re simply looking to collect data, the quick and easy instructions are:
$ mkdir /path/to/twitter/data $ cd /path/to/twitter/data $ twittercollect --bzip2 \ > --user USERNAME \ > --password PASSWORD \ > --stream-url STREAM_URL
The process does not daemonize. It is recommended that it be run in a screen session. In a future release this will be changed so that it may be run as a system daemon.
The most-available stream URL is http://stream.twitter.com/1/statuses/sample.json. If you have another agreement with Twitter, substitute the provided URL here. It is also possible to provide the username, password, and URL using environment variables.
The public API can be summed up with just two functions.
Metadata
Release files for twittercollect 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 |
|---|---|---|---|---|
| twittercollect-0.1.0.tar.gz | 8.5 kB | Without provenance | Details for twittercollect-0.1.0.tar.gz |
Release files / twittercollect-0.1.0.tar.gz
| Download URL | twittercollect-0.1.0.tar.gz |
|---|---|
| Size | 8.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7553e1b35fcc8ad58f273d980ab4bf8e2a5a4f024f87bf1ab4922dbe258a38d1
|
|
BLAKE2b-256 checksum How to use checksums |
427689e75760d65b0ec3e32cd5be4a19e3d0fb99fab835da84c6cbb32537b6aa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for twittercollect 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.