-
-
Notifications
You must be signed in to change notification settings - Fork 188
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
Impossible to import module in current working directory #83
Comments
Have you tried setting the For what it's worth, it looks like you're frustrated by Python's module import semantics rather than |
Thanks for your quick answer ! Yes, I tried in a vm, but in general I find using pythonpath highly inconvenient. Also, the point of this tool is to be lightweight (as I understood) and requiring users to make a virtualenv / modifying an environment variable kinda defeats this objective. Also, on a security side, this change of sys.path and/or PYTHONPATH are the same |
All you need to do:
I disagree. Requiring users to develop code idiomatically (i.e., I won't accept a patch that modifies |
Additionally, modifying |
It is currently impossible to document a module locally defined. It makes working with pdoc painful. Given the following folder structure:
The following doesn't work:
pdoc will only find
__init__.py
, however since the current working directory is not insys.path
python will not import the whole module. It won't even generate documentation for variables / functions in__init__.py
...The fix is simple, add these two lines to pdoc:405:
Then you can now work in any directory
The text was updated successfully, but these errors were encountered: