Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.web beat.web
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 54
    • Issues 54
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beatbeat
  • beat.webbeat.web
  • Issues
  • #497
Closed
Open
Issue created May 02, 2018 by Samuel GAIST@samuel.gaistOwner

Move to conda package

Currently all beat.something dependencies are being refactored to become conda packages. It has already been done for beat.backend.python, beat.core and beat.cmdline. The only one missing is beat.examples.

beat.web poses a different challenge has it requires several dependencies that are not directly available through conda's default channel or Idiaps software channel for bob. The main challenge comes from the fact that conda build doesn't support dependencies from PyPI directly. The current recommend practice is to use conda skeleton to create recipes for PyPI packages and use them to feed conda build

Here is a list of the dependencies that can be found in several places in beat.web like setup.py and buildout.cfg with their requirements and conda channel they can be found in if any:

package name requirements channel remarques
beat.core idiap
alabaster pkgs/main,pkgs/free
babel pkgs/main,pkgs/free
backports.shutil-get-terminal-size ODSP-TEST
colorlog software/bob/conda
coverage pkgs/main,pkgs/free
cycler pkgs/main,pkgs/free
decorator pkgs/main,pkgs/free
django >=1.11,<2.0 defaults
django-activity-stream >=0.6.5 too old
django-rest-swagger >2.1 too old
django-guardian >=1.3 conda-forge
djangorestframework >3.7 conda-forge
django-jsonfield >=1.0.1 too old
django-jsonfield-compat None
docopt pkgs/free
docutils pkgs/free
funcsigs pkgs/main,pkgs/free
functools32 pkgs/main,pkgs/free
graphviz pkgs/main,pkgs/free
ipdb software/bob/conda
ipython pkgs/main,pkgs/free
ipython-genutils GlaxoSmithKline linux only
imagesize pkgs/main,pkgs/free
Jinja2 pkgs/main,pkgs/free
jsonschema pkgs/main,pkgs/free
MarkupSafe pkgs/main,pkgs/free
matplotlib pkgs/main,pkgs/free
mock pkgs/main,pkgs/free
nose pkgs/main,pkgs/free
numpy pkgs/main,pkgs/free
oset software/bob/conda
pathlib2 pkgs/main,pkgs/free
pbr pkgs/main,pkgs/free
pexpect pkgs/main,pkgs/free
pickleshare pkgs/main,pkgs/free
pillow pkgs/main,pkgs/free
pip pkgs/main,pkgs/free
psutil pkgs/main,pkgs/free
ptyprocess pkgs/main,pkgs/free
psycopg2 pkgs/main,pkgs/free
Pygments pkgs/main,pkgs/free
pyparsing pkgs/main,pkgs/free
python-archive auto linux-only
python-dateutil pkgs/main,pkgs/free
pytz pkgs/main,pkgs/free
PyYAML pkgs/main,pkgs/free
pyzmq pkgs/main,pkgs/free
simplegeneric pkgs/main,pkgs/free
simplejson pkgs/main,pkgs/free
six pkgs/main,pkgs/free
snowballstemmer pkgs/main,pkgs/free
sphinx pkgs/main,pkgs/free
sphinxcontrib-ansi None
sphinxcontrib-httpdomain agoodman
sphinxcontrib-mscgen None
sphinxcontrib-programoutput software/bob/conda
sphinx-rtd-theme None
termcolor pkgs/main,pkgs/free
traitlets pkgs/main,pkgs/free
uwsgi conda-forge

One question that can be asked here is: do we still need all of them ?

This will also fix #462 (closed)

Edited May 02, 2018 by Samuel GAIST
Assignee
Assign to
Time tracking