matplotlib-devel Mailing List for matplotlib (Page 2)

Removing the hardcoded paths works.

I noticed two more build issues.

1) On Python 3.x I see the following errors/warnings, however the build 
succeeds.

```
Can't parse docstring in build\lib.win-amd64-3.2\matplotlib\artist.py 
line 1265: ParseError: bad token: type=55, value="'", context=('', 
(1265, 38))
Can't parse docstring in build\lib.win-amd64-3.2\matplotlib\axes.py line 
3344: TokenError: ('EOF in multi-line statement', (2, 0))
Can't parse docstring in build\lib.win-amd64-3.2\matplotlib\axes.py line 
3345: ParseError: bad input: type=5, value='  ', 
context=('\n\n<snip>\n\n', (3345, 0))
Can't parse docstring in build\lib.win-amd64-3.2\matplotlib\axes.py line 
3346: ParseError: bad input: type=5, value='  ', 
context=('\n\n<snip>\n\n', (3346, 0))
Can't parse docstring in 
build\lib.win-amd64-3.2\matplotlib\backends\backend_agg.py line 322: 
TokenError: ('EOF in multi-line statement', (2, 0))
```

2) On Python 2.6 with distribute-0.6.45, the build fails during 
packaging. See <https://github.com/matplotlib/matplotlib/pull/2085>

Christoph


On 5/29/2013 12:08 PM, Michael Droettboom wrote:
> It seems that in the setuptools way [TM] it is rather difficult to not
> include this folder.  Does it work if you only remove those hardcoded
> paths?  It should be easy for me to fix that by not having it search for
> system libraries when building a tarball.
>
> Mike
>
> On 05/29/2013 02:55 PM, Christoph Gohlke wrote:
>> Hi,
>>
>> minor issue: the tarball contains a lib\matplotlib.egg-info directory.
>> The SOURCES.txt contains absolute paths (/usr/src/CXX/...) and
>> therefore fails to build on my system. Deleting the
>> lib\matplotlib.egg-info folder works.
>>
>> Does the release announcement mention that Windows binaries won't
>> include required dependencies (pytz, dateutil, pyparsing, six) any
>> longer?
>>
>> Christoph
>>
>>
>> On 5/29/2013 11:41 AM, Michael Droettboom wrote:
>>> I'm pleased to announce the tagging of matplotlib-1.3.0rc1.
>>>
>>> Once the binaries from Christoph and Russell have been uploaded, I'll
>>> make a broader announcement to get some testing of this in advance of
>>> the final release.
>>>
>>> The tarball is available here:
>>>
>>> https://downloads.sourceforge.net/project/matplotlib/matplotlib/matplotlib-1.3.0rc1/matplotlib-1.3.0rc1.tar.gz
>>>
>>>
>>>
>>> The documentation for this version is viewable here:
>>>
>>> http://matplotlib.org/1.3.0
>>>
>>> Thanks everyone for their hard work getting this out the door!
>>>
>>> Mike
>>>
>

It seems that in the setuptools way [TM] it is rather difficult to not 
include this folder.  Does it work if you only remove those hardcoded 
paths?  It should be easy for me to fix that by not having it search for 
system libraries when building a tarball.

Mike

On 05/29/2013 02:55 PM, Christoph Gohlke wrote:
> Hi,
>
> minor issue: the tarball contains a lib\matplotlib.egg-info directory. 
> The SOURCES.txt contains absolute paths (/usr/src/CXX/...) and 
> therefore fails to build on my system. Deleting the 
> lib\matplotlib.egg-info folder works.
>
> Does the release announcement mention that Windows binaries won't 
> include required dependencies (pytz, dateutil, pyparsing, six) any 
> longer?
>
> Christoph
>
>
> On 5/29/2013 11:41 AM, Michael Droettboom wrote:
>> I'm pleased to announce the tagging of matplotlib-1.3.0rc1.
>>
>> Once the binaries from Christoph and Russell have been uploaded, I'll
>> make a broader announcement to get some testing of this in advance of
>> the final release.
>>
>> The tarball is available here:
>>
>> https://downloads.sourceforge.net/project/matplotlib/matplotlib/matplotlib-1.3.0rc1/matplotlib-1.3.0rc1.tar.gz 
>>
>>
>>
>> The documentation for this version is viewable here:
>>
>> http://matplotlib.org/1.3.0
>>
>> Thanks everyone for their hard work getting this out the door!
>>
>> Mike
>>

On 05/29/2013 02:55 PM, Christoph Gohlke wrote:
> Hi,
>
> minor issue: the tarball contains a lib\matplotlib.egg-info directory. 
> The SOURCES.txt contains absolute paths (/usr/src/CXX/...) and 
> therefore fails to build on my system. Deleting the 
> lib\matplotlib.egg-info folder works.

Doh.  This is the first time building with setuptools -- I'll fix that 
and create a new tarball...  1.3.0rc2 here we come!
>
> Does the release announcement mention that Windows binaries won't 
> include required dependencies (pytz, dateutil, pyparsing, six) any 
> longer?

