This project provides a collection of tools for the BitTorrent protocol and especially the rTorrent client. They enable you to filter rTorrent’s item list for displaying or changing selected items, also creating, inspecting and changing .torrent files, and much more.
An optional daemon process (pyrotorque) can add flexible queue management for rTorrent, starting items added in bulk slowly over time according to customizable rules. The same daemon can also watch one or more directory trees recursively for new metafiles using inotify, resulting in instantaneous loading without any polling and no extra configuration for nested directories.
The PyroScope command line utilities are not the same as the sibling project rTorrent-PS, and they work perfectly fine without it; the same is true the other way ‘round. It’s just that both unsurprisingly have synergies if used together, and some features do only work when both are present.
Further information can be found in the main documentation.
To get in contact and share your experiences with other users of PyroScope, join the pyroscope-users mailing list or the inofficial ##rtorrent channel on irc.freenode.net.
Copyright (c) 2009 - 2017 The PyroScope Project <pyroscope.project@gmail.com>
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
Metadata
Release files for pyrocore 0.5.3
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 |
|---|---|---|---|---|
| pyrocore-0.5.3.zip | 1.2 MB | Without provenance | Details for pyrocore-0.5.3.zip |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyrocore-0.5.3-py2-none-any.whl | Python 2 | none | any | Details for pyrocore-0.5.3-py2-none-any.whl |
Total release size: 1.5 MB
Release files / pyrocore-0.5.3.zip
| Download URL | pyrocore-0.5.3.zip |
|---|---|
| Size | 1.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6bbb018989d7778551fb461c2f75f1eddda08878bae42fe322976bd6927f37f5
|
|
BLAKE2b-256 checksum How to use checksums |
05bd681485581f02b998b9fca18c5462b9b93984a2209c90c01d4918e18e4657
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / pyrocore-0.5.3-py2-none-any.whl
| Download URL | pyrocore-0.5.3-py2-none-any.whl |
|---|---|
| Size | 251.9 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
b253fb65e8c6bb524b727dc82a00ef7e067dc2ca361402cd7f93d615e13b5cfc
|
|
BLAKE2b-256 checksum How to use checksums |
c827e45215e1d14fda352e974b46d093caa90f40fe622d5aa1eb25c0600befbf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pyrocore 0.5.3
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.