From: fche@redhat.com (Frank Ch. Eigler)
To: David Smith <dsmith@redhat.com>
Cc: Nathan Scott <nathans@redhat.com>, systemtap <systemtap@sourceware.org>
Subject: Re: [PATCH] python3 support for /usr/bin/dtrace
Date: Mon, 23 Feb 2015 19:11:00 -0000 [thread overview]
Message-ID: <y0mr3tgfnoj.fsf@fche.csb> (raw)
In-Reply-To: <54EB54A5.2010801@redhat.com> (David Smith's message of "Mon, 23 Feb 2015 10:26:13 -0600")
> [...]
>> RHEL5 ships with python 2.4.*. Is there a solution that lets that
>> work too?
Yes, there is; a hack from http://python3porting.com/noconv.html makes
exception catching work on rhel5's python2.4 and python3. A new
commit does this, and a the dtrace.exp test case checks that the
python script runs fully on both python2 & python3.
- FChE
next prev parent reply other threads:[~2015-02-23 19:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <452908795.11130378.1424394762756.JavaMail.zimbra@redhat.com>
2015-02-20 5:09 ` Nathan Scott
2015-02-21 20:31 ` Frank Ch. Eigler
2015-02-22 23:44 ` Nathan Scott
2015-02-22 23:50 ` Frank Ch. Eigler
2015-02-23 0:45 ` Nathan Scott
2015-02-23 0:47 ` Frank Ch. Eigler
2015-02-23 16:26 ` David Smith
2015-02-23 19:11 ` Frank Ch. Eigler [this message]
2015-02-23 23:26 ` Nathan Scott
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=y0mr3tgfnoj.fsf@fche.csb \
--to=fche@redhat.com \
--cc=dsmith@redhat.com \
--cc=nathans@redhat.com \
--cc=systemtap@sourceware.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 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).