Yes. http://matplotlib.org/1.3.0/users/whats_new.html#new-setup-script
>
> Christoph
>
>
> On 5/29/2013 11:41 AM, Michael Droettboom wrote:
>> I'm pleased to announce the tagging of matplotlib-1.3.0rc1.
>>
>> Once the binaries from Christoph and Russell have been uploaded, I'll
>> make a broader announcement to get some testing of this in advance of
>> the final release.
>>
>> The tarball is available here:
>>
>> https://downloads.sourceforge.net/project/matplotlib/matplotlib/matplotlib-1.3.0rc1/matplotlib-1.3.0rc1.tar.gz 
>>
>>
>>
>> The documentation for this version is viewable here:
>>
>> http://matplotlib.org/1.3.0
>>
>> Thanks everyone for their hard work getting this out the door!
>>
>> Mike
>>

Hi,

minor issue: the tarball contains a lib\matplotlib.egg-info directory. 
The SOURCES.txt contains absolute paths (/usr/src/CXX/...) and therefore 
fails to build on my system. Deleting the lib\matplotlib.egg-info folder 
works.

Does the release announcement mention that Windows binaries won't 
include required dependencies (pytz, dateutil, pyparsing, six) any longer?

Christoph


On 5/29/2013 11:41 AM, Michael Droettboom wrote:
> I'm pleased to announce the tagging of matplotlib-1.3.0rc1.
>
> Once the binaries from Christoph and Russell have been uploaded, I'll
> make a broader announcement to get some testing of this in advance of
> the final release.
>
> The tarball is available here:
>
> https://downloads.sourceforge.net/project/matplotlib/matplotlib/matplotlib-1.3.0rc1/matplotlib-1.3.0rc1.tar.gz
>
>
> The documentation for this version is viewable here:
>
> http://matplotlib.org/1.3.0
>
> Thanks everyone for their hard work getting this out the door!
>
> Mike
>

I'm pleased to announce the tagging of matplotlib-1.3.0rc1.

Once the binaries from Christoph and Russell have been uploaded, I'll 
make a broader announcement to get some testing of this in advance of 
the final release.

The tarball is available here:

https://downloads.sourceforge.net/project/matplotlib/matplotlib/matplotlib-1.3.0rc1/matplotlib-1.3.0rc1.tar.gz

The documentation for this version is viewable here:

http://matplotlib.org/1.3.0

Thanks everyone for their hard work getting this out the door!

Mike

I am going to hold off one more day on making the release candidate.  
There are three blocker bugs that were discovered over the weekend and 
I'd like to give them a chance for review first:

#854 and #2061: These both have to do with problems with ignoring limits 
and can be fixed by the same changes

#2070: Incorrect bbox of text: This was another negative fallout from 
the refactor to have text pass the baseline coordinate to the backend by 
default.

#2072: PEP8 conformance test failing: This is due to an unexpected 
interaction between setuptools and Travis

There is an additional blocker bug:

#1719: pickling gridlines: I suspect this is just an 
environmental/installation issue on the part of the OP, so I'm confident 
moving forward without that resolved.

#2024: Update homepage image: I'll get to this later tonight or tomorrow 
as part of my customary release day documentation cleaning

Cheers,
Mike

