Am 10.11.2016 um 13:35 schrieb Ludovic Courtès:
> Hmm, OK. That doesn’t make it sounds like it’s really safe to use with
> Python 3.
You challenged me :-) I fixed the test-suite using a simple change
which opens a file in binary mode.
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.g
Hartmut Goebel skribis:
> Am 10.11.2016 um 11:46 schrieb Ludovic Courtès:
>>> > +(arguments
>>> > + `(#:tests? #f)) ; tests fail in Python 3 (due to str vs bytes)
>> So probably we should only build the Python 2 variant? WDYT?
>>
>
> The main feature of PyPDF2 is that is supports Python
Am 10.11.2016 um 11:46 schrieb Ludovic Courtès:
>> > +(arguments
>> > + `(#:tests? #f)) ; tests fail in Python 3 (due to str vs bytes)
> So probably we should only build the Python 2 variant? WDYT?
>
The main feature of PyPDF2 is that is supports Python 3, what the old
pyPdf does not. So
Hartmut Goebel skribis:
> * gnu/packages/pdf.scm(python-pypdf2, python2-pypdf2): New variables.
^
Space please.
> +(arguments
> + `(#:tests? #f)) ; tests fail in Python 3 (due to str vs bytes)
So probably we should only build the Python 2 variant? WDYT?
> +@ite
* gnu/packages/pdf.scm(python-pypdf2, python2-pypdf2): New variables.
---
gnu/packages/pdf.scm | 45 +
1 file changed, 45 insertions(+)
diff --git a/gnu/packages/pdf.scm b/gnu/packages/pdf.scm
index ee33e3c..e243006 100644
--- a/gnu/packages/pdf.scm
+++