From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: Christopher Larson <clarson@kergoth.com>
Cc: "Avery, Brian" <brian.avery@intel.com>,
"toaster@yoctoproject.org" <toaster@yoctoproject.org>
Subject: Re: virtualenv for toaster and python 3
Date: Wed, 1 Jun 2016 12:27:36 +0300 [thread overview]
Message-ID: <20160601092736.GA6648@linux.intel.com> (raw)
In-Reply-To: <CABcZANmo1a_G7u5=t7Zou27j71xbKR6r=+HPbnzCueBsCUQq7w@mail.gmail.com>
On Tue, May 31, 2016 at 11:48:01AM -0700, Christopher Larson wrote:
> On Tue, May 31, 2016 at 11:47 AM, Brian Avery <avery.brian@gmail.com> wrote:
>
> > One possible solution is to use RP's suggestion to leverage the --user
> > argument (which stores packges in
> > $HOME/.local/lib/python3.4/site-packages.
> >
> > >pip3 install --user -r poky/bitbake/toaster-requirements.txt
> > * works except wsgiref is not python3 compatible yet
> > >pip3 list installed --local
> > argparse (1.2.1)
> > beautifulsoup4 (4.4.1)
> > Django (1.8.13)
> >
> > * works to show what is a --user install vs a global site install.
> > > pip3 uninstall/install --user --upgrade/.... works as expected...
> >
>
> Cluttering up my ~/.local with app/project specific requirements is not
> appropriate. As someone who uses --user quite a bit, I'd be quite annoyed
> by this.
So far pip3 --user looks like the only working approach to me. It's not
ideal, but it's not that bad either. It should be used for its direct purpose
- to install dependencies for 'one user' mode.
For production Toaster instances I'd suggest to install runtime
dependencies on the host system.
BTW, Toaster has only one runtime requirement: Django. argparse and
wsgiref is a legacy and beautifulsoup4 is not a runtime dependency. It's used only
in tests.
--
Regards,
Ed
next prev parent reply other threads:[~2016-06-01 9:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 10:45 virtualenv for toaster and python 3 Richard Purdie
2016-05-31 14:09 ` Christopher Larson
2016-05-31 18:28 ` Brian Avery
2016-05-31 18:47 ` Brian Avery
2016-05-31 18:48 ` Christopher Larson
2016-06-01 9:27 ` Ed Bartosh [this message]
2016-06-01 17:24 ` Christopher Larson
2016-06-01 20:12 ` Ed Bartosh
2016-06-08 12:56 ` Michael Wood
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=20160601092736.GA6648@linux.intel.com \
--to=ed.bartosh@linux.intel.com \
--cc=brian.avery@intel.com \
--cc=clarson@kergoth.com \
--cc=toaster@yoctoproject.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.
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.