On 05/24/2013 05:40 PM, Michael Droettboom wrote:
> I've gone ahead and created the 1.3.x branch on master.  This means that
> the feature freeze on master is effectively lifted.  Any PRs for 1.3.x
> should be milestoned as such before merging (and can be merged to either
> master or the 1.3.x branch).  That milestone will indicate to me what
> needs to be on the v1.3.x branch before making the release candidate
> early next week.
>
> Mike
>
> On 05/24/2013 01:38 PM, Michael Droettboom wrote:
>> The 1.3.0 release candidate tagging is scheduled for this coming Monday,
>> May 27.  Unfortunately, due to an oversight on my part, I forgot that is
>> a holiday, so I'm going to postpone it one day to Tuesday, May 28.  I
>> will be hoping to tag the release by 23:00 UTC that day.
>>
>> I think we're in really good shape for this release, given all of the
>> great work solving and triaging bugs that's been going on since the
>> feature freeze.
>>
>> I think all of the blocker bugs (except possibly #2061) are really close
>> to being resolved.  There are a number of issues tagged for 1.3.x that
>> may unfortunately need to get punted, but not a very large number.
>>
>> Question: Should I create a 1.3.x branch now?  The upside of doing that
>> is that development of post-1.3.x things can continue on master until
>> Tuesday, of course, and I think the pool of 1.3.x things is small enough
>> for that to make sense.  The downside, of course, is that any existing
>> pull requests against master will have to be manually merged to 1.3.x.
>> That shouldn't be a big deal, though, because we don't have too many of
>> them left and I can just pull the PR logs when I'm back at the office on
>> Tuesday to find out which ones need to be merged.  Any objections to
>> creating the branch now?
>>
>> Mike
>>
>> ------------------------------------------------------------------------------
>> Try New Relic Now & We'll Send You this Cool Shirt
>> New Relic is the only SaaS-based application performance monitoring service
>> that delivers powerful full stack analytics. Optimize and monitor your
>> browser, app, & servers with just a few lines of code. Try New Relic
>> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

I've gone ahead and created the 1.3.x branch on master.  This means that 
the feature freeze on master is effectively lifted.  Any PRs for 1.3.x 
should be milestoned as such before merging (and can be merged to either 
master or the 1.3.x branch).  That milestone will indicate to me what 
needs to be on the v1.3.x branch before making the release candidate 
early next week.

Mike

On 05/24/2013 01:38 PM, Michael Droettboom wrote:
> The 1.3.0 release candidate tagging is scheduled for this coming Monday,
> May 27.  Unfortunately, due to an oversight on my part, I forgot that is
> a holiday, so I'm going to postpone it one day to Tuesday, May 28.  I
> will be hoping to tag the release by 23:00 UTC that day.
>
> I think we're in really good shape for this release, given all of the
> great work solving and triaging bugs that's been going on since the
> feature freeze.
>
> I think all of the blocker bugs (except possibly #2061) are really close
> to being resolved.  There are a number of issues tagged for 1.3.x that
> may unfortunately need to get punted, but not a very large number.
>
> Question: Should I create a 1.3.x branch now?  The upside of doing that
> is that development of post-1.3.x things can continue on master until
> Tuesday, of course, and I think the pool of 1.3.x things is small enough
> for that to make sense.  The downside, of course, is that any existing
> pull requests against master will have to be manually merged to 1.3.x.
> That shouldn't be a big deal, though, because we don't have too many of
> them left and I can just pull the PR logs when I'm back at the office on
> Tuesday to find out which ones need to be merged.  Any objections to
> creating the branch now?
>
> Mike
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

The 1.3.0 release candidate tagging is scheduled for this coming Monday, 
May 27.  Unfortunately, due to an oversight on my part, I forgot that is 
a holiday, so I'm going to postpone it one day to Tuesday, May 28.  I 
will be hoping to tag the release by 23:00 UTC that day.

I think we're in really good shape for this release, given all of the 
great work solving and triaging bugs that's been going on since the 
feature freeze.

I think all of the blocker bugs (except possibly #2061) are really close 
to being resolved.  There are a number of issues tagged for 1.3.x that 
may unfortunately need to get punted, but not a very large number.

Question: Should I create a 1.3.x branch now?  The upside of doing that 
is that development of post-1.3.x things can continue on master until 
Tuesday, of course, and I think the pool of 1.3.x things is small enough 
for that to make sense.  The downside, of course, is that any existing 
pull requests against master will have to be manually merged to 1.3.x.  
That shouldn't be a big deal, though, because we don't have too many of 
them left and I can just pull the PR logs when I'm back at the office on 
Tuesday to find out which ones need to be merged.  Any objections to 
creating the branch now?

Mike

For what it is worth, we attacked this problem about four years ago at my
work.  We just implemented a simple formatter.  A locator can also be done
in a similar manner if that is desired.

This is not exactly is a perfect solution, but it worked really well for us.

class ScaledFormatter( ticker.Formatter ):
   """: Takes an exisiting formatter and scales the value by a specified
amount.
   """
   def __init__( self, scale, formatter ):
      """Initialize the scaled formatter.

      = INPUT VARIABLES
      - scale     The scale factor to apply to the values specified by the
                  other formatter.
      - formatter Another matplotlib formatter to use for formatting the
                  data labels.
      """
      self.scale = scale
      self.formatter = formatter

   def __call__( self, x, pos = None ):
      'Return the format for tick val x at position pos'
      # get the string form of the value
      valueStr = self.formatter( x, pos )

      if len(valueStr) == 0:
         return ''

      # remove the unicode hyphen
      valueStr = valueStr.replace( u'\u2212', '-' )

      # convert to a float
      value = float( valueStr )

      # now scale the value
      value *= self.scale

      # convert ot a Unicode string
      s = unicode( value )

      # add the unicode hyphen
      s.replace( '-', u'\u2212' )

      return s

   def set_locs( self, locs ):
      'Make sure the encompassed formatter get these set.'
      ticker.Formatter.set_locs( self, locs )
      self.formatter.set_locs( locs )

   def set_axis( self, axis ):
      'Make sure the encompassed formatter get these set.'
      ticker.Formatter.set_axis( self, axis )
      self.formatter.set_axis( axis )

   def set_view_interval( self, vmin, vmax ):
      'Make sure the encompassed formatter get these set.'
      ticker.Formatter.set_view_interval( self, vmin, vmax )
      self.formatter.set_view_interval( vmin, vmax )

   def set_data_interval( self, vmin, vmax ):
      'Make sure the encompassed formatter get these set.'
      ticker.Formatter.set_data_interval( self, vmin, vmax )
      self.formatter.set_data_interval( vmin, vmax )

   def set_bounds( self, vmin, vmax ):
      'Make sure the encompassed formatter get these set.'
      ticker.Formatter.set_bounds( self, vmin, vmax )
      self.formatter.set_bounds( vmin, vmax )


--James

> -----Original Message-----
> From: Thomas Caswell [mailto:tca...@gm...]
> Sent: Thursday, May 23, 2013 5:26 PM
> To: mat...@li...
> Subject: [matplotlib-devel] adding second formatter/locater set to axes
> objects
> 
> A question I have seen go by twice on SO is how to add a tick marks to the
> top/right of a plot which are re-scaled version of the values on the
> bottom/lefit axis (ex km/h on the left and mph on the right).  My
> understanding of the best way to do this is to use twin* and then keep the
> range of the two axes in sync by hand.
> 
> I am proposing adding at set of alternate formatters/locators to the
`axis`
> objects which if they exist are used for the top/right labels.
> Before I dive too deep into this, I want to check that a) there isn't a
better
> way to do this that I do not know and b) if this sounds like a reasonable
> approach.
> 
> Tom
> 
> --
> Thomas Caswell
> tca...@gm...
> 
>
----------------------------------------------------------------------------
--
> Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only
SaaS-
> based application performance monitoring service that delivers powerful
full
> stack analytics. Optimize and monitor your browser, app, & servers with
just
> a few lines of code. Try New Relic and get this awesome Nerd Life shirt!
> http://p.sf.net/sfu/newrelic_d2d_may
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Unfortunately, the panning/zooming code is strewn about through the 
backends and in the toolbar, when it really should be on the axes itself.

#1849 is underway to address that (and will probably become a MEP before 
a final implementation is made), and I'd say adding scrollwheel zooming 
to that plan would be the best long term course of action.  Not that we 
couldn't take a transitional step if an obvious one exists...

