Quite a few problems with your code: On Arrays.asList returning a fixed-size list From the API: Arrays.asList: Returns a fixed-size list backed by the specified array. You can’t add to it; you can’t remove from it. You can’t structurally modify the List. Fix Create a LinkedList, which supports faster remove. List<String> list = new LinkedList<String>(Arrays.asList(split)); … Read more
Commons Lang has it. Or you could throw an UnsupportedOperationException.
I haven’t tried this, so I don’t know if the JVM would restrict something like this, but maybe you could compile code which throws ChuckNorrisException, but at runtime provide a class definition of ChuckNorrisException which does not extend Throwable. UPDATE: It doesn’t work. It generates a verifier error: Exception in thread “main” java.lang.VerifyError: (class: TestThrow, … Read more
Yes, ensure ensures that the code is always evaluated. That’s why it’s called ensure. So, it is equivalent to Java’s and C#’s finally. The general flow of begin/rescue/else/ensure/end looks like this: begin # something which might raise an exception rescue SomeExceptionClass => some_variable # code that deals with some exception rescue SomeOtherException => some_other_variable # … Read more
I think it is too early to give a “best practices” answer for this as there hasn’t been enough time to use it in practice. If this was asked about throw specifiers right after they came out then the answers would be very different to now. Having to think about whether or not I need … Read more
Have a look at the Requests exception docs. In short: In the event of a network problem (e.g. DNS failure, refused connection, etc), Requests will raise a ConnectionError exception. In the event of the rare invalid HTTP response, Requests will raise an HTTPError exception. If a request times out, a Timeout exception is raised. If … Read more
logger.exception will output a stack trace alongside the error message. For example: import logging try: 1/0 except ZeroDivisionError: logging.exception(“message”) Output: ERROR:root:message Traceback (most recent call last): File “<stdin>”, line 2, in <module> ZeroDivisionError: integer division or modulo by zero @Paulo Cheque notes, “be aware that in Python 3 you must call the logging.exception method just … Read more
The statements in the else block are executed if execution falls off the bottom of the try – if there was no exception. Honestly, I’ve never found a need. However, Handling Exceptions notes: The use of the else clause is better than adding additional code to the try clause because it avoids accidentally catching an … Read more
Many people say that checked exceptions (i.e. these that you should explicitly catch or rethrow) should not be used at all. They were eliminated in C# for example, and most languages don’t have them. So you can always throw a subclass of RuntimeException (unchecked exception) However, I think checked exceptions are useful – they are … Read more
I would just raise ValueError, unless you need a more specific exception.. def import_to_orm(name, save=False, recurse=False): if recurse and not save: raise ValueError(“save must be True if recurse is True”) There’s really no point in doing class BadValueError(ValueError):pass – your custom class is identical in use to ValueError, so why not use that?