Feature/blaze blueprint

[hhuuggoo]

No description provided.

[hhuuggoo]

#1635

[bryevdv]

Is PIL only needed for the test? If so, ideal to skip only for py3 but ok to skip altogether for now. If PIL is a real dependency we need to find a py3 pkg or find an alternative.

[pzwang]

Can we monkeypatch imresize to work with Pillow on Py3k?
https://github.com/python-pillow/Pillow

In any case, I don't think this test is worth holding up the merge. But definitely create an issue for this.

[hhuuggoo]

oh great! looks like if we install pillow then scipy.misc.imresize exists in both py3 and py2

[damianavila]

Just a corner comment: Nice to see Pillow enable the imresize... some time ago I tested with Pillow and it was not working so I switched to PIL... Pillow is better, so great it is working!

[bryevdv]

@hhuuggoo is this ready? It needs some docs for the examples, I can add some tomorrow but it would be good to merge this tomorrow if possible.

[hhuuggoo]

you mean comments on examples? I was going to add some sphinx docs, but I wanted to do that separately (unless you prefer in same pr, but this is getting large)

Yes I think this is ready after a review - there are some usability enhancements to make, but again - separate PR.

Before merging we should have a discussion about dependencies. The additional dependencies are

• blaze (current production release)
• into (based on master - I have a conda package in the bokeh channel)
• multiuserblazeserver (based on master - I have a conda package)

Not sure if you want to wait for a real into release - I can talk to @mrocklin about that, he said it would not take long to push one out. I can release the multiuserblazeserver immediately

[mrocklin]

I technically did a release for into a couple hours ago (version 0.1.4). I didn't publicize it though (well except for this blogpost about into generally) and will likely release again before strata.

I've also been thinking about making two blaze packages, one with minimal dependencies (numpy, pandas, into, sqlalchemy) and one with everything (hdf5, bcolz, ...) If this would ease hearts and minds in bokeh-land let me know.

[bryevdv]

BTW can we just call it blaze-server or if we must, multiuser-blaze-server

[hhuuggoo]

@JosephCottam can you have a look?

thanks

[JosephCottam]

The changes look solid, but not all of the server examples are updated as yet.

Of the files in examples/plotting/server that use remote data sources, only blaze_source.py and abstractrender.py are currently working. census.py, remote_image.py, serversource.py all fail on client-side execution due to changes in datasource setup parameters.

[hhuuggoo]

@JosephCottam I think census was the only one I didn't update - serversource, remote_image should have all been updated i thought? what is the error you are getting? I am getting additional errors on a few examples due to color maps being missing - I think this is unrelated and we should merge and then fix that problem later