From: Marius Bakke <mbakke@fastmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>, guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add python-pycontracts.
Date: Thu, 12 Jan 2017 19:26:40 +0100 [thread overview]
Message-ID: <878tqg6snz.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20170112093257.27397-1-dannym@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 2289 bytes --]
Danny Milosavljevic <dannym@scratchpost.org> writes:
> * gnu/packages/python.scm (python-pycontracts, python2-pycontracts):
> New variables.
> ---
> gnu/packages/python.scm | 32 ++++++++++++++++++++++++++++++++
> 1 file changed, 32 insertions(+)
>
> diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm
> index 4dc284d03..1cd4f168a 100644
> --- a/gnu/packages/python.scm
> +++ b/gnu/packages/python.scm
> @@ -2201,6 +2201,38 @@ have failed since the last commit or what tests are currently failing.")
> (define-public python2-testrepository
> (package-with-python2 python-testrepository))
>
> +(define-public python-pycontracts
> + (package
> + (name "python-pycontracts")
> + (version "1.7.15")
> + (source
> + (origin
> + (method url-fetch)
> + (uri (pypi-uri "PyContracts" version))
> + (sha256
> + (base32
> + "0sf41nccy5ihymiab31sfc4ylxd87fvvhbzqd8lhw7fnryskmgr4"))))
> + (build-system python-build-system)
> + (propagated-inputs
> + `(("python-decorator" ,python-decorator)
> + ("python-pyparsing" ,python-pyparsing)
> + ("python-six" ,python-six)))
> + (native-inputs
> + `(("python-nose" ,python-nose)))
> + (home-page "http://andreacensi.github.com/contracts/")
> + (synopsis "Checks declared constraints on function parameters and return
> +values")
This is a little too long for my taste. Maybe just 'Declare constraints
on function parameters and return values'. Checking them is kind of
implied, me thinks.
> + (description "PyContracts is a Python package that allows to declare
> +constraints on function parameters and return values. Contracts can be
> +specified using Python3 annotations, in a decorator, or inside a docstring
> +:type: and :rtype: tags. PyContracts supports a basic type system, variables
^^^^ ^^^^ @code{} on these.
> +binding, arithmetic constraints, and has several specialized contracts
> +(notably for Numpy arrays), as well as an extension API.")
> + (license license:lgpl3)))
> +
> +(define-public python2-pycontracts
> + (package-with-python2 python-pycontracts))
Otherwise LGTM, thanks! I guess you can push this yourself when the
account is set up :)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2017-01-12 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 9:32 [PATCH] gnu: Add python-pycontracts Danny Milosavljevic
2017-01-12 18:26 ` Marius Bakke [this message]
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=878tqg6snz.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.com \
--cc=dannym@scratchpost.org \
--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 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).