---
title: "Comment by Aagam Sheth on \"Some Python built-in features that could lead to bugs\" | Hashnode"
description: "return balance - amount Line breaks in Python or any language assumes that a new statement has started. Python is a dynamic language, so you can't simply ch"
url: "https://hashnode.com/posts/some-python-built-in-features-that-could-lead-to-bugs/6013441a2e1296101bd585ec/comment/6013fce813f0a55761bdc4f7"
---

[Discussion](https://hashnode.com/posts/some-python-built-in-features-that-could-lead-to-bugs/6013441a2e1296101bd585ec)

Comment [Some Python built-in features that could lead to bugs](https://hashnode.com/posts/some-python-built-in-features-that-could-lead-to-bugs/6013441a2e1296101bd585ec)

[Aagam Sheth](https://hashnode.com/@AagamSheth)

[Jan 29, 2021](https://hashnode.com/posts/some-python-built-in-features-that-could-lead-to-bugs/6013441a2e1296101bd585ec/comment/6013fce813f0a55761bdc4f7)

```
return balance 
- amount
```

Line breaks in Python or any language assumes that a new statement has started. Python is a dynamic language, so you can't simply check for compilation errors and end of a statement `;` is not used in Python. So in the above code `balance` is returned. The interpreter never reaches `- amount` which never throws a error.

To write a statement in multiple lines you use `\` character to notify the interpreter that the next line is a part of the current statement.

```
  return balance \  # Line below is a part of current statement.
  - amount
```

Also floating point is not a bug of python but the underlying platform handling numbers. It happens because it is the way the underlying c platform (on which python works in a sense) handles floating-point numbers. Floating point error is not a bug. [Stackoverflow](https://stackoverflow.com/questions/62991249/how-pythons-round-function-works/62991488#62991488)

PS : Apologies. My intensions are not to criticize. Just sharing my opinions.

[iamoracle](https://hashnode.com/@iamoracle)

[Jan 29, 2021](https://hashnode.com/posts/some-python-built-in-features-that-could-lead-to-bugs/6013441a2e1296101bd585ec/comment/6013fce813f0a55761bdc4f7#reply-60143e87e54673573b570892)

Thank you very much for the explanation.

I believe we are saying almost the same thing. Check the explanation in the article, I explicitly stated that "This is a good practice that could lead to a potential bug as only the expressions directly on the same line as the return gets evaluated."