Docs2Us PDF CLI
Docs2Us PDF CLI tool is a tool for obtaining brief stats concerning a PDF file.
Table of Contents
Getting Started
These instructions will guide you on how to install and use the Docs2Us PDF CLI tool.
Install
Install with pip
pip install docs2us-pdf-cli
Runn
The command is pdf-stats:
pdf-stats ~/path/to/your.pdf
{
"can_open": true,
"has_toc": false,
"is_pdf": true,
"password_protected": false,
"pdf_version": "1.3",
"size_bytes": 827244,
"size_pages": 12
}
Developing
Prerequisites
- Python 3.10 or higher
- Poetry (Python dependency management tool)
If you haven't installed Poetry yet, you can find the installation instructions here.
Setting up the Development Environment
-
Clone the Docs2Us PDF CLI repository to your local machine.
-
Navigate to the root directory of the cloned repository.
-
Run the following command to install the necessary dependencies:
poetry install -
To build the package with any changes, increase the version in
pyproject.tomland build:poetry build poetry install
Deploying
Test PyPi:
poetry config repositories.testpypi https://test.pypi.org/legacy/
poetry config pypi-token.testpypi YOUR_TEST_PYPI_TOKEN
poetry publish --repository testpypi
pip install --index-url https://test.pypi.org/simple/ YOUR_PACKAGE_NAME
Contributing
We welcome contributions from everyone. Here are a few guidelines to help you get started:
- Fork the Repository: Start by forking the Docs2Us PDF CLI repository to your own GitHub account.
- Clone the Repository: Clone the forked repository to your local machine.
- Create a New Branch: Always create a new branch for your changes. This keeps the commit history clean and easy to navigate.
- Make Your Changes: Make your changes in the new branch. Be sure to test your changes!
- Commit Your Changes: Commit your changes regularly with clear, concise commit messages.
- Push Your Changes: Once you're happy with your changes, push them to your forked repository.
- Submit a Pull Request: Finally, submit a pull request from your forked repository to the original Docs2Us PDF CLI repository. Be sure to provide a clear description of the changes you've made.
Before contributing, please read our Code of Conduct. By participating in this project, you agree to abide by its terms.
Thank you for your interest in contributing to Docs2Us!
Metadata
Release files for docs2us-pdf-cli 1.0.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 |
|---|---|---|---|---|
| docs2us_pdf_cli-1.0.0.tar.gz | 4.0 kB | Without provenance | Details for docs2us_pdf_cli-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| docs2us_pdf_cli-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for docs2us_pdf_cli-1.0.0-py3-none-any.whl |
Total release size: 9.0 kB
Release files / docs2us_pdf_cli-1.0.0.tar.gz
| Download URL | docs2us_pdf_cli-1.0.0.tar.gz |
|---|---|
| Size | 4.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
239672b83beef524ea5b5dcef7cb634c4b13136752da796cd143b380b510031a
|
|
BLAKE2b-256 checksum How to use checksums |
b0e8f986fa5505b38308a1228fb4af16a7fc370bdf559cb1c81061a6dcc3c9f7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.5.1 CPython/3.10.4 Darwin/23.3.0
|
Release files / docs2us_pdf_cli-1.0.0-py3-none-any.whl
| Download URL | docs2us_pdf_cli-1.0.0-py3-none-any.whl |
|---|---|
| Size | 4.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9145afa454300f8966ea8fc8414730fc2238fb39d87755443635b39b47e19a99
|
|
BLAKE2b-256 checksum How to use checksums |
d43c6cd03805eda2d7d519c340f7b7f9f4a3a73e1873bea6b0a22913b34fbcd5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.5.1 CPython/3.10.4 Darwin/23.3.0
|
Security for docs2us-pdf-cli 1.0.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.