NWChemEx / NWChemEx/PluginPlay
Weird Behaviors
Open
Nobody has claimed this yet.
good first issue
- Dominant language
- C++
- Stars
- 13
- Forks
- 1
- Avg merge
- 43m
- Merged PRs (30d)
- 4
Description
Writing the Python bindings has brought to light some weird behaviors that should be addressed:
Module Class
-
has_descriptionthrows for default modules (should be false) - default modules can be locked (not ready, so should throw)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the Module Class behavior used by the Python bindings, focusing on default modules, has_description, and locking. Confirm that has_description returns false for default modules and that locking a not-ready default module throws; verify both behaviors through the relevant binding checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100