Installation
Install using pip
$ pip install -U magzdb
Usage
usage: magzdb [-h] [-V] -i MAGAZINE_ID [-e [EDITION [EDITION ...]]]
[-f FILTER] [-l] [-P DIRECTORY_PREFIX] [--downloader DOWNLOADER]
[--debug]
Magzdb.org Downloader
required arguments:
-i MAGAZINE_ID, --id MAGAZINE_ID
ID of the Magazine to Download. eg. http://magzdb.org/j/<ID>.
optional arguments:
-h, --help show this help message and exit
-V, --version Print program version and exit
-e [EDITION [EDITION ...]], --editions [EDITION [EDITION ...]]
Select Edition
-f FILTER, --filter FILTER
Use filter. See README#Filters
-l, --latest Download only latest edition.
-P DIRECTORY_PREFIX, --directory-prefix DIRECTORY_PREFIX
Download directory.
--downloader DOWNLOADER
Use External downloader (RECOMMENDED). Currently supported: aria2, wget, curl
--debug Print debug information.
--skip-download Don't download files.
Usage Examples
Docker
docker build . -t magzdb
docker run -v $(PWD):/tmp magzdb -h
# Add alias to shell
alias magzdb="docker run -v $(PWD):/tmp magzdb"
magzdb -h
Download all editions
$ magzdb -i 1826
Filters
You can supply filter using -f, for example to download issues between
4063895 and 4063901, you can write as
$ magzdb -i 1826 -f "eid > 4063895 and eid < 4063901"
You can use eid, year in the filter expression.
More examples of filter expression
eid > 4063895 and eid < 4063901oreid >= 4063895 and eid <= 4063901eid >= 4063895oreid != 4063895year >= 2018,year <= 2018,year == 2018or evenyear != 2018
Download only latest edition
$ magzdb -i 1826 -l
Download only latest edition with custom location magazine
$ magzdb -i 1826 -l -P magazine
Use external downloader
$ magzdb -i 1826 -l -P magazine --downloader wget
This is recommended since internal downloader does not support resuming interrupted downloads.
Python Installation Recommendation
If you don't want to install official Python to your system (global). You can install pyenv installer environment under your specific account. It's prefered method for macOS users, because High Sierra and later macOS ships with old Python 2.7.10.
Contributing
Found a bug or missing a feature you are more than welcome to contribute.
License
MIT
Metadata
Release files for magzdb 1.2.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 | |
|---|---|---|---|---|
| magzdb-1.2.0.tar.gz | 11.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| magzdb-1.2.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 20.4 kB
Release files / magzdb-1.2.0.tar.gz
| Download URL | magzdb-1.2.0.tar.gz |
|---|---|
| Size | 11.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c1267735631f8a8884074ec90d187f43ed3f5417deed89612f4ac2d7012d7ab7
|
|
BLAKE2b-256 checksum How to use checksums |
8833e3c0dd5a1f02d6851a759717c7865fac9e6a07fd3995060a5a78d0e30f04
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.16
|
Release files / magzdb-1.2.0-py2.py3-none-any.whl
| Download URL | magzdb-1.2.0-py2.py3-none-any.whl |
|---|---|
| Size | 9.1 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
bcb96d9e7eea06aa77124bd1a0e7a9cee2d317ec27b59c62e10518be818d1216
|
|
BLAKE2b-256 checksum How to use checksums |
42a561c36c86526eefa726bc2e7a776ab0312059a704526c6913eb72efa6ce43
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.16
|
Security for magzdb 1.2.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.