Remove the dbmol CLI

Open
  • Is something wrong?
#138 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
cli

Research direction

Start by locating the dbmol CLI entry point and the packaging or release configuration that exposes it. Check whether any users report relying on it before proceeding. Done means the untested CLI is removed for Lomap's next major release without removing unrelated functionality.

Written by the indexing model from the issue text.

Description

The dbmol CLI is untested and increasingly becoming a maintenance burden.
To address this, we want to remove it in the next major release of Lomap.

If you are using this CLI entry point, please let us know here so that we can consider keeping the CLI.

Dominant language
Python
Stars
45
Forks
15
Avg merge
18h 11m
Merged PRs (30d)
4

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenFreeEnergy/Lomap

All issues in OpenFreeEnergy/Lomap

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.