Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

Python Python Basics Functions and Looping Returning Values

Posted by Mark Rogers
.a{fill-rule:evenodd;}techdegree
Mark Rogers
Python Development Techdegree Student 1,583 Points

File "<stdin>", line 1

In check_please.py, as soon as I added import math for the math ceiling I get a stdin error I do not understand. Please advise:

import math


def split_check(total, number_of_people):
    cost_per_person = math.ceil(total / number_of_people)
    return cost_per_person

amount_due = split_check(84.97, 4)
print("Each person owes ${}".format(amount_due))

Console returns:

>>> python check_please.py
  File "<stdin>", line 1
    python check_please.py 
           ^ 
SyntaxError: invalid syntax

2 Answers

Chris Freeman
MOD
Chris Freeman
Treehouse Moderator 68,457 Points
Chris Freeman
Chris Freeman
Treehouse Moderator 68,457 Points

Based on the “>>>”, you appear to be in the REPL interpreter. To run your code from there use:

>>> import check_please
Each person owes $22

As ‘python.py’ doesn’t exist to be imported by the REPL.

Or you may run from the shell:

$ python check_please.py

Post back if you need more help. Good luck!!!

Mark Rogers
seal-mask
.a{fill-rule:evenodd;}techdegree
Mark Rogers
Python Development Techdegree Student 1,583 Points
Mark Rogers
.a{fill-rule:evenodd;}techdegree
Mark Rogers
Python Development Techdegree Student 1,583 Points

Thanks for the reply Chris. I ended up shutting down the workspace a few times and reopening. Finally, it worked after exiting web browser and starting up again.

Not sure how/why it eventually fixed itself, but that's what had to happen.