Thomas Mansencal

> Since doctests are code, would this be more appropriate as a dedicated tool wrapping Black? This is a good point!

Oh awesome! I will give it a stab, that would be certainly worth showcasing in the black docs/website!

Interesting I got the same issue, and realised that the package I was using was not the one I intended!

@peterschindler : The Pypi package is simply not the same than this repository. For what it is worth, I forked this repo and made a Pypi package: https://pypi.org/project/biblib-simple/

Hi @Speierers, This is on macOs Catalina and the code is fresh from just before creating the ticket. I might have added the “packet_” modes after the initial build and...

Great information @greg-cohoon! I will re-run some tests with the latest version to see if it is still the same for me, probably should be but keen to confirm.

Hi, This seems like artefacts coming from sensor saturation as discussed in #3. Cheers, Thomas

The model is not bounded so there is not really a defined range. As to find that of *sRGB*, you could simply use the primaries and complementary colours to define...

We implemented them in Colour a few days ago, as Colorspacious has CIECAM02, it should be straightforward: https://github.com/colour-science/colour/pull/372/commits/b6a5d25f5a3f5652f8e402591b80aae56e39ffc1#diff-92c76ff05b61adca366526ad1d02fd45

Of interest and related: https://www.osapublishing.org/oe/abstract.cfm?uri=oe-25-13-15131 and https://figshare.com/articles/JzAzBz_m/5016299