From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: Kevin Wilson <wkevils@gmail.com>
Cc: "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] Python version for DTS
Date: Tue, 23 Apr 2019 18:07:11 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BA65699@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <CAGXs5wVNNZRQb5RQTes1fwvER3+_cw5kYvoiauo5_8cZ41izTw@mail.gmail.com>
Redhat7.4 scapy2.2.0
centos7.4 scapy2.2.0
fedora25 scapy2.3.1
> -----Original Message-----
> From: Kevin Wilson [mailto:wkevils@gmail.com]
> Sent: Saturday, April 20, 2019 9:40 AM
> To: Tu, Lijuan <lijuan.tu@intel.com>
> Cc: dts@dpdk.org
> Subject: Re: [dts] Python version for DTS
>
> Hello,
> Short question for developers/users of scapy, as I am not sure as to which
> scapy should be used:
> which scapy are you using on a RedHat distro like REHL/CentOS/Fedora ? can
> you please run "rpm -qa | grep scpay" and post it here ?
> and also
> "pip list | grep scapy"
>
> Thanks!
>
> Regards,
> Kevin
>
> On Sat, Feb 2, 2019 at 11:19 AM Tu, Lijuan <lijuan.tu@intel.com> wrote:
> >
> > Python 2.7
> >
> > > -----Original Message-----
> > > From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Kevin Wilson
> > > Sent: Friday, February 1, 2019 5:53 PM
> > > To: dts@dpdk.org
> > > Subject: [dts] Python version for DTS
> > >
> > > Hi, all,
> > >
> > > Which Python version should I use to run DTS test suites?
> > > Is it Python 2.7 (or any other Python 2.* version)?
> > >
> > > Or is it Python 3.* ?
> > >
> > > I did not see any mention of the require Python version to use, as
> > > far as I remember.
> > >
> > > Best Regards,
> > > Kevin Wilson
prev parent reply other threads:[~2019-04-23 18:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 9:52 Kevin Wilson
2019-02-02 9:19 ` Tu, Lijuan
2019-04-20 16:39 ` Kevin Wilson
2019-04-23 18:07 ` Tu, Lijuan [this message]
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=8CE3E05A3F976642AAB0F4675D0AD20E0BA65699@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=wkevils@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;
as well as URLs for NNTP newsgroup(s).