GNU bug report logs - #44786
[PATCH] gnu: Add python-xlsxwriter.

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 44786 in the body.
You can then email your comments to 44786 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

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

From: Vinicius Monego <monego <at> posteo.net>
To: guix-patches <at> gnu.org
Cc: Vinicius Monego <monego <at> posteo.net>
Subject: [PATCH] gnu: Add python-xlsxwriter.
Date: Sat, 21 Nov 2020 23:40:07 -0300

* gnu/packages/python-xyz.scm (python-xlsxwriter): New variable.
---
 gnu/packages/python-xyz.scm | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/gnu/packages/python-xyz.scm b/gnu/packages/python-xyz.scm
index 32235c22a1..0d53797a36 100644
--- a/gnu/packages/python-xyz.scm
+++ b/gnu/packages/python-xyz.scm
@@ -5851,6 +5851,28 @@ a front-end for C compilers or analysis tools.")
 (define-public python2-pycparser
   (package-with-python2 python-pycparser))
 
+(define-public python-xlsxwriter
+  (package
+    (name "python-xlsxwriter")
+    (version "1.3.7")
+    (source
+     (origin
+       ;; There are no tests in the PyPI tarball.
+       (method git-fetch)
+       (uri (git-reference
+             (url "https://github.com/jmcnamara/XlsxWriter")
+             (commit (string-append "RELEASE_" version))))
+       (file-name (git-file-name name version))
+       (sha256
+        (base32 "1qg40r2mwrqfmhaxnary1cfgi0dwwazp5qga7c9p2cdji2v0x5rm"))))
+    (build-system python-build-system)
+    (home-page "https://github.com/jmcnamara/XlsxWriter")
+    (synopsis "Python module for creating Excel XLSX files")
+    (description
+     "XlsxWriter is a Python module that can be used to write text, numbers,
+formulas and hyperlinks to multiple worksheets in an Excel 2007+ XLSX file.")
+    (license license:bsd-2)))
+
 (define-public python-pywavelets
   (package
     (name "python-pywavelets")
-- 
2.20.1

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

From: Nicolas Goaziou <mail <at> nicolasgoaziou.fr>
To: Vinicius Monego <monego <at> posteo.net>
Cc: 44786 <at> debbugs.gnu.org
Subject: Re: [bug#44786] [PATCH] gnu: Add python-xlsxwriter.
Date: Tue, 24 Nov 2020 13:55:30 +0100

Hello,

Vinicius Monego <monego <at> posteo.net> writes:

> * gnu/packages/python-xyz.scm (python-xlsxwriter): New variable.

Thank you.

> +       ;; There are no tests in the PyPI tarball.
> +       (method git-fetch)

Is this the sole reason to not use PyPI here? If that's the case,
I wonder if it's worth reconsidering, because using PyPI makes updates
easier.

WDYT?

Regards,
-- 
Nicolas Goaziou

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

From: Vinicius Monego <monego <at> posteo.net>
To: Nicolas Goaziou <mail <at> nicolasgoaziou.fr>
Cc: 44786 <at> debbugs.gnu.org
Subject: Re: [bug#44786] [PATCH] gnu: Add python-xlsxwriter.
Date: Tue, 24 Nov 2020 18:25:47 -0300

Hello,

Nicolas Goaziou writes:

> Hello,
>
> Vinicius Monego <monego <at> posteo.net> writes:
>
>> * gnu/packages/python-xyz.scm (python-xlsxwriter): New variable.
>
> Thank you.
>
>> +       ;; There are no tests in the PyPI tarball.
>> +       (method git-fetch)
>
> Is this the sole reason to not use PyPI here? If that's the case,
> I wonder if it's worth reconsidering, because using PyPI makes updates
> easier.
>
> WDYT?

That is the sole reason. I prefer to enable tests because Python lacks
setup-time checking. Without tests, the build would succeed even if core
dependencies are unmet.

How does PyPI make updates easier, though? Refreshing works on GitHub.

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

From: Efraim Flashner <efraim <at> flashner.co.il>
To: Nicolas Goaziou <mail <at> nicolasgoaziou.fr>
Cc: Vinicius Monego <monego <at> posteo.net>, 44786 <at> debbugs.gnu.org
Subject: Re: [bug#44786] [PATCH] gnu: Add python-xlsxwriter.
Date: Wed, 25 Nov 2020 09:37:52 +0200

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

On Tue, Nov 24, 2020 at 01:55:30PM +0100, Nicolas Goaziou wrote:
> Hello,
> 
> Vinicius Monego <monego <at> posteo.net> writes:
> 
> > * gnu/packages/python-xyz.scm (python-xlsxwriter): New variable.
> 
> Thank you.
> 
> > +       ;; There are no tests in the PyPI tarball.
> > +       (method git-fetch)
> 
> Is this the sole reason to not use PyPI here? If that's the case,
> I wonder if it's worth reconsidering, because using PyPI makes updates
> easier.
> 
> WDYT?
> 

It is standard for us to use a git checkout when the pypi release
doesn't have the tests packaged. It's not uncommon for python packages
to build correctly but fail to run, and the test suite almost always
catches those.

-- 
Efraim Flashner   <efraim <at> flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[signature.asc (application/pgp-signature, inline)]

Message #19 received at 44786-done <at> debbugs.gnu.org (full text, mbox):

From: Nicolas Goaziou <mail <at> nicolasgoaziou.fr>
To: Efraim Flashner <efraim <at> flashner.co.il>
Cc: Vinicius Monego <monego <at> posteo.net>, 44786-done <at> debbugs.gnu.org
Subject: Re: [bug#44786] [PATCH] gnu: Add python-xlsxwriter.
Date: Thu, 26 Nov 2020 14:48:30 +0100

Hello,

Efraim Flashner <efraim <at> flashner.co.il> writes:

> It is standard for us to use a git checkout when the pypi release
> doesn't have the tests packaged.

I had not heard about this standard before. Considering many Python
packages are imported through PyPI, I genuinely wonder how common this
custom is, tho.

Fair enough. I applied the patch. Thank you!

Regards,
-- 
Nicolas Goaziou

Previous Next

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