Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #7241

Packaging Bokeh

Show all headers | View raw

Hi,

I've made some limited progress trying to package Bokeh (BSD-3-Clause) 
upstream: http://bokeh.pydata.org/en/latest/
my packaging: https://github.com/detrout/python-bokeh

I managed to get the version 0.9.1 from pypi installable. (Though since it was 
my own experiments I didn't remove the jquery / bootstrap libraries.)

The most proper packaging would require grunt to be able to rebuild bokeh.js. 
I was wondering if releasing the pypi version would be good enough. (The 
package does at least contain a non-minimized version of bokeh.js)
(And it looks like someone may have signed up to try and deal with the ITP for 
bokeh #756017)

I recently tried to update to bokeh 0.9.3 and their unit tests flushed out a 
few more dependencies.

I just packaged abstract_rendering (BSD-3-Clause) 
upstream: https://github.com/ContinuumIO/abstract_rendering/
my packaging: https://github.com/detrout/python-abstract-rendering

Bokeh's unit tests also appear to depend on blaze, and that looks like that 
has several missing dependencies.

Currently I built the packaging following the debian-qt team's common 
standards (source-less), Thought It looks like the python-modules team is just 
about to transition to git-dpm. 

Should I go ahead and submit abstract_rendering? Should I work on getting 
blaze submitted?

Diane

Back to linux.debian.maint.python | Previous | Next — Next in thread | Find similar

Thread

Packaging Bokeh Diane Trout <diane@ghic.org> - 2015-09-05 08:50 +0200
  Re: Packaging Bokeh "W. Martin Borgert" <debacle@debian.org> - 2015-09-05 10:00 +0200
    Re: Packaging Bokeh Diane Trout <diane@ghic.org> - 2015-09-05 18:50 +0200
      Re: Packaging Bokeh Diane Trout <diane@ghic.org> - 2015-09-06 06:50 +0200

csiph-web