papers-cli 2.3.1__tar.gz → 2.5__tar.gz

{papers-cli-2.3.1 → papers_cli-2.5}/.github/workflows/tests.yml

@@ -10,7 +10,7 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        python-version: [ "3.8", "3.9", "3.10" ]
+        python-version: [ "3.9", "3.10", "3.11", "3.12", "3.13"  ]
 
     steps:
     - uses: actions/checkout@v2

papers_cli-2.5/.gitignore

@@ -0,0 +1,15 @@
+*.egg-info/
+*.pyc
+.tox
+.cache
+__pycache__
+build
+MANIFEST
+papers/_version.py
+dist/
+.coverage
+htmlcov/
+.venv
+.pytest_cache
+papers.sublime-project
+papers.sublime-workspace

{papers-cli-2.3.1/papers_cli.egg-info → papers_cli-2.5}/PKG-INFO

@@ -1,32 +1,40 @@
-Metadata-Version: 2.1
+Metadata-Version: 2.2
 Name: papers-cli
-Version: 2.3.1
+Version: 2.5
 Summary: utilities to keep your PDF library organized
 Author-email: Mahé Perrette <mahe.perrette@gmail.com>
 License: MIT
 Project-URL: homepage, https://github.com/perrette/papers
 Keywords: bibtex,references,bibliography
 Classifier: Programming Language :: Python :: 3
-Requires-Python: >=3.7
+Requires-Python: >=3.9
 Description-Content-Type: text/markdown
 License-File: LICENSE
