Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Scientific Computing with Python

You're reading from   Scientific Computing with Python High-performance scientific computing with NumPy, SciPy, and pandas

Arrow left icon
Product type Paperback
Published in Jul 2021
Publisher Packt
ISBN-13 9781838822323
Length 392 pages
Edition 2nd Edition
Languages
Tools
Arrow right icon
Authors (4):
Arrow left icon
Olivier Verdier Olivier Verdier
Author Profile Icon Olivier Verdier
Olivier Verdier
Jan Erik Solem Jan Erik Solem
Author Profile Icon Jan Erik Solem
Jan Erik Solem
Claus Führer Claus Führer
Author Profile Icon Claus Führer
Claus Führer
Claus Fuhrer Claus Fuhrer
Author Profile Icon Claus Fuhrer
Claus Fuhrer
Arrow right icon
View More author details
Toc

Table of Contents (23) Chapters Close

Preface 1. Getting Started 2. Variables and Basic Types FREE CHAPTER 3. Container Types 4. Linear Algebra - Arrays 5. Advanced Array Concepts 6. Plotting 7. Functions 8. Classes 9. Iterating 10. Series and Dataframes - Working with Pandas 11. Communication by a Graphical User Interface 12. Error and Exception Handling 13. Namespaces, Scopes, and Modules 14. Input and Output 15. Testing 16. Symbolic Computations - SymPy 17. Interacting with the Operating System 18. Python for Parallel Computing 19. Comprehensive Examples 20. About Packt 21. Other Books You May Enjoy 22. References

Raising exceptions

Creating an error is referred to as raising an exception. You saw some examples of exceptions in the previous section. You can also define your own exceptions of a predefined type or use an exception of an unspecified type. Raising an exception is done with a command like this:

raise Exception("Something went wrong")

Here an exception of an unspecified type was raised.

It might be tempting to print out error messages when something goes wrong, for example, like this:

print("The algorithm did not converge.")

This is not recommended for a number of reasons. Firstly, printouts are easy to miss, especially if the message is buried in many other messages being printed to your console. Secondly, and more importantly, it renders your code unusable by other code. The calling code will not read what you printed and will not have a way of knowing that an error occurred and therefore has no way of taking care of it.

For these reasons, it is always better...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image