From: ludo@gnu.org (Ludovic Courtès)
To: Eric Bavier <ericbavier@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 1/2] gnu: Add behave. (forgot the attchment...)
Date: Mon, 30 Jun 2014 12:51:12 +0200 [thread overview]
Message-ID: <874mz24qn3.fsf@gnu.org> (raw)
In-Reply-To: <CADwNbn8HKnvmmidHBmZ4yE1C+1NoEt58q+FC7Lvu3y+L59kydg@mail.gmail.com> (Eric Bavier's message of "Mon, 30 Jun 2014 00:43:47 -0500")
Eric Bavier <ericbavier@gmail.com> skribis:
> From ea01959c9d733b0151fbe1780a8c36244a43eb3a Mon Sep 17 00:00:00 2001
> From: Eric Bavier <bavier@member.fsf.org>
> Date: Mon, 30 Jun 2014 00:25:33 -0500
> Subject: [PATCH 1/2] gnu: Add behave.
>
> * gnu/packages/python.scm (python-six, python-enum34, python-parse-type,
> python-parse, behave): New variables.
OK.
> + (synopsis
> + "Extended parse module")
No newline after ‘synopsis’ please (in other places as well.)
> + (description
> + "")
Could you add a description? :-)
> + (synopsis "Python behaviour-driven development")
> + (description
> + "Behave is behaviour-driven development, Python style. Behavior-driven
> +development (or BDD) is an agile software development technique that
> +encourages collaboration between developers, QA and non-technical or business
> +participants in a software project. Behave uses tests written in a natural
> +language style, backed up by Python code.")
For the first sentence, perhaps something like “Behave is a tool for
behavior-drive development in Python”?
Also, choose “behaviour” or “behavior” (rather the latter.)
OK to push with these changes.
Thanks,
Ludo’.
next prev parent reply other threads:[~2014-06-30 10:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 5:43 [PATCH 1/2] gnu: Add behave. (forgot the attchment...) Eric Bavier
2014-06-30 10:51 ` Ludovic Courtès [this message]
2014-06-30 10:52 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874mz24qn3.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=ericbavier@gmail.com \
--cc=guix-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.