-
Notifications
You must be signed in to change notification settings - Fork 53
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
Debugging #33
Comments
I wouldn't mind some debugging insights, not for the reasons you asked... but since even using |
I will add some documentation on debugging tips, but here are a few things to start: General Tips
DATA_WIZARD = {
"BACKEND": "data_wizard.backends.immediate"
} Debugging File Loading/Parsing (IterTable)To debug issues loading and parsing files, try using from itertable import load_file
for row in load_file('/path/to/file.xlsx'):
print(row)
If you are writing a custom Iter class, test the class with a similar loop: from myapp import CustomIter
for row in CustomIter(filename='/path/to/file.xlsx'):
print(row) Debugging the Serializer (DRF)To investigate validation issues, try instantiating the DRF serializer class directly. from data_wizard import registry
Serializer = registry.get_serializer("My Model")
serializer = Serializer(data={"test": "data"})
serializer.is_valid(raise_exception=True)
|
Hi there
This might be a question for DRF instead, but how exactly does one use
pdb
with this library. If one inserts aset_trace()
the output on the django server keeps rolling past and so even though one is able to interact with pdb, the command prompt disappears under a torrent of HTTP requests. Is there any way to pause everything so I can debug ?Thanks
The text was updated successfully, but these errors were encountered: