As a side note, adding jitter has been discussed before
(https://github.com/matplotlib/matplotlib/issues/2750) in a slightly
different context and the consensus was to _not_ add it to mpl (as it
is a non-deterministic data transformation).
Tom
On Sat, Feb 15, 2014 at 10:45 PM, Yaroslav Halchenko
I left some comments on the wiki (in []). Not sure what the best way
to leave comments is.
On Mon, Jan 27, 2014 at 5:04 PM, Federico Ariza
wrote:
> Hello everybody
>
> I just added "click_tool" to simulate a click programatically.
> https://github.com/matplotlib/matpl
as
> Federico
>
> --
> Y yo que culpa tengo de que ellas se crean todo lo que yo les digo?
>
> -- Antonio Alducin --
>
> --
> Rapidly troubleshoot problems before they affect your business.
> I've got a branch going to refactor the boxplot function and address several
> issues that have cropped up lately.
>
> Currently, everything on my feature branch is working well except for
> Travis' Python 2.6 build.
>
> Here's a link directly the erro
There needs to be layers to the interface. At the bottom there is super
general stuff that will cover (we hope) 100% of use cases. However, the
cost is a very verbose interface with lots of knobs. To cope with this
there are higher level function which can deal with 90% of the use cases
and do
Please keep all emails in-band
I was commenting that the issue you are having with getting easy-to-use
pre-built figures in a non-interactive program without dragging pyplot in
is the same as what I think the root of 2503 is and the re-factor I
proposed to make your life easier would also help
embedding vs launching is a distinction without a difference, you are
integrating matplotlib with your own gui application.
That said, it would be nice to re-factor the figure_manager classes so they
they make no reference to `Gcf` or anything associated with pylab and could
be easily re-used.
I
If you are embedding matplotlib, do not import `pyplot`. `pyplot` sets up
a bunch of gui-magic (tm) in the background (as you found in
`figure_manager`).
Tom
On Fri, Oct 11, 2013 at 11:57 AM, Federico Ariza
wrote:
> Hello everybody
>
> Working on one GTK3 app, that calls matplotli
This thread from h5py may be relevant (https://github.com/h5py/h5py/pull/356).
Tom
On Fri, Sep 20, 2013 at 9:41 AM, Benjamin Root wrote:
> There is setup_requires, and from the documentation that I see, I wonder
> if listing NumPy in both build_requires and install_requires inv
<
lorenzo.digrego...@gmail.com> wrote:
> Hi,
>
> I've just installed matplotlib 1.3.0 and run into the following error when
> using the "home" button of a figure():
>
> Exception in Tkinter callback
> Traceback (most recent call last):
> File "
I second Eric's concern about pyplot being imported into everything. It
will really mess up the people that are embedding matplotlib into guis
because pyplot starts up gui mainloops if you are using an interactive
backend.
There is a genre of question on SO that is 'why isn't pypl
I think there is something to be said for not starting from pylab.
Answering questions on SO, a good chunk of them (by volume) can be
traced back to not understanding the magic that pylab is doing for you
in the background or not even knowing magic is being done for you.
Starting from pylab makes
Michael Droettboom writes:
> >
> Thanks for the pointers.
>
> The original simplification code was written by John Hunter (I believe),
> and I don't know if it was designed by him also or is a replication of
> something published elsewhere. So I take no
- it has the advantage of choosing points that actually
lie on the curve, which is better visually, and would seem to be a better
solution for publication quality plots.
The method for simplifying the paths is quite simple and effective, but a bit
crude- there are other algorithms you might look i
14 matches
Mail list logo
