unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Guix Workflow Language ?
Date: Thu, 25 Jan 2018 21:36:04 +0100	[thread overview]
Message-ID: <87fu6ty8uj.fsf@elephly.net> (raw)
In-Reply-To: <CAJ3okZ3qpSgFTSx7V2aPvmnvpHd0eASw1E1Ba8TUE81RZpnQ=A@mail.gmail.com>


Hi,

zimoun <zimon.toutoune@gmail.com> writes:

> In this context, since 'lispy' syntax is not mainstream (and will
> never be), it appears to me as a hard position.

We’ve got you covered here: the GWL has built-in support for Wisp, a
pretty language extension for Guile.  It also comes with a bunch of
extra syntax support to make the definition of workflows easier.

Here’s a convoluted artificial example:

--8<---------------cut here---------------start------------->8---
define-module
    test

use-modules
    guix workflows
    guix processes
    gnu packages bioinformatics
    gnu packages python

process: simple-test
    package-inputs
        list python samtools
    data-inputs
        list "sample.bam" "hg38.fa" "abc"
    procedure #---{python}
import os

def hello():
  print "hello from python 3"
  print GWL['data-inputs']
  print GWL['name']

hello()
---

workflow: example-workflow
    processes
        list simple-test
--8<---------------cut here---------------end--------------->8---

Put this in a file called “test.wisp” and add the directory to the
GUIX_WORKFLOW_PATH and you’re good to go.

Note that the “simple-test” process definition embeds Python code.  A
number of other languages can be supported easily.

I don’t think syntax should hold you back.

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

  reply	other threads:[~2018-01-25 20:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-24 14:25 Guix Workflow Language ? zimoun
2018-01-24 20:07 ` Roel Janssen
2018-01-25 16:16   ` zimoun
2018-01-25 20:36     ` Ricardo Wurmus [this message]
2018-01-25 22:04     ` Roel Janssen
2018-01-25 22:23       ` Cook, Malcolm
2018-01-26 13:05       ` Pjotr Prins
2018-01-29 16:55         ` zimoun
2018-01-30  1:57           ` Ricardo Wurmus
2018-02-15 17:28             ` zimoun

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fu6ty8uj.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).