James Braza

Usually an issue stays open until it's resolved, not closed as completed when it wasn't. Think of issues as targets to aim for, but closing them defeats that

Per the `pydocstyle` "D100: Missing docstring in public module" error being raised, I learned from reading [`pydocstyle`'s Exclude given files #186](https://github.com/PyCQA/pydocstyle/issues/186) of using [`flake8-docstrings`](https://pypi.org/project/flake8-docstrings/) to ignore docstring problems on a...

To review: - `pydocstyle`: let's ignore that I said this... I don't agree with adding a module-level docstring - `pylint`: let's also ignore this... making the variable name say `VERSION`...

More out of curiosity, why add type annotations and then not export them? Is it just to test out type annotations for some time?

Oh that makes sense, thank you for circling back! Appreciate the quick response too

Lol give in to your temptations 😈 🔥 🚀 🦾 😆

Maybe `PACKAGE_ROOT` can have a fallback (or a configuration option `--package-root-is-not-cwd`) to maintain compatibility: 1. Looks in target directory (in this case, `./repo`) 2. Falls back on current working directory...

Before I answer, I want to understand one related scenario for `DOC501`. Let's say a parent class's method raises an `Exception`. If: - The child's overridden method calls `super()`, and...

Thank you @Madnex for your help here. In general, we have just released `paper-qa` version 5, which completely outsources all LLM management to [BerriAI/litellm](https://github.com/BerriAI/litellm). So I am going to close...

Hello @qayyumabro thank you for the issue. It seems unrelated to `paper-qa`, instead it's specific to Python on your machine, so I am going to close this out. Perhaps you...