Peter Suter

Thanks, that's very helpful to know. :+1: Is that documented somewhere? Is it specific to Pillow? ---- As far as I can tell: * The change happened from imageio 2.27.0...

I'd also like to read 16 bit grayscale images in the same code. Example: https://github.com/lunapaint/pngsuite/blob/main/png/basi0g16.png ```python >>> imageio.v3.imread("basi0g16.png").dtype dtype('int32') >>> imageio.v3.imread("basi0g16.png", mode="L").dtype dtype('uint8') >>> imageio.v3.imread("basi0g16.png", mode="I").dtype dtype('int32') >>> imageio.v3.imread("basi0g16.png", mode="I;16").dtype...

``` Traceback (most recent call last): File "", line 1, in imageio.v3.imread(r"test.tif", mode="L") File "C:\Python311\site-packages\imageio\v3.py", line 54, in imread return np.asarray(img_file.read(**call_kwargs)) File "C:\Python311\site-packages\imageio\plugins\tifffile_v3.py", line 189, in read ndimage = self._fh.asarray(series=index,...

> example to #959 as well as a reference to ImageProperties in the docs of `improps`. Nice. 👍 > a tuple of type `Tuple[Union[Tuple[float, ...], float], ...]`. If the spacing...

Yes, differentiating color channels from spatial axes is useful. (In OME-TIFF they call this DimensionOrder e.g. XYZTC and the "scaling" values are e.g. PhysicalSizeX, PhysicalSizeY, PhysicalSizeZ, TimeIncrement, WaveStart, and WaveIncrement....

Sure it doesn't break anything directly. However when not all files in a project use the same style e.g. copying lines from one file to another can easily lead to...

Same problem. ``` echo "C:\\example\\raw.dat">test.json jsonlint test.json ``` Expected output: `"C:\\example\\raw.dat"` Actual output: `"C:\\example\raw.dat"`

Apparently the Windows `py` launcher is aware of `VIRTUAL_ENV` ([already since Python 3.5](https://docs.python.org/3/whatsnew/3.5.html#pep-486-make-the-python-launcher-aware-of-virtual-environments), ([PEP 486 ](https://peps.python.org/pep-0486/)). Nice. 👍 The [The Python Launcher for Unix](https://github.com/brettcannon/python-launcher#the-python-launcher-for-unix) is also aware of `VIRUAL_ENV` https://python-launcher.app/#activated-virtual-environment...

Thanks for checking. You are right, it works in simple cases. It breaks once `\begin{longtable}` gets used instead of `\begin{tabulary}`, which seems to happen with 30 target items or more....

Might be that this is a general Sphinx issue: https://bitbucket.org/birkenfeld/sphinx/issue/1580/paragraphs-in-longtable-dont-work-in-latex