Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #81417

Re: "**" in python

Newsgroups comp.lang.python
Date 2014-11-23 18:30 -0800
References <20141123184316.77485a91@bigbox.christie.dr> <20141124010003.GA44963@cskk.homeip.net> <CAGGBd_pVNSCqhO-WAPW5bq8B80s+Cn2A7+A_Qgh8CzOY=o4hjA@mail.gmail.com> <mailman.16217.1416793733.18130.python-list@python.org>
Message-ID <ddd49362-4e0f-4924-9ce3-e0710b8e6ce5@googlegroups.com> (permalink)
Subject Re: "**" in python
From llanitedave <llanitedave@birdandflower.com>

Show all headers | View raw


On Sunday, November 23, 2014 5:49:05 PM UTC-8, Skip Montanaro wrote:
> 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


I dunno, if it took 7.5 million years to come up with the answer in the first place, imagine how long it might take to square it!

Back to comp.lang.python | Previous | Next — Previous in thread | 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