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
Failure on json export #52
Comments
Interesting! This does indeed look like a bug within Tablib. We could compensate for it here, but it would be better for everyone if we fixed it on Tablib's side. |
We do currently have a datetime fixer in this codebase, specifically for json, however. Perhaps we'll just add a Decimal fixer as well. |
Tablib uses |
Is it best to submit a pull request for omnijson and tablib separately, or to fix it within this repo? |
the separate projects would be best — tablib could likely drop support for omnijson altogether, and rely on the built-in json (this would require dropping support for Python 2.5, however) |
Ok, gave it a shot. PR on omnijson as well as tablib. |
After 'pip install ujson', I bypassed this bug. |
Require tablib>=0.11.4 to resolve #52
This issues shall be already resolved by upgraded tablib since version 0.11.4. PR #150 added requirement for |
I have the following table in a postgresql database:
That I can dump pretty easily in CSV:
But the same operation fails if I try to export to JSON or YAML:
Here is the full stack trace from Python:
Additional info:
Even more info:
The error may actually originate in Tablib or SQLAlchemy. If so, please let me know and I will move the issue.
The text was updated successfully, but these errors were encountered: