GNU bug report logs - #40195
Add Docusign python API module as a package

Previous Next

Full log

Message #11 received at 40195 <at> debbugs.gnu.org (full text, mbox):

From: Josh Marshall <Josh.Marshall <at> jax.org>
To: Leo Famulari <leo <at> famulari.name>
Cc: "40195 <at> debbugs.gnu.org" <40195 <at> debbugs.gnu.org>
Subject: Re: [EXTERNAL]Re: [bug#40195] Add Docusign python API module as a
 package
Date: Tue, 24 Mar 2020 17:46:43 +0000

[Message part 1 (text/plain, inline)]

The tarballs that GitHub automatically generates per-tag (named like
'v3.0.0.tar.gz') do sometimes change, which breaks our packaging. So we
should package this either from the Git tag or from PyPI:
> Done

I think we should take the PyPi name as canonical, so as a Python
library, this Guix package should be called 'python-docusign-esign'.
> Done

Why are the tests skipped? Can you add a code comment? Even just "No
test suite" if that is the case.
> Done

Make sure to lint the package. You may need to do it in a Guix
development environment; something like this should work:
> I couldn't figure the command -- thanks.  Also done

Can you send a revised patch? 
> See attached

Also, does this integrate with any Guix packages?
> No?
---

The information in this email, including attachments, may be confidential and is intended solely for the addressee(s). If you believe you received this email by mistake, please notify the sender by return email as soon as possible.

[0001-Adding-Docusign-python-API-module-as-a-package.patch (application/octet-stream, attachment)]

[0002-Making-reccomended-changes.patch (application/octet-stream, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.