Mike

On 05/23/2013 08:35 PM, Thomas Caswell wrote:
> A while ago I wrote a code snippet to generate and connect a function
> to enable scroll wheel zooming of axes.
> (https://gist.github.com/tacaswell/3144287)
>
> Is this worth cleaning up and getting into the repository?  If so,
> where should it go?
>
> Tom
>
>
> --
> Thomas Caswell
> tca...@gm...
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

A while ago I wrote a code snippet to generate and connect a function
to enable scroll wheel zooming of axes.
(https://gist.github.com/tacaswell/3144287)

Is this worth cleaning up and getting into the repository?  If so,
where should it go?

Tom


--
Thomas Caswell
tca...@gm...

A question I have seen go by twice on SO is how to add a tick marks to
the top/right of a plot which are re-scaled version of the values on
the bottom/lefit axis (ex km/h on the left and mph on the right).  My
understanding of the best way to do this is to use twin* and then keep
the range of the two axes in sync by hand.

I am proposing adding at set of alternate formatters/locators to the
`axis` objects which if they exist are used for the top/right labels.
Before I dive too deep into this, I want to check that a) there isn't
a better way to do this that I do not know and b) if this sounds like
a reasonable approach.

Tom

--
Thomas Caswell
tca...@gm...

Wx users on OSX: help in testing this ASAP would be appreciated.  It 
would be ideal to test it with both wx 2.8 and 2.9--the more 
configuration combinations, the better.

You may want to look also at 
https://github.com/matplotlib/matplotlib/pull/1995, which is work 
towards support of the new Phoenix version of wxpython.

Thanks.

Eric


-------- Original Message --------
Subject: 	Re: [matplotlib] Make wx and wxagg work with wx 2.9.x on Mac.
(#2004)
Date: 	Mon, 20 May 2013 12:48:23 -0700
From: 	Michael Droettboom <not...@gi...>
Reply-To: 	matplotlib/matplotlib
<rep...@re...>
To: 	matplotlib/matplotlib <mat...@no...>
CC: 	Eric Firing <ef...@ha...>



As a data point, this works fine with wx 2.8.12 on my Linux box.

Any testers with wx 2.8 on their Mac? It seems harmless enough...

—
Reply to this email directly or view it on GitHub
<https://github.com/matplotlib/matplotlib/pull/2004#issuecomment-18168325>.

Thanks, Tony.

Again, I'm wondering if someone can set this up (perhaps based on the 
content on our wiki).  I still don't have a working account there (I 
think because of the unusual way I had to register).

Mike

On 05/20/2013 04:25 PM, Tony Yu wrote:
> Hi all,
>
> Since you're already discussing a SciPy BoF [1], it might be a good 
> idea to discuss a sprint (which was discussed briefly a couple of 
> months ago [2]).
>
> http://conference.scipy.org/scipy2013/sprints.php
>
> Unfortunately, I might not be able to participate (since I may be 
> committed to another sprint), but it'd be a good idea to start 
> advertising the sprint soon in order to attract participants.
>
> Cheers,
> -Tony
>
> [1] 
> http://www.mail-archive.com/mat...@li.../msg10017.html
> [2] 
> http://www.mail-archive.com/mat...@li.../msg09951.html
>
>
> ------------------------------------------------------------------------------
> AlienVault Unified Security Management (USM) platform delivers complete
> security visibility with the essential security capabilities. Easily and
> efficiently configure, manage, and operate all of your security controls
> from a single console and one unified framework. Download a free trial.
> http://p.sf.net/sfu/alienvault_d2d
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Hi all,

