Re: "**" in python

References	<20141123184316.77485a91@bigbox.christie.dr> <20141124010003.GA44963@cskk.homeip.net> <CAGGBd_pVNSCqhO-WAPW5bq8B80s+Cn2A7+A_Qgh8CzOY=o4hjA@mail.gmail.com>
Date	2014-11-23 19:48 -0600
Subject	Re: "**" in python
From	Skip Montanaro <skip.montanaro@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.16217.1416793733.18130.python-list@python.org> (permalink)

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

I want to add one more thing to the other responses. People new to Python
often seem unaware that being an interpreted language, often the best way
to figure something out is to simply try it at the interpreter prompt. The
OP saw "var ** 2" in done code. The most obvious thing to me would have
been to type

var = 42
var ** 2

and see what happened. It's unlikely to trigger a nuclear meltdown, or even
crash the interpreter.

Skip

Back to comp.lang.python | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Re: "**" in python Skip Montanaro <skip.montanaro@gmail.com> - 2014-11-23 19:48 -0600
  Re: "**" in python llanitedave <llanitedave@birdandflower.com> - 2014-11-23 18:30 -0800
  Re: "**" in python Steven D'Aprano <steve@pearwood.info> - 2014-11-24 04:47 +0000
    Re: "**" in python Chris Angelico <rosuav@gmail.com> - 2014-11-24 16:18 +1100
  Re: "**" in python albert@spenarnc.xs4all.nl (Albert van der Horst) - 2014-12-15 10:33 +0000
    Re: "**" in python Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-12-15 22:31 +1100

csiph-web