-
Notifications
You must be signed in to change notification settings - Fork 114
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
PyDeps - Unable to render a module that uses a stdlib #181
Comments
Hi @Dholguin-Programmer , and thank you for your interest in pydeps. If I add the missing (empty)
and run pydeps from the parent folder of root (here
I get: |
Would you happen to know if relative vs absolute import paths would influence the expected behavior? I ask because my overall project is many levels of submodules that are references and am trying to get the leaf node directory and submodule wise to generate successfully before I attempt to generate from the 'root'. Also, is there a means I can toggle to try to debug this ValueError ? I tried enabling --debug but I'm not really seeing something that gives me enough output to deduce the actual error. |
From experience it is usually better to let pydeps have at the entire tree and exclude branches using the The ValueError is probably coming from python's modulefinder (or potentially from pydeps/mf27.py line 75, but a traceback would help verify. You can turn on modulefinder debugging using the For debugging pydeps the |
Hey, so running with -LDEBUG, I'm getting more information, but am not sure making much sense of the output, but at least I have some now. Below is what I got when running the follinwg command :
The Modules included (and branched) are as follows:
Taking your advice, I ran this from the root directory of the project. I'll proceed with the -X option and trying to narrow things down, but is there any particular signs I should be looking for? Once I deduce which modules are causing pydeps to barf, I'll post the information here. |
As the title suggest, I'm having issues using the pydeps utility whenever one of my classes imports a standard python module (os, etc).
Directory Structure
Main.py
I noticed that when I run the following command via bash, that it throws some sort of marshalling error.
Command:
cd root && pydeps Main.py --show-deps --show-dot --show-cycles --include-missing --pylib-all --no-show -o Main.svg && cd -
Return Code:
ValueError: bad marshal data (unknown type code)
Thus far, I've tried playing around with various command line options and have combed through various discussion boards, but haven't seen anything. Wanted to reach out to see if I'm misunderstanding something fundamental and if so, what it is. The only thing I noticed of importance is that when I remove all references to the os module internal to Main.py and omit the --pylib-all option, that I'm getting the graph I expect. The graph looks more or less something like this:
This isn't specific to the os module and I have seen it with anything that uses the standard set of python modules included. Below are versions of which Python version I have installed as well as the version of pydeps.
Python Version: Python 3.9.14
PyDeps Version: v1.12.2
The text was updated successfully, but these errors were encountered: