New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to add path for a module #252
Comments
no matter what I try, I keep getting this error.
or this error::
|
Hello @sidhomj
Could you show us your Markdown file? Particularly the autodoc instruction, starting with |
so my file structure looks like this: -DeepTCR/DeepTCR.py and my markdown file has the following:
and i get this error:
with this yaml file:
|
Can you try this: plugins:
- mkdocstrings:
handlers:
python:
setup_commands:
- import sys
- sys.path.append('../')
selection:
new_path_syntax: true This will help debugging. |
now i get this error:
Is this because I have to install all dependencies on the venv storing mkdocs? |
Yes, or add it to |
your solution solved my problem! can you explain the reasoning behind using the new_path_syntax? |
|
So to answer, yes, your project and its dependencies must be installed for mkdocstrings to work. Closing, but feel free to continue the discussion! |
I am also having this problem. I can't seem to crack it. Here is my gha log Here is my workflow And my mkdoc I did attempt plugins:
- mkdocstrings:
handlers:
python:
setup_commands:
- import sys
- sys.path.append('../')
- python -c 'tablespoon'
- python -c 'cmdstanpy'
selection:
new_path_syntax: true but I had no luck |
When using the legacy (default) Python handler, you must install your project's dependencies as well:
|
mkdocs Okay. I updated this to install
This is my error below
|
You are mixing Python statements with shell commands in |
Thanks you! I think that did it. |
I think this is a fairly simple question but I haven't been able to solve it. If I have my python package in a different directory than my docs folder, how do I tell mkdocstrings to look at where the python package is?
I'm currently using the below in my .yaml file
The text was updated successfully, but these errors were encountered: