[Matplotlib-devel] [matplotlib-devel] matplotlib 1.5.1 closed path in draw_path when it is not necessary closed

[Jens Nielsen]

I can reproduce the problem with the GTK backend but not the GTKAgg or
GTKCairo backends. Unless you have some specific reason for using the GTK
backend I would strongly recommend against it. It is untested, unmaintained
and officially discouraged:
http://matplotlib.org/faq/usage_faq.html#what-is-a-backend I would
recommend you to use GTKAgg instead.

Furthermore the GDK toolkit, used in that backend, has been dropped from
GTK3 which officially uses Cairo internally and thus Matplotlib only
supports GTK3Agg and GTK3Cario

I guess the issue is likely a result of the large C++ refactoring in
master.

best
Jens




fre. 14. aug. 2015 kl. 15.21 skrev Thomas Caswell <tcaswell at gmail.com>:

> Please keep all discussion on the mailing list (
> matplotlib-devel at python.org).
>
> Being pedantic about versions, current master is v1.5.0dev1 , not 1.5.1
> (which will be the first bug fix release in the 1.5 series which may or may
> not ever happen).
>
> I don't have gtk installed to easily test this and it looks fine with
> qt4agg, can you provide a minimal script and the code paths from a simple
> polygon?
>
> Tom
>
> On Fri, Aug 14, 2015 at 9:05 AM Andrés Vargas <andnovar at gmail.com> wrote:
>
>> Hello Tom,
>>
>> Thanks for your prompt reply. I am using the function path.to_polygons()
>> and that gives me a non-closed path in matplotlib 1.4.3 (last stable
>> release) and give me a closed path in 1.5.1 (master from github). You can
>> see the problem if you run integral_demo.py with matplotlib 1.5.1 master
>> with matplotlib.use('gtk').
>>
>> Thanks, Andres
>>
>
>> On Fri, Aug 14, 2015 at 8:13 AM, Thomas Caswell <tcaswell at gmail.com>
>> wrote:
>>
>>> Did you mean 1.4.1 instead of 1.5.1 ?
>>>
>>> Exactly which paths are you looking at and how are you generating then
>>> on the mpl side? We have many ways to generate the paths and there maybe
>>> inconsistence in how closed paths are handled.
>>>
>>> Tom
>>>
>>> On Wed, Aug 12, 2015, 1:57 PM Andrés Vargas <andnovar at gmail.com> wrote:
>>>
>>>> Hello,
>>>>
>>>> My name is Andres I am developing a backend for kivy. I was initially
>>>> developing for 1.5.1 and I found that the paths are coming with the initial
>>>> vertex at the end of the list. Does anyone know whether this is change in
>>>> the way paths are sent ? and how can be fixed coming from 1.4.3 since I am
>>>> developing the backend for that version.
>>>>
>>>> Thanks, Andres
>>>>
>>>> ------------------------------------------------------------------------------
>>>> _______________________________________________
>>>> Matplotlib-devel mailing list
>>>> Matplotlib-devel at lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>>>
>>>
>>
>>
>> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20150814/15f36547/attachment.html>