On Thu, Nov 27, 2014 at 9:54 AM, Todd wrote:
>
> On Nov 26, 2014 10:04 PM, "Nathaniel Smith" wrote:
>>
>> The main differences in requirements are:
>> - for the color cycle, you want isoluminant colors, to avoid the issue
>> where one line is glaring bright red and one is barely-visible-grey.
>>
For reference, the IPython script is in tools/update_whatsnew.py
On Thu Nov 27 2014 at 11:58:40 AM Ian Thomas wrote:
> On 27 November 2014 at 16:16, Thomas Caswell wrote:
>
>> There should be an automatic process, but no one has written it yet. I
>> think IPython has code we can adapt in thei
On 27 November 2014 at 16:16, Thomas Caswell wrote:
> There should be an automatic process, but no one has written it yet. I
> think IPython has code we can adapt in their doc build process. I had
> planned to deal with this when we cut the next minor/major release.
>
> Tom
>
Thanks for letting
There should be an automatic process, but no one has written it yet. I
think IPython has code we can adapt in their doc build process. I had
planned to deal with this when we cut the next minor/major release.
Tom
On Thu, Nov 27, 2014, 04:18 Ian Thomas wrote:
> Fellow developers,
>
> I know we a
On Nov 26, 2014 10:04 PM, "Nathaniel Smith" wrote:
>
> On Wed, Nov 26, 2014 at 9:30 AM, Todd wrote:
> > On Sat, Nov 22, 2014 at 12:22 AM, Nathaniel Smith wrote:
> >>
> >> - Default line colors: The rgbcmyk color cycle for line plots doesn't
> >> appear to be based on any real theory about visual
Fellow developers,
I know we are now encouraged when writing a PR not to alter
doc/users/whats_new.rst and doc/api/api_changes.rst directly, but rather to
create files in the doc/users/whats_new and doc/api/api_changes directories
instead. When building the master branch docs I was expecting the
