When using the following code using the python interpreter from ArcGIS Pro:
The result is:
When running using ArcGis Desktop 10.6 python it shows the expected result:
I experienced this bug before in the 10.3 release of ArcGIS Desktop.
Is this the correct behavior for ArcGIS Pro related python? Or is it the old bug acting up again?