Since you're already discussing a SciPy BoF [1], it might be a good idea to
discuss a sprint (which was discussed briefly a couple of months ago [2]).

http://conference.scipy.org/scipy2013/sprints.php

Unfortunately, I might not be able to participate (since I may be committed
to another sprint), but it'd be a good idea to start advertising the sprint
soon in order to attract participants.

Cheers,
-Tony

[1]
http://www.mail-archive.com/mat...@li.../msg10017.html
[2]
http://www.mail-archive.com/mat...@li.../msg09951.html

On Wed, May 15, 2013 at 10:12 PM, Damon McDougall <dam...@gm...
> wrote:

>
>
>
> On Wed, May 15, 2013 at 8:11 PM, Michael Droettboom <md...@st...>wrote:
>
>>  I think discussing existing MEPs and proposing new MEPs would be a
>> great use of the time.
>>
>> 1) Matplotlib enhancement proposal discussion
>> 2) A chance to discuss ongoing and new matplotlib enhancement proposals
>> (MEPs).  MEPs are posted on the matplotlib development wiki here:
>>
>> https://github.com/matplotlib/matplotlib/wiki
>>
>> Participants who wish to comment or help with existing MEPs or propose
>> entirely new MEPs are welcome.
>> 3) Panelist suggestions: (I'm not sure exactly what is meant by this, but
>> I think any of us on matplotlib-devel who are attending would be good
>> candidates)
>>
>
> Ben has prior experience of this, so I'm happy to put you both, and
> perhaps Phil too, and then that gives three plus the moderator.
>
> Phil, is that alright with you?
>
> Happy to add others if someone specifically wants to step up to the
> crease/plate.
>
>  4) I'm certainly willing to moderate, but I'm also happy to hand the
>> reigns to you, Damon, for taking the initiative.
>>
>
> Sure, I don't mind.
>
> I envisage the discussion aspect being useful, especially if a fair few
> people turn up with ideas and opinions.  The advantage of github is that
> anything we take away from this can be pencilled into the wiki for future
> reference.  It'd also be a good place to stick action items for the
> developers.
>
> Ben, what do you think?
>
> I will complete the web from tomorrow.
>

Done.  Phil is happy being on the panel.

Cheers for the suggestions, Mike.


>
>
>>
>> Mike
>>
>>
>> On 05/15/2013 05:57 PM, Damon McDougall wrote:
>>
>>
>>
>>
>> On Tue, May 14, 2013 at 10:05 AM, Michael Droettboom <md...@st...>wrote:
>>
>>>  Great idea.  I'm having trouble creating the entry -- I think there's
>>> something incorrect about my account.  Are you able to?
>>>
>>
>>  Yes, I am able to.  I'll happily do it.  I need the following
>> information to create a BoF:
>>
>>  1) BoF subject
>> 2) BoF summary (150) words
>> 3) Panelist suggestions
>> 4) A name of someone who is willing to moderate
>>
>>  I'm not really sure what to write here.  We could basically make this
>> an arena in which people can throw around MEP ideas.  What do you think
>> about that?
>>
>>
>>>
>>> Mike
>>>
>>>
>>> On 05/13/2013 08:21 PM, Damon McDougall wrote:
>>>
>>>  All,
>>>
>>>  Here's the site where we can suggest a BoF at the SciPy conference:
>>> http://conference.scipy.org/scipy2013/bofs.php?utm_source=buffer&utm_medium=twitter&utm_campaign=Buffer&utm_content=bufferce96b
>>>
>>>  We should do an mpl BoF and toss around ideas.
>>>
>>>  Best wishes,
>>> Damon
>>>
>>>  --
>>> Damon McDougall
>>> http://www.damon-is-a-geek.com
>>> Institute for Computational Engineering Sciences
>>> 201 E. 24th St.
>>> Stop C0200
>>> The University of Texas at Austin
>>> Austin, TX 78712-1229
>>>
>>>
>>>  ------------------------------------------------------------------------------
>>> AlienVault Unified Security Management (USM) platform delivers complete
>>> security visibility with the essential security capabilities. Easily and
>>> efficiently configure, manage, and operate all of your security controls
>>> from a single console and one unified framework. Download a free trial.http://p.sf.net/sfu/alienvault_d2d
>>>
>>>
>>>
>>> _______________________________________________
>>> Matplotlib-devel mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> AlienVault Unified Security Management (USM) platform delivers complete
>>> security visibility with the essential security capabilities. Easily and
>>> efficiently configure, manage, and operate all of your security controls
>>> from a single console and one unified framework. Download a free trial.
>>> http://p.sf.net/sfu/alienvault_d2d
>>> _______________________________________________
>>> Matplotlib-devel mailing list
>>> Mat...@li...
>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>>
>>>
>>
>>
>>  --
>> Damon McDougall
>> http://www.damon-is-a-geek.com
>> Institute for Computational Engineering Sciences
>> 201 E. 24th St.
>> Stop C0200
>> The University of Texas at Austin
>> Austin, TX 78712-1229
>>
>>
>>
>
>
> --
> Damon McDougall
> http://www.damon-is-a-geek.com
> Institute for Computational Engineering Sciences
> 201 E. 24th St.
> Stop C0200
> The University of Texas at Austin
> Austin, TX 78712-1229
>



