Live data from Hacker News

Pyxley: Python Powered Dashboards

multithreaded.stitchfix.com

21–30 of 47 posts

Re: Pyxley: Python Powered Dashboards

#21
post #11
post #6

Will work great until you try to render 50,000 points and your browser crashes because it's build on d3.

D3 is pretty ok with large datasets but I understand your point. What Shiny does to get around this is natively 'evaluate' the plots on the backend, creating a rasterized PNG file. A similar approach could work for Pyxley (using matplotlib or Seaborn to render the plot, and then sending that image file to the front end) but I fear with so much development time spent on d3 support such an approach would not be nativel…

>What Shiny does to get around this is natively 'evaluate' the plots on the backend, creating a rasterized PNG file

I don't think that's the case for D3 charts, because that would kill the interactivity that is so great about D3. I use RCharts to inject D3 into my Shiny applications, and have ran into into performance issues with just a couple hundred data points. I think this is because all heavy lifting is done by the client (browser), not the server.

Re: Pyxley: Python Powered Dashboards

#22
post #8

I've been looking for something to do this (below) in python at least on backend. Big screen on wall with 6 or so boxes. Each box displaying data which updates in real time. Such as - scrolling list of source control commits - graph of busy/idle slaves - single big number, pending builds - graph of open ticket counts - etc I can't tell if this is one of Pyxley's use cases?

I actually just implemented some thing very similar to this. You probably want to checkout Dashing [1] which has built in plugins for a lot of things already. It's pretty easy to work with as well.

[1] https://shopify.github.io/dashing/

Re: Pyxley: Python Powered Dashboards

#23

looks cool. shiny is very neat, but has the limitation of having R behind it and debugging ain't fun. I very much look forward to testing pyxley!

Why is having R a limitation? R is a fantastic data language which arguably beats all others in terms of number of libraries and data manipulation tools.

If GP comes from a more software-dev background, I can understand a general dislike for R. There's lots of things where R can't be beat right now, but for simple data analysis and visualization, there's some damn good python packages like pandas and d3py that GP may find easier to use than dataframes/tables and rCharts in R.

Re: Pyxley: Python Powered Dashboards

#24
post #22
post #8

I've been looking for something to do this (below) in python at least on backend. Big screen on wall with 6 or so boxes. Each box displaying data which updates in real time. Such as - scrolling list of source control commits - graph of busy/idle slaves - single big number, pending builds - graph of open ticket counts - etc I can't tell if this is one of Pyxley's use cases?

I actually just implemented some thing very similar to this. You probably want to checkout Dashing [1] which has built in plugins for a lot of things already. It's pretty easy to work with as well. [1] https://shopify.github.io/dashing/

And if the parent prefers doing it in python, there's pydashie [1], a python port of Dashing.

[1] https://github.com/evolvedlight/pydashie

Re: Pyxley: Python Powered Dashboards

#25
How important is flask in this mix? How difficult would it be to back this by a django app for example? I'm asking because the charting would be REALLY useful for me right now, and I already have the django models...

Re: Pyxley: Python Powered Dashboards

#26

How important is flask in this mix? How difficult would it be to back this by a django app for example? I'm asking because the charting would be REALLY useful for me right now, and I already have the django models...

The flask dependency is pretty strong because I used the requests module for the api route functions. It should be possible to override it and use django instead, but I don't know django that well. It's probably a good idea to separate that dependency so it's a little more flexible.

Re: Pyxley: Python Powered Dashboards

#27

How important is flask in this mix? How difficult would it be to back this by a django app for example? I'm asking because the charting would be REALLY useful for me right now, and I already have the django models...

The flask dependency is pretty strong because I used the requests module for the api route functions. It should be possible to override it and use django instead, but I don't know django that well. It's probably a good idea to separate that dependency so it's a little more flexible.

>The flask dependency is pretty strong because I used the requests module for the api route functions.

Not sure I understand? Are you talking about Kenneth Reitz's requests module? Why would that tie you to Flask or any other framework or library?

Re: Pyxley: Python Powered Dashboards

#28
post #22
post #8

I've been looking for something to do this (below) in python at least on backend. Big screen on wall with 6 or so boxes. Each box displaying data which updates in real time. Such as - scrolling list of source control commits - graph of busy/idle slaves - single big number, pending builds - graph of open ticket counts - etc I can't tell if this is one of Pyxley's use cases?

I actually just implemented some thing very similar to this. You probably want to checkout Dashing [1] which has built in plugins for a lot of things already. It's pretty easy to work with as well. [1] https://shopify.github.io/dashing/

Dashing is great, but it's Ruby on the backend, not Python :)

Re: Pyxley: Python Powered Dashboards

#29

Earlier quoted context omitted.

The flask dependency is pretty strong because I used the requests module for the api route functions. It should be possible to override it and use django instead, but I don't know django that well. It's probably a good idea to separate that dependency so it's a little more flexible.

>The flask dependency is pretty strong because I used the requests module for the api route functions. Not sure I understand? Are you talking about Kenneth Reitz's requests module? Why would that tie you to Flask or any other framework or library?

pyxley uses `flask.request`, not Kenneth Reitz's `requests`.

Re: Pyxley: Python Powered Dashboards

#30

How important is flask in this mix? How difficult would it be to back this by a django app for example? I'm asking because the charting would be REALLY useful for me right now, and I already have the django models...

If you already have a working web app, why not just use something like flot[1] for your charting (or d3 if you are up for it). Seems like pyxley is more targeted at people who have some data in pandas and want to get some visualizations on the web quickly.

[1]http://www.flotcharts.org/

Post reply on HN