Check your indenting. This unhelpful SyntaxError error has fooled me before. :)

From the deleted question:

I'd expect this to be a duplicate, but I couldn't find it.

Here's Python code, expected outcome of which should be obvious:

x = {1: False, 2: True} # no 3

for v in [1,2,3]:
  try:
      print x[v]
  except Exception, e:
      print e
      continue
I get the following exception: SyntaxError: 'continue' not properly in loop.

I'd like to know how to avoid this error, which doesn't seem to be 
explained by the continue documentation.

I'm using Python 2.5.4 and 2.6.1 on Mac OS X, in Django.

Thank you for reading

There is very little difference between the two types. In fact, even the core Python developers agreed that there is no real difference and removed IOError in Python 3 (it is now an alias for OSError). See PEP 3151 - Reworking the OS and IO exception hierarchy:

While some of these distinctions can be explained by implementation considerations, they are often not very logical at a higher level. The line separating OSError and IOError, for example, is often blurry. Consider the following:

>>> os.remove("fff")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
OSError: [Errno 2] No such file or directory: 'fff'
>>> open("fff")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
IOError: [Errno 2] No such file or directory: 'fff'

Yes, that's two different exception types with the exact same error message.

For your own code, stick to throwing OSError. For existing functions, check the documentation (it should detail what you need to catch), but you can safely catch both:

try:
    # ...
except (IOError, OSError):
    # handle error

Quoting the PEP again:

In fact, it is hard to think of any situation where OSError should be caught but not IOError, or the reverse.

According to the Python Docs, the IOError is an alias of the OSError. In other words, the IOError is actually the OSError, so let's take a look at what the Python docs say about the OSError:

This exception is raised when a system function returns a system-related error, including I/O failures such as “file not found” or “disk full” (not for illegal argument types or other incidental errors).

Note: The above statement is true for Python 3.3 and up.

Sources:

• Regarding the IOError being an alias of the OSError: https://docs.python.org/3/library/exceptions.html#IOError

Note: If you click on the above link, you must scroll up a little to see the text talking about the IOError being an alias to the OSError.

• About the OSError: https://docs.python.org/3/library/exceptions.html#OSError

It is easy:

try:
  result = do_here_what_can_cause_IOError
except IOError as e:
  log.error('Error when trying to perform do_here_what_can_cause_IOError: %s', e)
else:
  use_the_result_here

In a word, to catch any kind of exception Python throws, use try/except/else/finally

The documentation here