-- 
Damon McDougall
http://www.damon-is-a-geek.com
Institute for Computational Engineering Sciences
201 E. 24th St.
Stop C0200
The University of Texas at Austin
Austin, TX 78712-1229

On Wed, May 15, 2013 at 8:11 PM, Michael Droettboom <md...@st...> wrote:

>  I think discussing existing MEPs and proposing new MEPs would be a great
> use of the time.
>
> 1) Matplotlib enhancement proposal discussion
> 2) A chance to discuss ongoing and new matplotlib enhancement proposals
> (MEPs).  MEPs are posted on the matplotlib development wiki here:
>
> https://github.com/matplotlib/matplotlib/wiki
>
> Participants who wish to comment or help with existing MEPs or propose
> entirely new MEPs are welcome.
> 3) Panelist suggestions: (I'm not sure exactly what is meant by this, but
> I think any of us on matplotlib-devel who are attending would be good
> candidates)
>

Ben has prior experience of this, so I'm happy to put you both, and perhaps
Phil too, and then that gives three plus the moderator.

Phil, is that alright with you?

Happy to add others if someone specifically wants to step up to the
crease/plate.

4) I'm certainly willing to moderate, but I'm also happy to hand the reigns
> to you, Damon, for taking the initiative.
>

Sure, I don't mind.

I envisage the discussion aspect being useful, especially if a fair few
people turn up with ideas and opinions.  The advantage of github is that
anything we take away from this can be pencilled into the wiki for future
reference.  It'd also be a good place to stick action items for the
developers.

Ben, what do you think?

I will complete the web from tomorrow.


>
> Mike
>
>
> On 05/15/2013 05:57 PM, Damon McDougall wrote:
>
>
>
>
> On Tue, May 14, 2013 at 10:05 AM, Michael Droettboom <md...@st...>wrote:
>
>>  Great idea.  I'm having trouble creating the entry -- I think there's
>> something incorrect about my account.  Are you able to?
>>
>
>  Yes, I am able to.  I'll happily do it.  I need the following
> information to create a BoF:
>
>  1) BoF subject
> 2) BoF summary (150) words
> 3) Panelist suggestions
> 4) A name of someone who is willing to moderate
>
>  I'm not really sure what to write here.  We could basically make this an
> arena in which people can throw around MEP ideas.  What do you think about
> that?
>
>
>>
>> Mike
>>
>>
>> On 05/13/2013 08:21 PM, Damon McDougall wrote:
>>
>>  All,
>>
>>  Here's the site where we can suggest a BoF at the SciPy conference:
>> http://conference.scipy.org/scipy2013/bofs.php?utm_source=buffer&utm_medium=twitter&utm_campaign=Buffer&utm_content=bufferce96b
>>
>>  We should do an mpl BoF and toss around ideas.
>>
>>  Best wishes,
>> Damon
>>
>>  --
>> Damon McDougall
>> http://www.damon-is-a-geek.com
>> Institute for Computational Engineering Sciences
>> 201 E. 24th St.
>> Stop C0200
>> The University of Texas at Austin
>> Austin, TX 78712-1229
>>
>>
>>  ------------------------------------------------------------------------------
>> AlienVault Unified Security Management (USM) platform delivers complete
>> security visibility with the essential security capabilities. Easily and
>> efficiently configure, manage, and operate all of your security controls
>> from a single console and one unified framework. Download a free trial.http://p.sf.net/sfu/alienvault_d2d
>>
>>
>>
>> _______________________________________________
>> Matplotlib-devel mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> AlienVault Unified Security Management (USM) platform delivers complete
>> security visibility with the essential security capabilities. Easily and
>> efficiently configure, manage, and operate all of your security controls
>> from a single console and one unified framework. Download a free trial.
>> http://p.sf.net/sfu/alienvault_d2d
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>
>>
>
>
>  --
> Damon McDougall
> http://www.damon-is-a-geek.com
> Institute for Computational Engineering Sciences
> 201 E. 24th St.
> Stop C0200
> The University of Texas at Austin
> Austin, TX 78712-1229
>
>
>


-- 
Damon McDougall
http://www.damon-is-a-geek.com
Institute for Computational Engineering Sciences
201 E. 24th St.
Stop C0200
The University of Texas at Austin
Austin, TX 78712-1229

I think discussing existing MEPs and proposing new MEPs would be a great 
use of the time.

1) Matplotlib enhancement proposal discussion
2) A chance to discuss ongoing and new matplotlib enhancement proposals 
(MEPs).  MEPs are posted on the matplotlib development wiki here:

