Skip to main content

AutoReviewer

Tests PyPI PyPI - Python Version PyPI - License Documentation Status Codecov status Cookiecutter template from @cthoyt Code style: black Contributor Covenant

Scientists often do the same bad stuff. Automate giving feedback during peer review for Python packages.

Goals:

  1. Given a GitHub repository, automate finding common issues such as
    • No setup.py/setup.cfg/pyproject.toml
    • No zenodo archive linked from the README
    • Non-standard code layout (src/ or bust)
    • Files contain hard-coded file paths
    • No documentation (search README for link to readthedocs)
    • Package name doesn't match github repository name
    • No reproducible installation instructions (i.e., does the README contain pip)
    • Uses conda for installation
    • Code does not have consistent style (i.e., there's no configuration for black)
    • pyroma doesn't pass 10/10
    • missing LICENSE file
    • missing CITATION.cff file
  2. Automate sending issues to the repository instructing how to do these things
    • Use deterministic titles for all issues to avoid duplicates / make idempotent
    • Create and edit "epic" issue that links others

Example Reviews:

Want to collaborate? What do you expect out of Python packages? Let me know in the comments. I envision this being sort of modular so people can contribute their own checks.

Desired interface:

Run on the command line with:

$ autoreviewer https://github.com/rs-costa/sbml2hyb

J. Chem. Inf. Analysis

There's a submodule autoreviewer.jcheminf that has utilities for scraping the paper list from the Journal of Cheminformatics, getting their ePub files, extracting GitHub references from the availability statements, running autoreview on each, then making the following summary with python -m autoreviewer.jcheminf.

🚀 Installation

The most recent release can be installed from PyPI with:

$ pip install autoreviewer

The most recent code and data can be installed directly from GitHub with:

$ pip install git+https://github.com/cthoyt/autoreviewer.git

You'll also need to make sure pandoc is installed. The best way to do this is brew install pandoc on macOS.

👐 Contributing

Contributions, whether filing an issue, making a pull request, or forking, are appreciated. See CONTRIBUTING.md for more information on getting involved.

👋 Attribution

⚖️ License

The code in this package is licensed under the MIT License.

🍪 Cookiecutter

This package was created with @audreyfeldroy's cookiecutter package using @cthoyt's cookiecutter-snekpack template.

🛠️ For Developers

See developer instructions

The final section of the README is for if you want to get involved by making a code contribution.

Development Installation

To install in development mode, use the following:

$ git clone git+https://github.com/cthoyt/autoreviewer.git
$ cd autoreviewer
$ pip install -e .

🥼 Testing

After cloning the repository and installing tox with pip install tox, the unit tests in the tests/ folder can be run reproducibly with:

$ tox

Additionally, these tests are automatically re-run with each commit in a GitHub Action.

📖 Building the Documentation

The documentation can be built locally using the following:

$ git clone git+https://github.com/cthoyt/autoreviewer.git
$ cd autoreviewer
$ tox -e docs
$ open docs/build/html/index.html

The documentation automatically installs the package as well as the docs extra specified in the setup.cfg. sphinx plugins like texext can be added there. Additionally, they need to be added to the extensions list in docs/source/conf.py.

📦 Making a Release

After installing the package in development mode and installing tox with pip install tox, the commands for making a new release are contained within the finish environment in tox.ini. Run the following from the shell:

$ tox -e finish

This script does the following:

  1. Uses Bump2Version to switch the version number in the setup.cfg, src/autoreviewer/version.py, and docs/source/conf.py to not have the -dev suffix
  2. Packages the code in both a tar archive and a wheel using build
  3. Uploads to PyPI using twine. Be sure to have a .pypirc file configured to avoid the need for manual input at this step
  4. Push to GitHub. You'll need to make a release going with the commit where the version was bumped.
  5. Bump the version to the next patch. If you made big changes and want to bump the version by minor, you can use tox -e bumpversion minor after.

Metadata

Release files for autoreviewer 0.0.5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for autoreviewer 0.0.5
File Size Uploaded Provenance Actions
autoreviewer-0.0.5.tar.gz 316.8 kB Without provenance Details for autoreviewer-0.0.5.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for autoreviewer 0.0.5
File Interpreter ABI Platform Actions
autoreviewer-0.0.5-py3-none-any.whl Python 3 none any Details for autoreviewer-0.0.5-py3-none-any.whl

Total release size: 797.9 kB

Release files / autoreviewer-0.0.5.tar.gz

Download URL autoreviewer-0.0.5.tar.gz
Size 316.8 kB
Tags Source
SHA-256 checksum
How to use checksums
694ddff489aaddb64b20f2e1c0e06fed8bba42a6d4fd38f910aea002059981ae
BLAKE2b-256 checksum
How to use checksums
8dfb2e763bef65a2f33138a87afa1fda2cb7674b823d010260c64d4affba0d28
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/5.0.0 CPython/3.11.8

Release files / autoreviewer-0.0.5-py3-none-any.whl

Download URL autoreviewer-0.0.5-py3-none-any.whl
Size 481.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
3f4d12562ad43950ef75c6774bc5350a1a806beda9ca425d37e765a5653809f8
BLAKE2b-256 checksum
How to use checksums
986ee5750a773e9367e2f4dbff1183966c9b8e2d630c561f080a0978934cdd73
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/5.0.0 CPython/3.11.8

Security for autoreviewer 0.0.5

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page