n't get around to actually making any
> changes, at the very least, I would file these issues as "bugs" to our
> issue tracker.
>
> Cheers!
> Ben Root
>
> On Tue, Mar 3, 2015 at 4:40 PM, Fabio Zanini
> mailto:fabio.zan...@tuebingen.mpg.de>>
> wrote:
&
to either create some pull requests to address some of these
> points, or at least file some bug reports so that we don't completely
> forget this. I may even be able to pick up some of it once my book
> finalizes for printing in the next week or two.
>
> Cheer
Dear Thomas,
Finally got some time to reply about the docs. My main point is not
about the API docs themselves, although they would need some tuning à la
MEP10. Rather, as Sebastian's doubts about pyplot/axes shows, I am
considering an issue with the non-API part of the docs, i.e. the user
guide,
Dear Sebastian,
I agree with your impression. I made a pull request for some axis
functionality (logit scales) and the PR got lost. I am convinced that:
1. working on things like axes, ticker, scales, locators would be a lot
easier with a little refactoring of the code
2. with a more modular cod
Dear all,
I made a pull request for this: #3753, at
https://github.com/matplotlib/matplotlib/pull/3753
Cheers,
Fabio
On 11/03/2014 01:30 PM, Fabio Zanini wrote:
> @Pierre: Yeah, my code looks 99% the same like yours. I'll make a PR
> starting from a mix of both - probably closer to
a plot with that
> scale and don't really understand it from your description. Seeing the
> code usually clarifies things.
>
> Tom
>
> On Mon, Nov 3, 2014, 05:58 Fabio Zanini <mailto:fabio.zan...@tuebingen.mpg.de>> wrote:
>
> Dear all,
>
>
Dear all,
I've been using matplotlib with great satisfaction for a few years, but
one feature I've been missing is a "logit" scale. This is essentially a
nonlinear scale that is log both towards 0+ and log towards 1-. It is
useful when one has frequencies in a population (i.e. floats between 0
and