+Requires-Dist: unidecode
+Requires-Dist: crossrefapi
+Requires-Dist: bibtexparser
+Requires-Dist: scholarly
+Requires-Dist: rapidfuzz
+Requires-Dist: normality
 
 [![test](https://github.com/perrette/papers/workflows/CI/badge.svg)](https://github.com/perrette/papers/actions)
-[![python](https://img.shields.io/badge/python-3.8-blue.svg)]()
 [![python](https://img.shields.io/badge/python-3.9-blue.svg)]()
 [![python](https://img.shields.io/badge/python-3.10-blue.svg)]()
 [![python](https://img.shields.io/badge/python-3.11-blue.svg)]()
+[![python](https://img.shields.io/badge/python-3.12-blue.svg)]()
+[![python](https://img.shields.io/badge/python-3.13-blue.svg)]()
 
 # papers
 
 Command-line tool to manage bibliography (pdfs + bibtex)
 
-> **WARNING**: This tool requires further development and testing, and is not fully production-ready as such (contributors welcome).
+Disclaimer: This tool requires further development and testing, and might never be fully production-ready (contributors welcome). \
+That said, it is becoming useful :)
 
 ## Motivation
 
 This project is an attempt to create a light-weight,
-command-line bibliography managenent tool. Aims:
+command-line bibliography management tool. Aims:
 
 - maintain a PDF library (with appropriate naming)
 - maintain one or several bibtex-compatible collections, linked to PDFs
@@ -35,13 +43,13 @@ command-line bibliography managenent tool. Aims:
 
 ## Dependencies
 
-- python 3.8+
+- python 3.9+
 - [poppler-utils](https://en.wikipedia.org/wiki/Poppler_(software)) (only:`pdftotext`): convert PDF to text for parsing
-- [bibtexparser (1.0.1)](https://bibtexparser.readthedocs.io) : parse bibtex files
-- [crossrefapi (1.2.0)](https://github.com/fabiobatalha/crossrefapi) : make polite requests to crossref API
-- [scholarly (0.2.2)](https://github.com/OrganicIrradiation/scholarly) : interface for google scholar
-- [rapidfuzz (0.2.0)](https://github.com/rhasspy/rapidfuzz) : calculate score to sort crossref requests
-- [unidecode (0.04.21)](https://github.com/avian2/unidecode) : replace unicode with ascii equivalent
+- [bibtexparser](https://bibtexparser.readthedocs.io) : parse bibtex files
+- [crossrefapi](https://github.com/fabiobatalha/crossrefapi) : make polite requests to crossref API
+- [scholarly](https://github.com/OrganicIrradiation/scholarly) : interface for google scholar
+- [rapidfuzz](https://github.com/rhasspy/rapidfuzz) : calculate score to sort crossref requests
+- [unidecode](https://github.com/avian2/unidecode) : replace unicode with ascii equivalent
 
 ## Install
 
@@ -102,15 +110,42 @@ If you already know the DOI of a PDF, and don't want to gamble the fulltext sear
 The `add` command above also works without any PDF (create a bibtex entry without file attachment).
 
     papers add --doi 10.5194/esd-4-11-2013 --bibtex papers.bib
-    
+
+
+### Add entry without DOI from bibtex library + PDF
+
+Some old files don't have a DOI. Best is to add the entry from its bibtex:
+
+    papers add entry.bib --attachment esd-4-11-2013.pdf
+
+
 ### List entries (and edit etc...)
 
-    $> papers list -l
+Pretty listing (-1 or -l for one-liner listing, otherwise plain bibtex):
+
+    $> papers list -1
     Perrette2013: A scaling approach to project regional sea level rise and it... (doi:10.5194/esd-4-11-2013, file:1)
 
-`papers list` is a useful command, inspired from unix's `find` and `grep`.
+Search with any number of keywords:
+
+    $> papers list perrette scaling approach sea level -1
+    ... (short list)
+    $> papers list perrette scaling approach sea level --any -1
+    ... (long list)
+    $> papers list --key perrette2013 --author perrette --year 2013 --title scaling approach sea level -1
+    ... (precise list)
+
+Add tags to view papers by topic:
+
+    $> papers list perrette2013 --add-tag sea-level projections -1
+    ...
+    $> papers list --tag sea-level projections -1
+    Perrette2013: A scaling approach to project regional sea level rise and it... (doi:10.5194/esd-4-11-2013, file:1, sea-level | projections )
+
+`papers list` is a powerful command, inspired from unix's `find` and `grep`.
+
 It lets you search in your bibtex in a typical manner (including a number of special flags such as `--duplicates`, `--review-required`, `--broken-file`...),
-then output the result in a number of formats (one-liner, raw bibtex, keys-only, selected fields) or let you perform actions on it (currently `--edit`, `--delete`).
+then output the result in a number of formats (one-liner, raw bibtex, keys-only, selected fields) or let you perform actions on it (currently `--edit`, `--delete`, `--add-tag`, `--fetch`).
 For instance, it is possible to manually merge the duplicates with:
 
     $> papers list --duplicates --edit
@@ -157,7 +192,6 @@ The same template and modifiers system applies to the bibtex key generation by r
 
 In the common case where the bibtex (`--bibtex`), files directory  (`--filesdir`), and name and key formats (e.g. `--name-template`) do not change, it is convenient to
 (install)[#install-make-bibtex-and-files-directory-persistent] `papers`.
-Install comes with the option to git-track any change to the bibtex file (`--git`) options.
 
 
 ### install: make bibtex and files directory persistent
@@ -187,11 +221,10 @@ Sometimes it is desirable to have separate configurations. In that case a local
     Bibtex file name [default to existing: papers.bib] [Enter/Yes/No]:
     Files folder [default to new: papers] [Enter/Yes/No]: pdfs
     papers configuration
-    * configuration file: .papers/config.json
+    * configuration file: papersconfig.json
     * cache directory:    /home/perrette/.cache/papers
     * absolute paths:     True
     * git-tracked:        False
-    * git-lfs tracked:    False
     * files directory:    pdfs (90 files, 337.4 MB)
     * bibtex:             papers.bib (82 entries)
 
@@ -216,7 +249,7 @@ and remove the configuration file by hand (`rm ...`). Or use `papers uninstall`
 
     papers uninstall
 
-You may repeat `papers status -v` and cleaning until a satistfying state is reached, or remove all config files recursively up to (and including) global install:
+You may repeat `papers status -v` and cleaning until a satisfying state is reached, or remove all config files recursively up to (and including) global install:
 
     papers uninstall --recursive
 
@@ -224,7 +257,7 @@ You may repeat `papers status -v` and cleaning until a satistfying state is reac
 ### Relative versus Absolute path
 
 By default, the file paths in the bibtex are stored as absolute paths (starting with `/`), except for local installs.
-It is possible to change this behavious explicitly during install or in a case by case basis with `--relative-paths` or `--absolute-paths` options.
+It is possible to change this behaviour explicitly during install or in a case by case basis with `--relative-paths` or `--absolute-paths` options.
 With or without install.
 
 
@@ -237,7 +270,7 @@ Simple cases are:
 In any other cases, you risk breaking the file links.
 
 Papers tries to be as little opinionated as possible about how files are organized, and so it relies on your own judgement and use case.
-When loading a bibtex, it always inteprete relative file links as being relative to the bibtex file.
+When loading a bibtex, it always interprete relative file links as being relative to the bibtex file.
 When saving a bibtex, it will save file links accordingly to the default setting path (usually absolute, unless local install or unless you specify otherwise).
 
 In any case, the following set of commands will always work provided the initial file links are valid (optional parameters in brackets):
@@ -278,25 +311,34 @@ That command is also convenient to check on what's actually tracked and what is
 
     Install comes with the option to git-track any change to the bibtex file (`--git`) options.
 
-    $> papers install --bibtex papers.bib --filesdir files --git
+    $> papers install --bibtex papers.bib --filesdir files --git  [ --git-lfs ]
 
 From now on, every change to the library will result in an automatic git commit.
 And `papers git ...` command will work just as `git ...` executed from the bibtex directory.
 E.g. `papers git add origin *REMOTE URL*`; `papers git lfs track files`; `papers git add files`; `papers git push`
-Note this is an experimental feature at this stage, with potential for improvement.
 
-This probably makes more sense for a global install (local installs usually have their own git tracking system).
+If `--git-lfs` is passed, the files will be backed-up along with the bibtex.
+Under the hood, bibtex and files (if applicable) are copied (hard-linked) to a back-up directory.
+Details are described in [issue 51](https://github.com/perrette/papers/issues/51).
+
+In local installs, backup occurs in `.papers/`. In global installs, defaults to `~/.local/.share/papers`.
+Type `papers status -v` to find out.
+
+For local install that are already git-tracked, the feature remains useful as it is the basis for `papers undo` and `papers redo`.
+You might want to add `.papers` to your .gitignore to avoid messing up with your larger project.
+
+This feature is experimental.
 
 
-### undo
+### undo / redo
 
 Did a `papers add` and are unhappy with the result?
 
     papers undo
 
 will revert to the previous version. If repeated, it will jump back and forth between latest and before-latest.
-
-Better to git-track your bibliography to go back deeper into history.
+Unless papers is installed with --git option, in which case `papers undo` and `papers redo` will have essentially infinite memory
+(doing undos and making a new commit risk loosing history, unless you keep track of the commit).
 
 
 Consult inline help for more detailed documentation!
@@ -315,10 +357,10 @@ Current features
 - some support for attachment
 - merging (`papers check --duplicates ...`)
 - fix entries (`papers check --format-name --encoding unicode --fix-doi --fix-key ...`)
-- undo command (`papers undo`)
 - configuration file with default bibtex and files directory (`papers install --bibtex BIB --filesdir DIR ...`)
-- integration with git (`papers install --git --gitdir DIR` and e.g. `papers git ...` to setup a remote, push...)
-- display / search / list entries : format as bibtex or key or whatever (`papers list ... [-k | -l]`)
+- integration with git
+- undo/redo command (`papers undo / redo`)
+- display / search / list entries : format as bibtex or key or whatever (`papers list ... [--key-only, -l]`)
 - list + edit or remove entry by key or else  (`papers list ... [--edit, --delete]`)
 - fix broken PDF links (`papers filecheck ...`):
     - remove duplicate file names (always) or file copies (`--hash-check`)
@@ -328,25 +370,12 @@ Current features
         - latex characters, e.g. `{\_}` or `{\'{e}}` replaced with unicode
 
 
-Feature ideas (TODO: organize as issues for discussion)
--------------
-- `papers encode`: text encoding in bibtex entries (latex, unicode, ascii)
-- additional checks on entries:
-    - duplicate-authors and more like [here](https://github.com/tdegeus/bibparse)
-- support collections (distinct bibtex entries, same files directory)
-    - or maybe more like ´papers update-from OTHER.bib´ to update changes based on DOI / key
-    - could also use git branches / merge
-- associate bibtex to existing pdf collection (to move library location)
-- fetch PDFs for existing entries? Bindings with [sopaper](https://github.com/ppwwyyxx/SoPaper)
-- lazy loading of modules (optimization)
-
-
 Tests
 -----
-Test coverage in progress...
+Test coverage is improving (now 80%)
 
 Currently covers:
-- `papers extract`
+- `papers extract` (test on a handful of PDFs)
     - parse pdf DOI
     - fetch bibtex on crossref based on DOI
     - fetch bibtex on crossref based fulltext search
@@ -355,21 +384,14 @@ Currently covers:
     - add entry and manage conflict
     - add pdf file, bibtex, directory
     - add one pdf file with attachment (beta, API will change)
-- `papers check --duplicates`
     - conflict resolution
-- `papers install` (superficial test)
+- `papers install`
 - internals:
     - duplicate test with levels `EXACT`, `GOOD`, `FAIR` (the default), `PARTIAL`
-
-
-Todo (more bug prone until then !):
-- `papers check` (fix DOI etc.)
-- `papers filecheck` (especially rename files, including those with attachment)
 - `papers list`
-- `papers status`
-- `papers install` (extend)
-- `papers undo`
-- `papers git`
+- `papers undo / redo` (partial)
+- `papers filecheck --rename` (superficial)
+- `papers check --duplicate` (fix DOI etc.) (superficial)
 
 
 Why not JabRef, Zotero or Mendeley (or...) ?

papers-cli-2.3.1/PKG-INFO → papers_cli-2.5/README.md

@@ -1,32 +1,21 @@
-Metadata-Version: 2.1
-Name: papers-cli
-Version: 2.3.1
-Summary: utilities to keep your PDF library organized
-Author-email: Mahé Perrette <mahe.perrette@gmail.com>
-License: MIT
-Project-URL: homepage, https://github.com/perrette/papers
-Keywords: bibtex,references,bibliography
-Classifier: Programming Language :: Python :: 3
-Requires-Python: >=3.7
-Description-Content-Type: text/markdown
-License-File: LICENSE
-
 [![test](https://github.com/perrette/papers/workflows/CI/badge.svg)](https://github.com/perrette/papers/actions)
-[![python](https://img.shields.io/badge/python-3.8-blue.svg)]()
 [![python](https://img.shields.io/badge/python-3.9-blue.svg)]()
 [![python](https://img.shields.io/badge/python-3.10-blue.svg)]()
 [![python](https://img.shields.io/badge/python-3.11-blue.svg)]()
+[![python](https://img.shields.io/badge/python-3.12-blue.svg)]()
+[![python](https://img.shields.io/badge/python-3.13-blue.svg)]()
 
 # papers
 
 Command-line tool to manage bibliography (pdfs + bibtex)
 
-> **WARNING**: This tool requires further development and testing, and is not fully production-ready as such (contributors welcome).
+Disclaimer: This tool requires further development and testing, and might never be fully production-ready (contributors welcome). \
+That said, it is becoming useful :)
 
 ## Motivation
 
 This project is an attempt to create a light-weight,
-command-line bibliography managenent tool. Aims:
+command-line bibliography management tool. Aims:
 
 - maintain a PDF library (with appropriate naming)
 - maintain one or several bibtex-compatible collections, linked to PDFs
@@ -35,13 +24,13 @@ command-line bibliography managenent tool. Aims:
 
 ## Dependencies
 
-- python 3.8+
+- python 3.9+
 - [poppler-utils](https://en.wikipedia.org/wiki/Poppler_(software)) (only:`pdftotext`): convert PDF to text for parsing
-- [bibtexparser (1.0.1)](https://bibtexparser.readthedocs.io) : parse bibtex files
-- [crossrefapi (1.2.0)](https://github.com/fabiobatalha/crossrefapi) : make polite requests to crossref API
-- [scholarly (0.2.2)](https://github.com/OrganicIrradiation/scholarly) : interface for google scholar
-- [rapidfuzz (0.2.0)](https://github.com/rhasspy/rapidfuzz) : calculate score to sort crossref requests
-- [unidecode (0.04.21)](https://github.com/avian2/unidecode) : replace unicode with ascii equivalent
+- [bibtexparser](https://bibtexparser.readthedocs.io) : parse bibtex files
+- [crossrefapi](https://github.com/fabiobatalha/crossrefapi) : make polite requests to crossref API
+- [scholarly](https://github.com/OrganicIrradiation/scholarly) : interface for google scholar
+- [rapidfuzz](https://github.com/rhasspy/rapidfuzz) : calculate score to sort crossref requests
+- [unidecode](https://github.com/avian2/unidecode) : replace unicode with ascii equivalent
 
 ## Install
 
@@ -102,15 +91,42 @@ If you already know the DOI of a PDF, and don't want to gamble the fulltext sear
 The `add` command above also works without any PDF (create a bibtex entry without file attachment).
 
     papers add --doi 10.5194/esd-4-11-2013 --bibtex papers.bib
-    
+
+
+### Add entry without DOI from bibtex library + PDF
+
+Some old files don't have a DOI. Best is to add the entry from its bibtex:
+
+    papers add entry.bib --attachment esd-4-11-2013.pdf
+
+
 ### List entries (and edit etc...)
 
-    $> papers list -l
+Pretty listing (-1 or -l for one-liner listing, otherwise plain bibtex):
+
+    $> papers list -1
     Perrette2013: A scaling approach to project regional sea level rise and it... (doi:10.5194/esd-4-11-2013, file:1)
 
-`papers list` is a useful command, inspired from unix's `find` and `grep`.
+Search with any number of keywords:
+
+    $> papers list perrette scaling approach sea level -1
+    ... (short list)
+    $> papers list perrette scaling approach sea level --any -1
+    ... (long list)
+    $> papers list --key perrette2013 --author perrette --year 2013 --title scaling approach sea level -1
+    ... (precise list)
+
+Add tags to view papers by topic:
+
+    $> papers list perrette2013 --add-tag sea-level projections -1
+    ...
+    $> papers list --tag sea-level projections -1
+    Perrette2013: A scaling approach to project regional sea level rise and it... (doi:10.5194/esd-4-11-2013, file:1, sea-level | projections )
+
+`papers list` is a powerful command, inspired from unix's `find` and `grep`.
+
 It lets you search in your bibtex in a typical manner (including a number of special flags such as `--duplicates`, `--review-required`, `--broken-file`...),
-then output the result in a number of formats (one-liner, raw bibtex, keys-only, selected fields) or let you perform actions on it (currently `--edit`, `--delete`).
+then output the result in a number of formats (one-liner, raw bibtex, keys-only, selected fields) or let you perform actions on it (currently `--edit`, `--delete`, `--add-tag`, `--fetch`).
 For instance, it is possible to manually merge the duplicates with:
 
     $> papers list --duplicates --edit
@@ -157,7 +173,6 @@ The same template and modifiers system applies to the bibtex key generation by r
 
 In the common case where the bibtex (`--bibtex`), files directory  (`--filesdir`), and name and key formats (e.g. `--name-template`) do not change, it is convenient to
 (install)[#install-make-bibtex-and-files-directory-persistent] `papers`.
-Install comes with the option to git-track any change to the bibtex file (`--git`) options.
 
 
 ### install: make bibtex and files directory persistent
@@ -187,11 +202,10 @@ Sometimes it is desirable to have separate configurations. In that case a local
     Bibtex file name [default to existing: papers.bib] [Enter/Yes/No]:
     Files folder [default to new: papers] [Enter/Yes/No]: pdfs
     papers configuration
-    * configuration file: .papers/config.json
+    * configuration file: papersconfig.json
     * cache directory:    /home/perrette/.cache/papers
     * absolute paths:     True
     * git-tracked:        False
-    * git-lfs tracked:    False
     * files directory:    pdfs (90 files, 337.4 MB)
     * bibtex:             papers.bib (82 entries)
 
@@ -216,7 +230,7 @@ and remove the configuration file by hand (`rm ...`). Or use `papers uninstall`
 
     papers uninstall
 
-You may repeat `papers status -v` and cleaning until a satistfying state is reached, or remove all config files recursively up to (and including) global install:
+You may repeat `papers status -v` and cleaning until a satisfying state is reached, or remove all config files recursively up to (and including) global install:
 
     papers uninstall --recursive
 
@@ -224,7 +238,7 @@ You may repeat `papers status -v` and cleaning until a satistfying state is reac
 ### Relative versus Absolute path
 
 By default, the file paths in the bibtex are stored as absolute paths (starting with `/`), except for local installs.
-It is possible to change this behavious explicitly during install or in a case by case basis with `--relative-paths` or `--absolute-paths` options.
+It is possible to change this behaviour explicitly during install or in a case by case basis with `--relative-paths` or `--absolute-paths` options.
 With or without install.
 
 
@@ -237,7 +251,7 @@ Simple cases are:
 In any other cases, you risk breaking the file links.
 
 Papers tries to be as little opinionated as possible about how files are organized, and so it relies on your own judgement and use case.
-When loading a bibtex, it always inteprete relative file links as being relative to the bibtex file.
+When loading a bibtex, it always interprete relative file links as being relative to the bibtex file.
 When saving a bibtex, it will save file links accordingly to the default setting path (usually absolute, unless local install or unless you specify otherwise).
 
 In any case, the following set of commands will always work provided the initial file links are valid (optional parameters in brackets):
@@ -278,25 +292,34 @@ That command is also convenient to check on what's actually tracked and what is
 
     Install comes with the option to git-track any change to the bibtex file (`--git`) options.
 
-    $> papers install --bibtex papers.bib --filesdir files --git
+    $> papers install --bibtex papers.bib --filesdir files --git  [ --git-lfs ]
 
 From now on, every change to the library will result in an automatic git commit.
 And `papers git ...` command will work just as `git ...` executed from the bibtex directory.
 E.g. `papers git add origin *REMOTE URL*`; `papers git lfs track files`; `papers git add files`; `papers git push`
-Note this is an experimental feature at this stage, with potential for improvement.
 
-This probably makes more sense for a global install (local installs usually have their own git tracking system).
+If `--git-lfs` is passed, the files will be backed-up along with the bibtex.
+Under the hood, bibtex and files (if applicable) are copied (hard-linked) to a back-up directory.
+Details are described in [issue 51](https://github.com/perrette/papers/issues/51).
+
+In local installs, backup occurs in `.papers/`. In global installs, defaults to `~/.local/.share/papers`.
+Type `papers status -v` to find out.
+
+For local install that are already git-tracked, the feature remains useful as it is the basis for `papers undo` and `papers redo`.
+You might want to add `.papers` to your .gitignore to avoid messing up with your larger project.
+
+This feature is experimental.
 
 
-### undo
+### undo / redo
 
 Did a `papers add` and are unhappy with the result?
 
     papers undo
 
 will revert to the previous version. If repeated, it will jump back and forth between latest and before-latest.
-
-Better to git-track your bibliography to go back deeper into history.
+Unless papers is installed with --git option, in which case `papers undo` and `papers redo` will have essentially infinite memory
+(doing undos and making a new commit risk loosing history, unless you keep track of the commit).
 
 
 Consult inline help for more detailed documentation!
@@ -315,10 +338,10 @@ Current features
 - some support for attachment
 - merging (`papers check --duplicates ...`)
 - fix entries (`papers check --format-name --encoding unicode --fix-doi --fix-key ...`)
-- undo command (`papers undo`)
 - configuration file with default bibtex and files directory (`papers install --bibtex BIB --filesdir DIR ...`)
-- integration with git (`papers install --git --gitdir DIR` and e.g. `papers git ...` to setup a remote, push...)
-- display / search / list entries : format as bibtex or key or whatever (`papers list ... [-k | -l]`)
+- integration with git
+- undo/redo command (`papers undo / redo`)
+- display / search / list entries : format as bibtex or key or whatever (`papers list ... [--key-only, -l]`)
 - list + edit or remove entry by key or else  (`papers list ... [--edit, --delete]`)
 - fix broken PDF links (`papers filecheck ...`):
     - remove duplicate file names (always) or file copies (`--hash-check`)
@@ -328,25 +351,12 @@ Current features
         - latex characters, e.g. `{\_}` or `{\'{e}}` replaced with unicode
 
 
-Feature ideas (TODO: organize as issues for discussion)
--------------
-- `papers encode`: text encoding in bibtex entries (latex, unicode, ascii)
-- additional checks on entries:
-    - duplicate-authors and more like [here](https://github.com/tdegeus/bibparse)
-- support collections (distinct bibtex entries, same files directory)
-    - or maybe more like ´papers update-from OTHER.bib´ to update changes based on DOI / key
-    - could also use git branches / merge
-- associate bibtex to existing pdf collection (to move library location)
-- fetch PDFs for existing entries? Bindings with [sopaper](https://github.com/ppwwyyxx/SoPaper)
-- lazy loading of modules (optimization)
-
-
 Tests
 -----
-Test coverage in progress...
+Test coverage is improving (now 80%)
 
 Currently covers:
-- `papers extract`
+- `papers extract` (test on a handful of PDFs)
     - parse pdf DOI
     - fetch bibtex on crossref based on DOI
     - fetch bibtex on crossref based fulltext search
@@ -355,21 +365,14 @@ Currently covers:
     - add entry and manage conflict
     - add pdf file, bibtex, directory
     - add one pdf file with attachment (beta, API will change)
-- `papers check --duplicates`
     - conflict resolution
-- `papers install` (superficial test)
+- `papers install`
 - internals:
     - duplicate test with levels `EXACT`, `GOOD`, `FAIR` (the default), `PARTIAL`
-
-
-Todo (more bug prone until then !):
-- `papers check` (fix DOI etc.)
-- `papers filecheck` (especially rename files, including those with attachment)
 - `papers list`
-- `papers status`
-- `papers install` (extend)
-- `papers undo`
-- `papers git`
+- `papers undo / redo` (partial)
+- `papers filecheck --rename` (superficial)
+- `papers check --duplicate` (fix DOI etc.) (superficial)
 
 
 Why not JabRef, Zotero or Mendeley (or...) ?