Tidal App discussion

Applications
130

Ok, I’m going to suggest a two pronged approach.

  1. First we supply them using the technique I often use Packaging Python dependencies, a not-yet-guide - #17 by poetaster

  2. When time is there, I will package those (dateutil and future) on chum

  3. requires picking a release, including the directories of the sources and adding a line to the spec file.

EDIT: or, we simply use the install lib approach:

In project file (this is the way it’s done in audiocut):

python.files = lib/pydub/*
python.path = "/usr/share/harbour-audiocut/lib/pydub"

and in my qml python I include it:

import sys
sys.path.append('/usr/share/harbour-audiocut/lib/')

This is the most simple approach.

Sigh. Or we use git submodules just the way the tidal apis are pulled. I’ll look at this approach.

EDIT: So, future builds on github and chum, dateutls does not. I’m going to split the difference:

  1. first get dateutil in a separate package on chum
  2. push the build that works (with future) to chum proper after some testing
  3. move future to it’s own package. this is where I wish @nephros had gotten to these :slight_smile:
1 Like