https://github.com/matplotlib/matplotlib/wiki

Participants who wish to comment or help with existing MEPs or propose 
entirely new MEPs are welcome.
3) Panelist suggestions: (I'm not sure exactly what is meant by this, 
but I think any of us on matplotlib-devel who are attending would be 
good candidates)
4) I'm certainly willing to moderate, but I'm also happy to hand the 
reigns to you, Damon, for taking the initiative.

Mike

On 05/15/2013 05:57 PM, Damon McDougall wrote:
>
>
>
> On Tue, May 14, 2013 at 10:05 AM, Michael Droettboom <md...@st... 
> <mailto:md...@st...>> wrote:
>
>     Great idea.  I'm having trouble creating the entry -- I think
>     there's something incorrect about my account.  Are you able to?
>
>
> Yes, I am able to.  I'll happily do it.  I need the following 
> information to create a BoF:
>
> 1) BoF subject
> 2) BoF summary (150) words
> 3) Panelist suggestions
> 4) A name of someone who is willing to moderate
>
> I'm not really sure what to write here.  We could basically make this 
> an arena in which people can throw around MEP ideas.  What do you 
> think about that?
>
>
>     Mike
>
>
>     On 05/13/2013 08:21 PM, Damon McDougall wrote:
>>     All,
>>
>>     Here's the site where we can suggest a BoF at the SciPy
>>     conference:
>>     http://conference.scipy.org/scipy2013/bofs.php?utm_source=buffer&utm_medium=twitter&utm_campaign=Buffer&utm_content=bufferce96b
>>
>>     We should do an mpl BoF and toss around ideas.
>>
>>     Best wishes,
>>     Damon
>>
>>     -- 
>>     Damon McDougall
>>     http://www.damon-is-a-geek.com
>>     Institute for Computational Engineering Sciences
>>     201 E. 24th St.
>>     Stop C0200
>>     The University of Texas at Austin
>>     Austin, TX 78712-1229
>>
>>
>>     ------------------------------------------------------------------------------
>>     AlienVault Unified Security Management (USM) platform delivers complete
>>     security visibility with the essential security capabilities. Easily and
>>     efficiently configure, manage, and operate all of your security controls
>>     from a single console and one unified framework. Download a free trial.
>>     http://p.sf.net/sfu/alienvault_d2d
>>
>>
>>     _______________________________________________
>>     Matplotlib-devel mailing list
>>     Mat...@li...  <mailto:Mat...@li...>
>>     https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
>     ------------------------------------------------------------------------------
>     AlienVault Unified Security Management (USM) platform delivers
>     complete
>     security visibility with the essential security capabilities.
>     Easily and
>     efficiently configure, manage, and operate all of your security
>     controls
>     from a single console and one unified framework. Download a free
>     trial.
>     http://p.sf.net/sfu/alienvault_d2d
>     _______________________________________________
>     Matplotlib-devel mailing list
>     Mat...@li...
>     <mailto:Mat...@li...>
>     https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
>
>
> -- 
> Damon McDougall
> http://www.damon-is-a-geek.com
> Institute for Computational Engineering Sciences
> 201 E. 24th St.
> Stop C0200
> The University of Texas at Austin
> Austin, TX 78712-1229

On Wed, May 15, 2013 at 5:57 PM, Damon McDougall
<dam...@gm...>wrote:

>
>
>
> On Tue, May 14, 2013 at 10:05 AM, Michael Droettboom <md...@st...>wrote:
>
>>  Great idea.  I'm having trouble creating the entry -- I think there's
>> something incorrect about my account.  Are you able to?
>>
>
> Yes, I am able to.  I'll happily do it.  I need the following information
> to create a BoF:
>
> 1) BoF subject
> 2) BoF summary (150) words
> 3) Panelist suggestions
> 4) A name of someone who is willing to moderate
>
> I'm not really sure what to write here.  We could basically make this an
> arena in which people can throw around MEP ideas.  What do you think about
> that?
>

That is essentially what we did last year.  Bounced a lot of ideas off of
each other during that.  The follow-through on that though, left a lot to
be desired (mea culpa).

Ben Root

On Tue, May 14, 2013 at 10:05 AM, Michael Droettboom <md...@st...>wrote:

>  Great idea.  I'm having trouble creating the entry -- I think there's
> something incorrect about my account.  Are you able to?
>

Yes, I am able to.  I'll happily do it.  I need the following information
to create a BoF:

1) BoF subject
2) BoF summary (150) words
3) Panelist suggestions
4) A name of someone who is willing to moderate

I'm not really sure what to write here.  We could basically make this an
arena in which people can throw around MEP ideas.  What do you think about
that?


