I "Hate" Papers
Create easily readable versions of papers via OpenAI
I often need to read a paper to provide background on a related topic. In these cases the technical depth of a paper can be a major obstacle. So I created I Hate Papers to create easily digestible versions of academic research.
Currently works with:
- An arXiv paper ID
- A local
.texfile - A local
.mdfile - A local
.htmlfile (experimental)
Installation
pip install i-hate-papers
Example use
# First set your OpenAI API key
❱ export OPENAI_API_KEY=...
# Summarise a arXiv paper ID
❱ i_hate_papers 2106.09685
# Summarise a latex file
❱ i_hate_papers path/to/some-paper.tex
# Summarise a html file
❱ i_hate_papers path/to/some-paper.html
Example output
- Example HTML (includes rendered math using MathJax)
- Example Markdown
Reference
❱ i_hate_papers --help
usage: i_hate_papers [-h] [--verbosity {0,1,2}] [--no-input] [--no-html] [--no-open] [--no-footer]
[--no-glossary] [--detail-level {0,1,2}] [--model MODEL] INPUT
Summarise an academic paper
You must set the OPENAI_API_KEY environment variable using your OpenAi.com API key
positional arguments:
INPUT arXiv paper ID (example: 1234.56789) or path to a .tex/.html/.md file
options:
-h, --help show this help message and exit
--verbosity {0,1,2} Set the logging verbosity (0 = quiet, 1 = info logging, 2 = debug logging). Default is 1
--no-input Don't prompt for file selection, just use the largest tex file
--no-html Skip HTML file generation
--no-open Don't open the HTML file when complete (macOS only)
--no-footer Don't include a footer containing metadata
--no-glossary Don't include a glossary
--detail-level {0,1,2}
How detailed should the summary be? (0 = minimal detail, 1 = normal, 2 = more detail)
--model MODEL What model to use to generate the summaries
Release process
For internal use:
export VERSION=0.1.1
poetry version $VERSION
git ci -a -m "Releasing version $VERSION"
git tag "v$VERSION"
git push origin main refs/tags/v$VERSION
poetry publish --build
Metadata
Release files for i-hate-papers 0.2.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 | Actions |
|---|---|---|---|---|
| i_hate_papers-0.2.1.tar.gz | 11.3 kB | Without provenance | Details for i_hate_papers-0.2.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| i_hate_papers-0.2.1-py3-none-any.whl | Python 3 | none | any | Details for i_hate_papers-0.2.1-py3-none-any.whl |
Total release size: 24.6 kB
Release files / i_hate_papers-0.2.1.tar.gz
| Download URL | i_hate_papers-0.2.1.tar.gz |
|---|---|
| Size | 11.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
749eebce70994700943b74287b0ab9e75f93a061dcd4c49aa8bdbe50cfec1aa1
|
|
BLAKE2b-256 checksum How to use checksums |
b04ed7c2f5b34e84db5d343560ae5daa3a14fd17704d4928ee8d24f4845c3620
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.5.1 CPython/3.11.4 Darwin/22.4.0
|
Release files / i_hate_papers-0.2.1-py3-none-any.whl
| Download URL | i_hate_papers-0.2.1-py3-none-any.whl |
|---|---|
| Size | 13.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
270cf4a6465cdd615106f0ebe035e70f8de777d3901687ddbce52bdcfcd405e3
|
|
BLAKE2b-256 checksum How to use checksums |
37ded129f420db65a26f7cb25df0522e2f542ba9a76cb4dc78946e232be1f2c6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.5.1 CPython/3.11.4 Darwin/22.4.0
|
Security for i-hate-papers 0.2.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.