public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Masahiro Yamada <yamada.m@jp.panasonic.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH v2 0/2] Make Python scripts compatible with older versions
Date: Mon, 04 Aug 2014 22:28:35 +0900	[thread overview]
Message-ID: <20140804222835.D562.AA925319@jp.panasonic.com> (raw)
In-Reply-To: <53DF87CC.3050104@compulab.co.il>

Hi Igor,


On Mon, 04 Aug 2014 16:17:00 +0300
Igor Grinberg <grinberg@compulab.co.il> wrote:

> Hi Masahiro,
> 
> On 08/04/14 15:59, Masahiro Yamada wrote:
> > Hi.
> > 
> >>
> >>> It seems that those scripts only work on Python versions 2.6 - 2.7?
> > 
> > 
> > 
> > I took a quick look and I found  Python 3.x is not comatible 2.x at all.
> > 
> > 3.x  requires the "print" is called like
> > print(msg, file=sys.stderr)
> > but it failes in Python 2.7.x.
> 
> Last time I checked the print function, it worked with parenthesis on
> both versions 2.7 and 3.x.


I think

print("helloworld")

works on both 2.x and 3.x.

On 2.x,  ( ) is just meaningless parantheses and simply omitted.
On 3.x,  ( ) is mandatory for function call.


print("helloworld", file=sys.stderr)

never works on 2.x because the print statement
does not take named arguments


Best
Masahiro Yamada

  reply	other threads:[~2014-08-04 13:28 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-04 10:23 [U-Boot] [RFC PATCH v2 0/2] Make Python scripts compatible with older versions Masahiro Yamada
2014-08-04 10:23 ` [U-Boot] [RFC PATCH v2 1/2] kconfig: make multiconfig.py compatible with Python 2.4 Masahiro Yamada
2014-08-04 10:23 ` [U-Boot] [RFC PATCH v2 2/2] tools: make genboardscfg.py compatible with Python 2.5 Masahiro Yamada
2014-08-22  6:01   ` Masahiro Yamada
2014-08-22  6:18     ` Masahiro Yamada
2014-08-23 12:44     ` Tom Rini
2014-08-25  1:53       ` Masahiro Yamada
2014-08-04 10:40 ` [U-Boot] [RFC PATCH v2 0/2] Make Python scripts compatible with older versions Simon Glass
2014-08-04 11:21 ` Igor Grinberg
2014-08-04 12:00   ` Masahiro Yamada
2014-08-04 12:59     ` Masahiro Yamada
2014-08-04 13:17       ` Igor Grinberg
2014-08-04 13:28         ` Masahiro Yamada [this message]
2014-08-07 10:57         ` Tom Rini
2014-08-07 13:17           ` Igor Grinberg
2014-08-07 16:57             ` Tom Rini
2014-08-07 17:33               ` Stephen Warren
2014-08-07 17:53                 ` Tom Rini
2014-08-10  8:49                 ` Igor Grinberg
2014-08-10 11:14                   ` Tom Rini
2014-08-11 10:18                     ` Igor Grinberg
2014-08-11 13:12                       ` Tom Rini
2014-08-11 23:03                         ` Masahiro YAMADA
2014-08-12  1:53                           ` Tom Rini
2014-08-18  4:45                             ` Masahiro Yamada
2014-08-11 16:58                   ` Stephen Warren
2014-08-12 10:32                     ` Igor Grinberg
2014-08-04 13:50 ` Tom Rini
2014-08-05  2:05   ` Yan, Miao
2014-08-05 14:18     ` Tom Rini

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=20140804222835.D562.AA925319@jp.panasonic.com \
    --to=yamada.m@jp.panasonic.com \
    --cc=u-boot@lists.denx.de \
    /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