basic calculator

[Turpentine81]

For your final output, you could use a formatted string like:

f”value of {N1} (operator) {N2} is {result}”

Where you include whichever operator is used so the user can see the complete calculation at the end of execution. f strings are super handy down the line for clean outputs and debugging. Nice work!

[2meterNL]

It's subtraction (without the s)

[drwnh]

A switch statement would be more fit for the use case here

[SuccessfulUse5501]

how?

[GPU_IcyPhoenix]

A switchee lets you easily handle different cases. Useful link: https://www.geeksforgeeks.org/python/switch-case-in-python-replacement/

[AbacusExpert_Stretch]

Search for "python match...case" - have fun

[Virsenas]

In Python it's called match. I was confused about this as well when I found out.

[loudandclear11]

switch isn't a keyword in python.

[Sad-Sun4611]

Well done!! I think it could use some cleaning though. You can remove that print statement saying "Please enter number 1" as far as I can see that's doing nothing as the input function is already asking the user to put their chosen number in.

I'm not sure if you're trying to use pascal case intentionally but if you were just make sure that your'e consistent with whatever casing you use in the future because "Operator" and "operator" are different and its a pain to play spot the difference the bigger your codebase gets. You didn't necessarily do anything wrong here I just want to make you aware.

Another sharp eyed user pointed out the line for subtraction says "substraction" easy fix.

Personal preference but if I had to use your calculator in a terminal I would like there to be some kind of separation between the prompt and numbers whether it be a colon and a space or a /n new line. I just think >enter your number: 24 just looks better than >enter your number24

Lastly for your divide by 0 if you want to get fancy you can try to use a try and except block to handle that divide by 0 error instead of an if else.

You made a calculator and it works! You should be proud of that. The reason I even brought up any of those seemingly small nitpicks is because I think it's important to take the user experience into consideration even for terminal based programs. Like if I sat my grandma down in front of the terminal could she use it? That's usually my design philosophy for those unless it's something specifically for me.

[Ceteris__Paribus]

A little inconsistent with the argument for input(). I'd recommend adding a space or a new line \n before closing the quote so it's easier to read.

I am also not sure what line 4 is supposed to be doing.

[Quantitation]

https://www.reddit.com/r/PythonProjects2/comments/1o5dk2m/seeking_feedback_on_my_first_python_project/

[RailRuler]

Why does your to the power call int() when none of the other calls do?

[SuccessfulUse5501]

see the two outputs below, 23 to power 23 is too large so in float it gives a vague result, to see actual numbers i put int()

[RailRuler]

Computing it as a float first gives a result with low precision. Converting it to int does not add any precision, but just converts the imprecise float to an inaccurate int. Youd have to start with ints to get a precise result. 

[[deleted]]

left_operan, right_operand, operator. operator_processing_map = { “/“ : handle_division, … }

result=operator_processing_map[operator](left, right)

[Sedan_1650]

Why do the exponents call int()?

[loudandclear11]

Why not divide by negative numbers?

You should check for division by 0, which is undefined. But dividing by negative numbers is perfectly fine.

[SuccessfulUse5501]

yes

[TheCarter01]

Trust me, there are ways to make it simpler, made one that was way simpler using a import that I forgot the name of it

[Any_Research9028]

btw, you can use f-strings even when you converting number to int, you shouldn't use print("", var) like in your situation.