From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 2/2] package/python-flask: fix runtime python modules dependencies
Date: Sun, 22 Mar 2020 22:37:14 +0100 [thread overview]
Message-ID: <20200322223714.646434eb@gmx.net> (raw)
In-Reply-To: <20200322221811.0779c169@windsurf.home>
Hello Thomas,
On Sun, 22 Mar 2020 22:18:11 +0100, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> On Sun, 22 Mar 2020 22:10:02 +0100
> Peter Seiderer <ps.report@gmx.net> wrote:
>
> > - add python setuptools runtime dependency, fixes:
> > ModuleNotFoundError: No module named 'pkg_resources'
> >
> > - add python libxml2 runtime dependency, fixes:
> > ModuleNotFoundError: No module named 'xml'
> >
> > - add python ssl runtime dependency, fixes:
> > AttributeError: 'NoneType' object has no attribute 'SSLContext'
>
> Are all these dependencies intentionally mandatory, or are they
> mandatory "by mistake" ?
No python expert - from my side intentionally mandatory, started
with a minimal defconfig only selected python3/python-flask and
added packages until I got a error free invocation of flask for
an hello world example...
Regards,
Peter
>
> Thomas
next prev parent reply other threads:[~2020-03-22 21:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-22 21:10 [Buildroot] [PATCH v1 1/2] package/python-jinja2: fix runtime python modules dependencies Peter Seiderer
2020-03-22 21:10 ` [Buildroot] [PATCH v1 2/2] package/python-flask: " Peter Seiderer
2020-03-22 21:18 ` Thomas Petazzoni
2020-03-22 21:37 ` Peter Seiderer [this message]
2020-04-07 16:55 ` Peter Korsgaard
2020-04-08 20:40 ` Peter Seiderer
2020-04-08 21:04 ` Peter Korsgaard
2020-03-22 21:17 ` [Buildroot] [PATCH v1 1/2] package/python-jinja2: " Thomas Petazzoni
2020-03-22 21:39 ` Peter Seiderer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200322223714.646434eb@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.