From: Henning Schild <henning.schild@siemens.com>
To: "[ext] Claudius Heine" <claudius.heine.ext@siemens.com>
Cc: <isar-users@googlegroups.com>
Subject: Re: Handling of additional python dependencies
Date: Wed, 27 Sep 2017 09:06:41 +0200 [thread overview]
Message-ID: <20170927090641.344991c8@md1em3qc> (raw)
In-Reply-To: <37e510ba-8e38-65d0-9980-286544bc8536@siemens.com>
Am Mon, 25 Sep 2017 14:44:13 +0200
schrieb "[ext] Claudius Heine" <claudius.heine.ext@siemens.com>:
> Hi,
>
> I am currently creating a proof of concept implementation for the
> caching apt repo proxy for isar.
Cant you just use some existing implementation, like apt-cacher or
apt-cacher-ng?
> My goal was to create this using asyncio, but the python std lacks a
> async http protocol implementation. I tried using as much as I can
> from the sync version of the http protocol that is available the
> python std lib, but that is not that trivial to do. I am now at the
> point where I have to decide if I just used some http asyncio library
> outside of the std or try another route with this. Maybe just use the
> sync version and slap more threads on it.
>
> How is the policy concerning external python dependencies and isar?
> Is it possible to just copy those libraries into the scripts/lib/
> directory, specify it as a host dependency or am I forced to only use
> the python std?
I would go for a host dependency or a git-submodule, more copies/forks
of stuff are not a good idea. Having bitbake and wic in there already
seems problematic.
Henning
> Thanks,
> Claudius
>
next prev parent reply other threads:[~2017-09-27 7:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 12:44 Claudius Heine
2017-09-27 7:06 ` Henning Schild [this message]
2017-09-27 7:44 ` Claudius Heine
2017-09-27 8:00 ` Henning Schild
2017-09-27 12:13 ` Claudius Heine
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=20170927090641.344991c8@md1em3qc \
--to=henning.schild@siemens.com \
--cc=claudius.heine.ext@siemens.com \
--cc=isar-users@googlegroups.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox