"Temporary" Variable

[darthbob88]

Problem: I wish to run an infinite loop and initialize a variable on
each iteration. Sort of like, "Enter Data", test it, "No good!", "Next
Try?", test it, etc. What I've tried is simply while 1: var1 =
raw_input, test var1, then run through the loop again. What results is
var1 gets and keeps the first value it receives. If this is in the FAQ,
my apologies, I did not find it. Thank you in advance.

[markscala]

I tried this code and it worked fine:

while 1:
var1 = raw_input("Ente r a number: ")
print "You entered:",var1
var1 = int(var1) + 1
print var1

[Steven D'Aprano]

da********@gmai l.com wrote:

Problem: I wish to run an infinite loop and initialize a variable on
each iteration. Sort of like, "Enter Data", test it, "No good!", "Next
Try?", test it, etc. What I've tried is simply while 1: var1 =
raw_input, test var1, then run through the loop again. What results is
var1 gets and keeps the first value it receives.

Hmmm. I get a syntax error.

while 1:

.... var1 = raw_input
.... test var1
File "<stdin>", line 3
test var1
^
SyntaxError: invalid syntax

How about posting your actual code?

You could try this:

while 1:
var = raw_input("Give me some data! ")
if var == "some data":
print "Success!"
break
else:
print "No good, try again."

--
Steven.

[darthbob88]

Steven D'Aprano wrote:

da********@gmai l.com wrote:

Problem: I wish to run an infinite loop and initialize a variable on
each iteration. Sort of like, "Enter Data", test it, "No good!", "Next
Try?", test it, etc. What I've tried is simply while 1: var1 =
raw_input, test var1, then run through the loop again. What results is
var1 gets and keeps the first value it receives.
Hmmm. I get a syntax error.

>>> while 1:

... var1 = raw_input
... test var1
File "<stdin>", line 3
test var1
^
SyntaxError: invalid syntax

How about posting your actual code?

Soitenly.
#!/usr/bin/python
#simple guessing game, with numbers
import random
spam = random.randint( 1, 100)
print spam #debugging purposes
while 1:
guess = raw_input("What 's your guess, friend? ")
if guess == spam:
print "You got it! Nicely done."
break
elif guess < spam:
print "Sorry, too low. Try again."
elif guess > spam:
print "Sorry, too high. Try again."
else:
print "You guessed ", guess You could try this:

while 1:
var = raw_input("Give me some data! ")
if var == "some data":
print "Success!"
break
else:
print "No good, try again." That works fine with strings and when "some_data" is hardcoded. I run
into trouble when "some data" is replaced with a number, unquoted. It
simply says "No good, etc" --
Steven.

[Rick Zantow]

da********@gmai l.com wrote in news:1140725159 .143882.202630
@j33g2000cwa.go oglegroups.com:

Steven D'Aprano wrote:

You could try this:

while 1:
var = raw_input("Give me some data! ")
if var == "some data":
print "Success!"
break
else:
print "No good, try again."

That works fine with strings and when "some_data" is hardcoded. I run
into trouble when "some data" is replaced with a number, unquoted. It
simply says "No good, etc"

Raw_input isn't giving you what you think it is. You're comparing it to
an integer, not a string. Does that help?

[Steven D'Aprano]

On Thu, 23 Feb 2006 12:05:59 -0800, darthbob88 wrote:

My comments inserted inline.

#!/usr/bin/python
#simple guessing game, with numbers
import random
spam = random.randint( 1, 100)
It is bad programming practice to give variables uninformative joke names.

How about target instead?
print spam #debugging purposes
while 1:
guess = raw_input("What 's your guess, friend? ")
Why don't you stick a "print guess" in here to see what your guess is?

(Hint: what is the difference between 1 and '1'?)
if guess == spam:
print "You got it! Nicely done."
break
elif guess < spam:
print "Sorry, too low. Try again."
elif guess > spam:
print "Sorry, too high. Try again."
else:
print "You guessed ", guess

You could try this:

while 1:
var = raw_input("Give me some data! ")
if var == "some data":
print "Success!"
break
else:
print "No good, try again."

That works fine with strings and when "some_data" is hardcoded. I run
into trouble when "some data" is replaced with a number, unquoted. It
simply says "No good, etc"

Try this, at a command line:

5 == '5'
and see what you get.
--
Steven.

[Jeffrey Schwab]

Steven D'Aprano wrote:

On Thu, 23 Feb 2006 12:05:59 -0800, darthbob88 wrote:

My comments inserted inline.

#!/usr/bin/python
#simple guessing game, with numbers
import random
spam = random.randint( 1, 100)

It is bad programming practice to give variables uninformative joke names.

Lighten up. This isn't the middle of a 100-KLOC corporate monstrosity,
it's a 1/2-page usenet post.

[Steven D'Aprano]

On Fri, 24 Feb 2006 00:24:25 +0000, Jeffrey Schwab wrote:

Steven D'Aprano wrote:

On Thu, 23 Feb 2006 12:05:59 -0800, darthbob88 wrote:

My comments inserted inline.

#!/usr/bin/python
#simple guessing game, with numbers
import random
spam = random.randint( 1, 100)

It is bad programming practice to give variables uninformative joke names.

Lighten up. This isn't the middle of a 100-KLOC corporate monstrosity,
it's a 1/2-page usenet post.

The original poster is also a newbie who was having trouble with the
difference between strings and ints. If Guido called a variable spam,
I wouldn't presume to correct him. When Newbie McNew does it, it might
very well be because he doesn't know any better.

Just out of curiosity, when do you think is the right time to begin
teaching programmers good practice from bad? Before or after they've
learnt bad habits?

--
Steven.

[bonono]

Steven D'Aprano wrote:

Just out of curiosity, when do you think is the right time to begin
teaching programmers good practice from bad? Before or after they've
learnt bad habits?

When you have authority over the coding guideline. Naming things is not
something limited to programming and most people know the importance of
choosing the appropriate ones. If on the other hand some names have
been chosen that have actual side effect(in python program), like
builtin function names, it is appropriate to point that out, though I
don't see that case here.

[Steven D'Aprano]

On Fri, 24 Feb 2006 01:50:40 -0800, bonono wrote:

Steven D'Aprano wrote:

Just out of curiosity, when do you think is the right time to begin
teaching programmers good practice from bad? Before or after they've
learnt bad habits?
When you have authority over the coding guideline.

By that logic, only senators and other government ministers are allowed
to tell people "Committing murder is strongly discouraged, don't do it",
because only they have authority over what is made law and what is not.

I don't need to be Guido van Rossum to know that calling a dict
"myFloat" is a terrible idea. Your suggestion that one needs somehow to be
authorized (by whom?) before you are allowed to point out poor programming
practice not only goes against the entire community ethos of
comp.lang.pytho n, but is offensive in the extreme.

Naming things is not
something limited to programming and most people know the importance of
choosing the appropriate ones.
"Most people". Let's not mention the Chevy Nova ("it won't go") then,
will we?

Car manufacturers seem to have a talent for not just choosing
bad names, but for getting them horribly, horribly wrong. I suggest
you google on "Opel Ascona", "Buick LaCrosse", "Honda Fitta", "Mitsubishi
Pajero", and the "Mazda LaPuta", to discover just why those cars went over
like lead balloons in places like Spain, Finland and Quebec.

But I digress. What of those that don't know the importance of choosing
appropriate names? We should just let them shoot themselves in the foot,
even when it is obvious to Blind Freddy that they are struggling with some
really basic concepts, and that they probably don't even know the gun is
loaded?

If on the other hand some names have
been chosen that have actual side effect(in python program), like
builtin function names, it is appropriate to point that out,

By your earlier logic, that should only be permitted to those who have
authority to create builtins, certainly not the likes of you and me.
--
Steven.