-
Notifications
You must be signed in to change notification settings - Fork 27
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
make command fails on vega-visualization branch #59
Comments
Hey @letusfly85 thank you for getting in touch! I haven't looked into this problem in depth, but my first guess would be that we're supporting an older version of tabulate for this branch as you can see here: p-ranav/tabulate#44 so an easy fix should be downloading I have to say we're not currently maintaining this branch anymore, this was mostly an experiment to show people what are the possibilities with xeus-SQLite. Fortunately! Now we have @madhur-tandon doing some amazing work to make You can keep an eye on the QuantStack channel for updates: https://gitter.im/QuantStack/Lobby, or I could also ping you here, if you want to (both if you want to help with this integration or just know when it's done). :) |
Hi, @marimeireles thank you for your reply! I downgraded tabulate to I will wait for @madhur-tandon 's solution 👍 If you can, I want to get your ping from here. Currently, I'm supporting one of the data science classes at the university in Japan. Thank you! |
Awesome! :) But Madhur's work is definitely a much better alternative to what we currently have. It's gonna be worth some waiting :) |
hey @letusfly85! |
Closing this since this branch was discontinued and soon we'll release a version containing xvega by default. |
Hi, thank you for the cool extension!
We're now planning to use this library.
And if we can, we want to try using
vega
extension.So, I tried building on the following branch, it failed.
Is there any lack of installation or some steps...? 🤔
https://github.com/jupyter-xeus/xeus-sqlite/tree/vega-visualization
Thank you.
The text was updated successfully, but these errors were encountered: