Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: jean.spector@gmail.com (Jean Spector)
Subject: [lttng-dev] Babeltrace python bindings documentation is no up-to-date
Date: Mon, 31 Oct 2016 23:20:42 +0200	[thread overview]
Message-ID: <CABVQWN1LwXepZrbnCTzbRbtUN+Z+fYw=eGvueq-W4rcGu9K7AA@mail.gmail.com> (raw)
In-Reply-To: <a9955420-8b89-fa48-7ee1-4d271af3bb41@efficios.com>

Hi Michael,

That's where I got python33 from eventually :-)
What I called out-of-the-box is actually EPEL.
I could just run "yum install python34" on my RHEL 7.2 (while the same
wouldn't work for python33), so for me it was the natural version to use.
Software Collections, though, required additional googling. Also, they
don't work out-of-the-box afterwards either, as you have to enable the scl
every time before using python33.




On Mon, Oct 31, 2016 at 10:54 PM, Michael Jeanson <mjeanson at efficios.com>
wrote:

> On 2016-10-31 16:44, Jean Spector wrote:
> > It's a matter of rpm dependencies.
> > Once installed, it might work fine with python 3.4 - but yum just
> > refuses to install it on RHEL 7.2
>
> RHEL 7 doesn't ship with python 3 out of the box, you'll need to get it
> from a software collection, have a look at :
>
>   https://www.softwarecollections.org/en/scls/rhscl/python33/
>
> Cheers,
>
> Michael
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.lttng.org/pipermail/lttng-dev/attachments/20161031/bccfb44a/attachment.html>


  reply	other threads:[~2016-10-31 21:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-29 13:55 Jean Spector
2016-10-31 17:07 ` Philippe Proulx
2016-10-31 20:02   ` Jean Spector
2016-10-31 20:38     ` Philippe Proulx
2016-10-31 20:44       ` Jean Spector
2016-10-31 20:54         ` Michael Jeanson
2016-10-31 21:20           ` Jean Spector [this message]
2016-10-31 21:34             ` Michael Jeanson

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='CABVQWN1LwXepZrbnCTzbRbtUN+Z+fYw=eGvueq-W4rcGu9K7AA@mail.gmail.com' \
    --to=jean.spector@gmail.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