>
> Mike
>
>
> On 05/13/2013 08:21 PM, Damon McDougall wrote:
>
> All,
>
>  Here's the site where we can suggest a BoF at the SciPy conference:
> http://conference.scipy.org/scipy2013/bofs.php?utm_source=buffer&utm_medium=twitter&utm_campaign=Buffer&utm_content=bufferce96b
>
>  We should do an mpl BoF and toss around ideas.
>
>  Best wishes,
> Damon
>
>  --
> Damon McDougall
> http://www.damon-is-a-geek.com
> Institute for Computational Engineering Sciences
> 201 E. 24th St.
> Stop C0200
> The University of Texas at Austin
> Austin, TX 78712-1229
>
>
> ------------------------------------------------------------------------------
> AlienVault Unified Security Management (USM) platform delivers complete
> security visibility with the essential security capabilities. Easily and
> efficiently configure, manage, and operate all of your security controls
> from a single console and one unified framework. Download a free trial.http://p.sf.net/sfu/alienvault_d2d
>
>
>
> _______________________________________________
> Matplotlib-devel mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
>
>
> ------------------------------------------------------------------------------
> AlienVault Unified Security Management (USM) platform delivers complete
> security visibility with the essential security capabilities. Easily and
> efficiently configure, manage, and operate all of your security controls
> from a single console and one unified framework. Download a free trial.
> http://p.sf.net/sfu/alienvault_d2d
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>


-- 
Damon McDougall
http://www.damon-is-a-geek.com
Institute for Computational Engineering Sciences
201 E. 24th St.
Stop C0200
The University of Texas at Austin
Austin, TX 78712-1229

Great idea.  I'm having trouble creating the entry -- I think there's 
something incorrect about my account.  Are you able to?

Mike

On 05/13/2013 08:21 PM, Damon McDougall wrote:
> All,
>
> Here's the site where we can suggest a BoF at the SciPy conference: 
> http://conference.scipy.org/scipy2013/bofs.php?utm_source=buffer&utm_medium=twitter&utm_campaign=Buffer&utm_content=bufferce96b
>
> We should do an mpl BoF and toss around ideas.
>
> Best wishes,
> Damon
>
> -- 
> Damon McDougall
> http://www.damon-is-a-geek.com
> Institute for Computational Engineering Sciences
> 201 E. 24th St.
> Stop C0200
> The University of Texas at Austin
> Austin, TX 78712-1229
>
>
> ------------------------------------------------------------------------------
> AlienVault Unified Security Management (USM) platform delivers complete
> security visibility with the essential security capabilities. Easily and
> efficiently configure, manage, and operate all of your security controls
> from a single console and one unified framework. Download a free trial.
> http://p.sf.net/sfu/alienvault_d2d
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

All,

Here's the site where we can suggest a BoF at the SciPy conference:
http://conference.scipy.org/scipy2013/bofs.php?utm_source=buffer&utm_medium=twitter&utm_campaign=Buffer&utm_content=bufferce96b

We should do an mpl BoF and toss around ideas.

Best wishes,
Damon

-- 
Damon McDougall
http://www.damon-is-a-geek.com
Institute for Computational Engineering Sciences
201 E. 24th St.
Stop C0200
The University of Texas at Austin
Austin, TX 78712-1229

Yeah -- I think it's a known bug (though not sure if it's in the tracker).

The solution is probably to do something like the compound path 
rendering you (Phil) have experimented with, or, perhaps more easily, 
rendering without alpha to a temporary image buffer and then compositing 
it with alpha in a single step.

Mike

On 05/13/2013 10:14 AM, Benjamin Root wrote:
>
>
>
> On Mon, May 13, 2013 at 9:58 AM, Phil Elson <pel...@gm... 
> <mailto:pel...@gm...>> wrote:
>
>     I can't work out if I'm having a brain block or it really can't be
>     done, but I'm trying to produce a pcolormesh with alpha without
>     the nasty edges seen in the attached image
>
>
> The issue is that the quads are overlapping just slightly.  Any 
> solution to this has to be to make them not overlap at all.  This is 
> an old problem, to be sure.
>
> Ben Root
>
>
>
>
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and
> their applications. This 200-page book is written by three acclaimed
> leaders in the field. The early access version is available now.
> Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

On Mon, May 13, 2013 at 9:58 AM, Phil Elson <pel...@gm...> wrote:

> I can't work out if I'm having a brain block or it really can't be done,
> but I'm trying to produce a pcolormesh with alpha without the nasty edges
> seen in the attached image
>
>
The issue is that the quads are overlapping just slightly.  Any solution to
this has to be to make them not overlap at all.  This is an old problem, to
be sure.

Ben Root

Today is the day scheduled to be the feature freeze for 1.3.0.

We should get all PRs that are close to ready for inclusion tagged as 
1.3.0 (or 1.3.x blocker if they represent a serious bug).

At the moment, we have 8 blocker bugs, of which only 3 of which seem to 
require much much effort at this point.  We have 27 non-blocker PRs.

I probably won't create a 1.3.x branch just yet, so things for 1.3.0 can 
just get merged into master for now, and things that are for post-1.3.0 
should be held off for the time being.  Once we have the PRs down to a 
manageable number, I will create a branch and let everyone know here.

Thanks again for all your help, and I look forward to seeing you at Scipy!

Mike