While investigating #6643, I found that

>>> from PIL import Image
>>> Image.new("RGB", (1, 1)).convert("XYZ")
Traceback (most recent call last):
  File "PIL/Image.py", line 1035, in convert
ValueError: conversion from RGB to XYZ not supported

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "PIL/Image.py", line 1040, in convert
ValueError: conversion from RGB to XYZ not supported
>>> 

It looks odd that "ValueError: conversion from RGB to XYZ not supported" is raised twice. One would expect the first time to be enough.

This is because of the following code. The intention is that if A -> B isn't supported, then maybe A -> C -> B will work, using the base mode as the intermediary.

But in this case, since getmodebase(self.mode) doesn't change the mode, it becomes A -> A -> B, and fails with the same error again.

This PR modifies that code so that if getmodebase(self.mode) doesn't change the mode, then this alternative conversion path is not attempted.