From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: "guix-devel\\@gnu.org" <guix-devel@gnu.org>
Subject: Inkscape export errors
Date: Tue, 20 Oct 2020 12:53:58 +0000 [thread overview]
Message-ID: <v16YWkuYCqkGLS0XJw1a8YI8XPht0StW-sqzf2JdVu0ZPmP-v9T429frQGiZsVrAeOemuObxyjPX9yZEkEfP2adOjq8Xbq368rP958xRXD8=@elenq.tech> (raw)
Hi,
I'm experiencing export errors in Inkscape 1.0.1 on several formats like DXF or Optimized SVG. I'm getting the following error:
```
Traceback (most recent call last):
File "output_scour.py", line 8, in <module>
import inkex
File "/gnu/store/ky8vkkxi4b7a3bqlbmlagmv5j2vdnafb-inkscape-1.0.1/share/inkscape/extensions/inkex/__init__.py", line 11, in <module>
from .extensions import *
File "/gnu/store/ky8vkkxi4b7a3bqlbmlagmv5j2vdnafb-inkscape-1.0.1/share/inkscape/extensions/inkex/extensions.py", line 33, in <module>
from .elements import load_svg, BaseElement, ShapeElement, Group, Layer, Grid, \
File "/gnu/store/ky8vkkxi4b7a3bqlbmlagmv5j2vdnafb-inkscape-1.0.1/share/inkscape/extensions/inkex/elements/__init__.py", line 8, in <module>
from ._base import SVG_PARSER, load_svg, ShapeElement, BaseElement
File "/gnu/store/ky8vkkxi4b7a3bqlbmlagmv5j2vdnafb-inkscape-1.0.1/share/inkscape/extensions/inkex/elements/_base.py", line 31, in <module>
from lxml import etree
ModuleNotFoundError: No module named 'lxml'
```
I suppose it's because python-lxml package is not included in Inkscape. Is there any reason for that?
I tried to edit package description to add python-lxml as a propagated input but it didn't work. Why is that?
Also, adding python-lxml as a propagated input should leave it available system wide, shouldn't it? Am I getting this wrong?
Thanks for your help.
Cheers,
Ekaitz
next reply other threads:[~2020-10-20 12:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 12:53 Ekaitz Zarraga [this message]
2020-10-20 16:34 ` Inkscape export errors Thorsten Wilms
2020-10-20 17:51 ` Ekaitz Zarraga
2020-10-21 7:35 ` Thorsten Wilms
2020-10-21 13:03 ` Ludovic Courtès
2020-10-21 13:56 ` Ekaitz Zarraga
2020-10-21 15:59 ` Ludovic Courtès
2020-10-21 17:17 ` Ekaitz Zarraga
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='v16YWkuYCqkGLS0XJw1a8YI8XPht0StW-sqzf2JdVu0ZPmP-v9T429frQGiZsVrAeOemuObxyjPX9yZEkEfP2adOjq8Xbq368rP958xRXD8=@elenq.tech' \
--to=ekaitz@elenq.tech \
--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).