unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@libertad.pw>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Trouble setting up hplip and cups - printer ppd fails
Date: Thu, 29 Dec 2016 22:38:29 +0000	[thread overview]
Message-ID: <87vau2qs2i.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87h95me655.fsf@gnu.org>

Ludovic Courtès <ludo@gnu.org> writes:

> Hello!
>
> Danny Milosavljevic <dannym@scratchpost.org> skribis:
>
>> On Sat, 24 Dec 2016 14:08:44 +0000
>> ng0 <ng0@libertad.pw> wrote:
>>
>>> > Traceback (most recent call last):
>>> >   File "/gnu/store/95vp3r6n9z7s85achc7a0b8aay1k73qq-hplip-3.16.11/share/hplip/setup.py", line 560, in <module>
>>> >     desc = nickname_pat.search(nickname).group(1)
>>> > TypeError: cannot use a string pattern on a bytes-like object
>>
>> The reason that fails is because gzip.GzipFile always provides reads in binary mode. However, ppd files are not binary and nickname_pat is not binary either. So not sure what they were thinking...
>
> Could it be that Python 3 support in hplip is incomplete?  (ISTR that
> Python 3 treats Unicode sequences differently compared to Python 2.)
>
> The hplip recipe has this comment:
>
>     ;; Python3 support is available starting from hplip@3.15.2.
>
> Ludo’.

It works in Gentoo with python3, so maybe their one patch on this
is not just cosmetic.

-- 
♥Ⓐ  ng0
PGP keys and more: https://n0is.noblogs.org/ http://ng0.chaosnet.org

      reply	other threads:[~2016-12-29 22:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-24 13:56 Trouble setting up hplip and cups - printer ppd fails ng0
2016-12-24 14:08 ` ng0
2016-12-24 15:23   ` Danny Milosavljevic
2016-12-29 22:12     ` Ludovic Courtès
2016-12-29 22:38       ` ng0 [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=87vau2qs2i.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me \
    --to=ng0@libertad.pw \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).