-
Notifications
You must be signed in to change notification settings - Fork 1
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
Improve and possibly vendor-in the tabulate package to get required functionality #701
Labels
Comments
andy-maier
changed the title
Vendor in the tabulate package
Improve and vendor in the tabulate package
Jul 31, 2020
Before we start forking tabulate (from its current repo on GitHub https://github.com/astanin/python-tabulate), we should work out what the issues are that we see, and whether we can deal with them. |
KSchopmeyer
changed the title
Improve and vendor in the tabulate package
Improve and possibly vendor-in the tabulate package to get required functionality
Aug 7, 2020
Moved to v 0.9.0 and also moves issue #249 |
Wanting for narrowing down the option space in issue #249 so we understand what the issues are that need to be addressed in tabulate. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
pywbemtools is using the tabulate package. We have proposed improvements for the nested table support it only very partially has right now, including a PR ready to be merged, but the maintainer of the package seems to be gone.
We need nested table support in order to address issue #249. See there for details on tabulate and the proposed change.
This issue is to fork the tabulate repo, so that the changes we need can be done there, and to include it as a vendored package within the pywbemtools package.
The text was updated successfully, but these errors were encountered: