From matthew.brett at gmail.com  Tue Aug  1 06:53:42 2017
From: matthew.brett at gmail.com (Matthew Brett)
Date: Tue, 1 Aug 2017 11:53:42 +0100
Subject: [Matplotlib-devel] mpl 2.1 + subprocess32
In-Reply-To: <CAA48SF_OfR3JUs9bOnOK4qZB_LzRY9NTU1BAPAA9A8buzqOiGg@mail.gmail.com>
References: <CAA48SF_OfR3JUs9bOnOK4qZB_LzRY9NTU1BAPAA9A8buzqOiGg@mail.gmail.com>
Message-ID: <CAH6Pt5pBq9mVVEMJJCaHcLydQxswLpUE5XY9=J5e75p7EaMS5Q@mail.gmail.com>

Hi,

On Sun, Jul 30, 2017 at 4:20 AM, Thomas Caswell <tcaswell at gmail.com> wrote:
> Folks,
>
> With 2.0 we picked up subprocess32
> (https://pypi.python.org/pypi/subprocess32/) to be able to use the improved
> subprocess module, however this has caused several problem with [1, 2] due
> to a bug in the release version and wheels not being published on pypi.  The
> bug is reportedly fixed on master [4] and Mathew Brett has provided them
> with wheel-building machinery [3], but there has been no motion on that
> sense May.
>
> I think our options are:
>
>  - document the known issues (meaning wheel-installing mac users have to
> install xcode and people on very old linux need to install from the
> subprocess32 master branch, and general linux users need to have a gcc
> installed)
>  - hope subprocess32 does a release and adopt Matthew's wheels in the next
> month
>  - vendor the master branch (is there a way we can do this _just_ for the
> wheels without actually vendoring it in the source tree?)
>  - change dependencies
>
> After 2.1 we won't have the last option until 2.2 so if we want to do that,
> it needs to be done this month.
>
> If anyone is motivated to work on changing the dependency, please do so
> otherwise I am inclined to go with the first option.

I'd be really sad if we went for option 1.  I'm particularly
interested in installations for new users, and these are often a) via
pip with b) Python 2.7 and b) without a compiler set up.  So this is a
painful hurdle, often for those least adapted to clear it...

I'm happy to do donkey work if someone can point me the way forward to
replacing the dependency.

Cheers,

Matthew

From jenshnielsen at gmail.com  Tue Aug  1 07:30:19 2017
From: jenshnielsen at gmail.com (Jens Nielsen)
Date: Tue, 01 Aug 2017 11:30:19 +0000
Subject: [Matplotlib-devel] mpl 2.1 + subprocess32
In-Reply-To: <CAH6Pt5pBq9mVVEMJJCaHcLydQxswLpUE5XY9=J5e75p7EaMS5Q@mail.gmail.com>
References: <CAA48SF_OfR3JUs9bOnOK4qZB_LzRY9NTU1BAPAA9A8buzqOiGg@mail.gmail.com>
 <CAH6Pt5pBq9mVVEMJJCaHcLydQxswLpUE5XY9=J5e75p7EaMS5Q@mail.gmail.com>
Message-ID: <CAM-Pw01qURDKXWkJNmHKyRfY-1XKspcYF5MrjBmsiZ6qYCwcAA@mail.gmail.com>

Another possible solution could be to drop the dependency on subprocess32
but retain the use of it in *compat/subprocess.py *and fallback to regular
subprocess if not found and then document that if a user sees
https://github.com/matplotlib/matplotlib/issues/5314 they should install
subprocess32. There should be few issues with dropping the dependency on
Linux as the main bug it resolves is OSX specific.

Furthermore 5314 should have been resolved in python 2.7.12 so the surface
for seeing the bug on OSX is getting smaller. Unfortunately Apple still
ships python 2.7.10 as the default python on OSX in Sierra (10.12)

Jens

On Tue, 1 Aug 2017 at 12:54 Matthew Brett <matthew.brett at gmail.com> wrote:

> Hi,
>
> On Sun, Jul 30, 2017 at 4:20 AM, Thomas Caswell <tcaswell at gmail.com>
> wrote:
> > Folks,
> >
> > With 2.0 we picked up subprocess32
> > (https://pypi.python.org/pypi/subprocess32/) to be able to use the
> improved
> > subprocess module, however this has caused several problem with [1, 2]
> due
> > to a bug in the release version and wheels not being published on pypi.
> The
> > bug is reportedly fixed on master [4] and Mathew Brett has provided them
> > with wheel-building machinery [3], but there has been no motion on that
> > sense May.
> >
> > I think our options are:
> >
> >  - document the known issues (meaning wheel-installing mac users have to
> > install xcode and people on very old linux need to install from the
> > subprocess32 master branch, and general linux users need to have a gcc
> > installed)
> >  - hope subprocess32 does a release and adopt Matthew's wheels in the
> next
> > month
> >  - vendor the master branch (is there a way we can do this _just_ for the
> > wheels without actually vendoring it in the source tree?)
> >  - change dependencies
> >
> > After 2.1 we won't have the last option until 2.2 so if we want to do
> that,
> > it needs to be done this month.
> >
> > If anyone is motivated to work on changing the dependency, please do so
> > otherwise I am inclined to go with the first option.
>
> I'd be really sad if we went for option 1.  I'm particularly
> interested in installations for new users, and these are often a) via
> pip with b) Python 2.7 and b) without a compiler set up.  So this is a
> painful hurdle, often for those least adapted to clear it...
>
> I'm happy to do donkey work if someone can point me the way forward to
> replacing the dependency.
>
> Cheers,
>
> Matthew
> _______________________________________________
> 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/20170801/b8dff0e4/attachment.html>

From matthew.brett at gmail.com  Tue Aug  1 07:57:16 2017
From: matthew.brett at gmail.com (Matthew Brett)
Date: Tue, 1 Aug 2017 12:57:16 +0100
Subject: [Matplotlib-devel] mpl 2.1 + subprocess32
In-Reply-To: <CAM-Pw01qURDKXWkJNmHKyRfY-1XKspcYF5MrjBmsiZ6qYCwcAA@mail.gmail.com>
References: <CAA48SF_OfR3JUs9bOnOK4qZB_LzRY9NTU1BAPAA9A8buzqOiGg@mail.gmail.com>
 <CAH6Pt5pBq9mVVEMJJCaHcLydQxswLpUE5XY9=J5e75p7EaMS5Q@mail.gmail.com>
 <CAM-Pw01qURDKXWkJNmHKyRfY-1XKspcYF5MrjBmsiZ6qYCwcAA@mail.gmail.com>
Message-ID: <CAH6Pt5rC_e+4V+sMCQZ+W89i_=c0ij3UqTfRVekXpjDcpqCOeQ@mail.gmail.com>

On Tue, Aug 1, 2017 at 12:30 PM, Jens Nielsen <jenshnielsen at gmail.com> wrote:
> Another possible solution could be to drop the dependency on subprocess32
> but retain the use of it in compat/subprocess.py and fallback to regular
> subprocess if not found and then document that if a user sees
> https://github.com/matplotlib/matplotlib/issues/5314 they should install
> subprocess32. There should be few issues with dropping the dependency on
> Linux as the main bug it resolves is OSX specific.
>
> Furthermore 5314 should have been resolved in python 2.7.12 so the surface
> for seeing the bug on OSX is getting smaller.

Excellent news!

> Unfortunately Apple still
> ships python 2.7.10 as the default python on OSX in Sierra (10.12)

The last time I looked into this, a default install of matplotlib into
system Python gets ignored because of the extra libraries "feature"

https://github.com/MacPython/wiki/wiki/Which-Python#system-python-and-extra-python-packages

Is that no longer true?

Cheers,

Matthew

From jenshnielsen at gmail.com  Tue Aug  1 08:06:25 2017
From: jenshnielsen at gmail.com (Jens Nielsen)
Date: Tue, 01 Aug 2017 12:06:25 +0000
Subject: [Matplotlib-devel] mpl 2.1 + subprocess32
In-Reply-To: <CAH6Pt5rC_e+4V+sMCQZ+W89i_=c0ij3UqTfRVekXpjDcpqCOeQ@mail.gmail.com>
References: <CAA48SF_OfR3JUs9bOnOK4qZB_LzRY9NTU1BAPAA9A8buzqOiGg@mail.gmail.com>
 <CAH6Pt5pBq9mVVEMJJCaHcLydQxswLpUE5XY9=J5e75p7EaMS5Q@mail.gmail.com>
 <CAM-Pw01qURDKXWkJNmHKyRfY-1XKspcYF5MrjBmsiZ6qYCwcAA@mail.gmail.com>
 <CAH6Pt5rC_e+4V+sMCQZ+W89i_=c0ij3UqTfRVekXpjDcpqCOeQ@mail.gmail.com>
Message-ID: <CAM-Pw01uejQdoC8LCm8dF8pxuMYxC1Vhb=ekSuo-QJAytH39Zg@mail.gmail.com>

I think it still true, I guess you can hack sys.path but perhaps we don't
need to worry about that

On Tue, 1 Aug 2017 at 13:57 Matthew Brett <matthew.brett at gmail.com> wrote:

> On Tue, Aug 1, 2017 at 12:30 PM, Jens Nielsen <jenshnielsen at gmail.com>
> wrote:
> > Another possible solution could be to drop the dependency on subprocess32
> > but retain the use of it in compat/subprocess.py and fallback to regular
> > subprocess if not found and then document that if a user sees
> > https://github.com/matplotlib/matplotlib/issues/5314 they should install
> > subprocess32. There should be few issues with dropping the dependency on
> > Linux as the main bug it resolves is OSX specific.
> >
> > Furthermore 5314 should have been resolved in python 2.7.12 so the
> surface
> > for seeing the bug on OSX is getting smaller.
>
> Excellent news!
>
> > Unfortunately Apple still
> > ships python 2.7.10 as the default python on OSX in Sierra (10.12)
>
> The last time I looked into this, a default install of matplotlib into
> system Python gets ignored because of the extra libraries "feature"
>
>
> https://github.com/MacPython/wiki/wiki/Which-Python#system-python-and-extra-python-packages
>
> Is that no longer true?
>
> Cheers,
>
> Matthew
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20170801/b4bc3cb7/attachment-0001.html>

From njs at pobox.com  Tue Aug  1 10:34:24 2017
From: njs at pobox.com (Nathaniel Smith)
Date: Tue, 1 Aug 2017 07:34:24 -0700
Subject: [Matplotlib-devel] mpl 2.1 + subprocess32
In-Reply-To: <CAH6Pt5pBq9mVVEMJJCaHcLydQxswLpUE5XY9=J5e75p7EaMS5Q@mail.gmail.com>
References: <CAA48SF_OfR3JUs9bOnOK4qZB_LzRY9NTU1BAPAA9A8buzqOiGg@mail.gmail.com>
 <CAH6Pt5pBq9mVVEMJJCaHcLydQxswLpUE5XY9=J5e75p7EaMS5Q@mail.gmail.com>
Message-ID: <CAPJVwBk9bmCxTsmY7CfEEjYPkvs1GA9yhjUhWb4xvx1ztb+DaA@mail.gmail.com>

On Aug 1, 2017 3:54 AM, "Matthew Brett" <matthew.brett at gmail.com> wrote:

Hi,

On Sun, Jul 30, 2017 at 4:20 AM, Thomas Caswell <tcaswell at gmail.com> wrote:
> Folks,
>
> With 2.0 we picked up subprocess32
> (https://pypi.python.org/pypi/subprocess32/) to be able to use the
improved
> subprocess module, however this has caused several problem with [1, 2] due
> to a bug in the release version and wheels not being published on pypi.
The
> bug is reportedly fixed on master [4] and Mathew Brett has provided them
> with wheel-building machinery [3], but there has been no motion on that
> sense May.
>
> I think our options are:
>
>  - document the known issues (meaning wheel-installing mac users have to
> install xcode and people on very old linux need to install from the
> subprocess32 master branch, and general linux users need to have a gcc
> installed)
>  - hope subprocess32 does a release and adopt Matthew's wheels in the next
> month
>  - vendor the master branch (is there a way we can do this _just_ for the
> wheels without actually vendoring it in the source tree?)
>  - change dependencies
>
> After 2.1 we won't have the last option until 2.2 so if we want to do
that,
> it needs to be done this month.
>
> If anyone is motivated to work on changing the dependency, please do so
> otherwise I am inclined to go with the first option.

I'd be really sad if we went for option 1.  I'm particularly
interested in installations for new users, and these are often a) via
pip with b) Python 2.7 and b) without a compiler set up.  So this is a
painful hurdle, often for those least adapted to clear it...

I'm happy to do donkey work if someone can point me the way forward to
replacing the dependency.


I guess the crude but effective solution would be to fork the subprocess32
repo, make sure the patch you want is applied, then rename the package to
subprocess32_for_matplotlib and upload that to pypi. (Later once they
release a fix you can upload a new version that just depends on and
reexports the real subprocess32.)

-n
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20170801/0d4a3af2/attachment.html>

From tcaswell at gmail.com  Sat Aug  5 12:40:47 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Sat, 05 Aug 2017 16:40:47 +0000
Subject: [Matplotlib-devel] list moderation
Message-ID: <CAA48SF-Lv57b4bOe0jS4JYDXn1PuQ-Hm8LeV6boc+ADMHnYX8g@mail.gmail.com>

Folks,

We have a pretty high false-positive rate in the python.org mailing list
moderation queues (mostly due to the 'must be a member to post' policy).  I
just cleared them from May - now (which is why there is a huge spike in
emails just now >:) )

Do we want to:
 a) relax that (at the cost of getting a bit more spam)
 b) some more people volunteer to help moderate the list

Tom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20170805/17d45765/attachment.html>

From juichenieder-nabb at yahoo.co.uk  Sat Aug  5 12:49:20 2017
From: juichenieder-nabb at yahoo.co.uk (OceanWolf)
Date: Sat, 5 Aug 2017 16:49:20 +0000 (UTC)
Subject: [Matplotlib-devel] list moderation
In-Reply-To: <CAA48SF-Lv57b4bOe0jS4JYDXn1PuQ-Hm8LeV6boc+ADMHnYX8g@mail.gmail.com>
References: <CAA48SF-Lv57b4bOe0jS4JYDXn1PuQ-Hm8LeV6boc+ADMHnYX8g@mail.gmail.com>
Message-ID: <271383452.393605.1501951760102@mail.yahoo.com>

Why not c) just discard all emails rejected with a message back to the user as to the explanation.? Up to the user to correct the problem and try again.? If they weren't a member, then become a member.? If you spam with large graphics, then upload it somewhere else and insert a link instead.


      From: Thomas Caswell <tcaswell at gmail.com>
 To: matplotlib development list <matplotlib-devel at python.org> 
 Sent: Saturday, 5 August 2017, 18:41
 Subject: [Matplotlib-devel] list moderation
   
Folks,
We have a pretty high false-positive rate in the python.org mailing list moderation queues (mostly due to the 'must be a member to post' policy).? I just cleared them from May - now (which is why there is a huge spike in emails just now >:) )?
Do we want to:?a) relax that (at the cost of getting a bit more spam)?b) some more people volunteer to help moderate the list?
Tom_______________________________________________
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/20170805/1c1deac1/attachment.html>

From tcaswell at gmail.com  Sat Aug  5 13:18:45 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Sat, 05 Aug 2017 17:18:45 +0000
Subject: [Matplotlib-devel] list moderation
In-Reply-To: <271383452.393605.1501951760102@mail.yahoo.com>
References: <CAA48SF-Lv57b4bOe0jS4JYDXn1PuQ-Hm8LeV6boc+ADMHnYX8g@mail.gmail.com>
 <271383452.393605.1501951760102@mail.yahoo.com>
Message-ID: <CAA48SF9rMMNSiN8U+d2xTr_gbe-N1vcD4E=6dOfTsUns7xCR5A@mail.gmail.com>

We should try to be an open and welcoming community.  Getting bounced from
the mailing list is not the best first impression to a new user looking for
help!

Tom

On Sat, Aug 5, 2017 at 12:49 PM OceanWolf <juichenieder-nabb at yahoo.co.uk>
wrote:

> Why not c) just discard all emails rejected with a message back to the
> user as to the explanation.  Up to the user to correct the problem and try
> again.  If they weren't a member, then become a member.  If you spam with
> large graphics, then upload it somewhere else and insert a link instead.
>
>
> ------------------------------
> *From:* Thomas Caswell <tcaswell at gmail.com>
> *To:* matplotlib development list <matplotlib-devel at python.org>
> *Sent:* Saturday, 5 August 2017, 18:41
> *Subject:* [Matplotlib-devel] list moderation
>
> Folks,
>
> We have a pretty high false-positive rate in the python.org mailing list
> moderation queues (mostly due to the 'must be a member to post' policy).  I
> just cleared them from May - now (which is why there is a huge spike in
> emails just now >:) )
>
> Do we want to:
>  a) relax that (at the cost of getting a bit more spam)
>  b) some more people volunteer to help moderate the list
>
> Tom
> _______________________________________________
> 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/20170805/edc8c1fe/attachment-0001.html>

From jklymak at uvic.ca  Sat Aug  5 13:26:35 2017
From: jklymak at uvic.ca (Klymak Jody)
Date: Sat, 5 Aug 2017 10:26:35 -0700
Subject: [Matplotlib-devel] list moderation
In-Reply-To: <CAA48SF9rMMNSiN8U+d2xTr_gbe-N1vcD4E=6dOfTsUns7xCR5A@mail.gmail.com>
References: <CAA48SF-Lv57b4bOe0jS4JYDXn1PuQ-Hm8LeV6boc+ADMHnYX8g@mail.gmail.com>
 <271383452.393605.1501951760102@mail.yahoo.com>
 <CAA48SF9rMMNSiN8U+d2xTr_gbe-N1vcD4E=6dOfTsUns7xCR5A@mail.gmail.com>
Message-ID: <B5AC6626-196C-4A38-8F09-1CB410C6E4BE@uvic.ca>

You can just make the bounce message nice.  If you aren't a member of the list you can't expect to see the answer to your query anyways, so asking someone to be signed up for the list isnt particularly user hostile.  And nowhere near as bad as getting no answer at all for three months ;-). 

Cheers.  Jody. 

Sent from my iPhone

> On Aug 5, 2017, at 10:18, Thomas Caswell <tcaswell at gmail.com> wrote:
> 
> We should try to be an open and welcoming community.  Getting bounced from the mailing list is not the best first impression to a new user looking for help!
> 
> Tom
> 
>> On Sat, Aug 5, 2017 at 12:49 PM OceanWolf <juichenieder-nabb at yahoo.co.uk> wrote:
>> Why not c) just discard all emails rejected with a message back to the user as to the explanation.  Up to the user to correct the problem and try again.  If they weren't a member, then become a member.  If you spam with large graphics, then upload it somewhere else and insert a link instead.
>> 
>> 
>> From: Thomas Caswell <tcaswell at gmail.com>
>> To: matplotlib development list <matplotlib-devel at python.org> 
>> Sent: Saturday, 5 August 2017, 18:41
>> Subject: [Matplotlib-devel] list moderation
>> 
>> Folks,
>> 
>> We have a pretty high false-positive rate in the python.org mailing list moderation queues (mostly due to the 'must be a member to post' policy).  I just cleared them from May - now (which is why there is a huge spike in emails just now >:) ) 
>> 
>> Do we want to:
>>  a) relax that (at the cost of getting a bit more spam)
>>  b) some more people volunteer to help moderate the list 
>> 
>> Tom
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Matplotlib-devel at python.org
>> https://mail.python.org/mailman/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/20170805/39bc9711/attachment.html>

From tcaswell at gmail.com  Sat Aug  5 13:31:28 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Sat, 05 Aug 2017 17:31:28 +0000
Subject: [Matplotlib-devel] Matplotlib Finance Maintenance
In-Reply-To: <1495138733.977201925@f27.my.com>
References: <1495138733.977201925@f27.my.com>
Message-ID: <CAA48SF8mdNkeE0jMxCmwqSM5=UPOSeuMaNOOv=23+cpAvsi9FQ@mail.gmail.com>

David,

Sorry this sat in moderation for so long.  The first task is to join the
devel mailing list (
https://mail.python.org/mailman/listinfo/matplotlib-devel) ;)

Right now the primary maintenance tasks are to do an official release
(create a tag, upload to pypi, contact various down-stream packagers to get
packages built, etc).

Going forward, now that mpl-finance is split off of the main code base it
can pick up dependencies, such as pandas, and develop an API that better
fits what day-to-day users need.  Much of that API design / review would
ultimately fall on the maintainer.

Tom

On Sat, Aug 5, 2017 at 12:40 PM <dmcnick150 at frontier.com> wrote:

> Hello!
>
> What is involved in maintaining the matplotlib.finance module? I am a
> daily user of the module and consider myself to be an okay Python script
> writer, but I wonder if maintaining the module is beyond my skill.
>
> Thanks for your consideration,
> David McNickle
> dmcnick150 at frontier.com
>
>
>
> Sent from myMail for iOS
> _______________________________________________
> 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/20170805/4a53f0bc/attachment.html>

From juichenieder-nabb at yahoo.co.uk  Sat Aug  5 14:23:42 2017
From: juichenieder-nabb at yahoo.co.uk (OceanWolf)
Date: Sat, 5 Aug 2017 18:23:42 +0000 (UTC)
Subject: [Matplotlib-devel] list moderation
In-Reply-To: <B5AC6626-196C-4A38-8F09-1CB410C6E4BE@uvic.ca>
References: <CAA48SF-Lv57b4bOe0jS4JYDXn1PuQ-Hm8LeV6boc+ADMHnYX8g@mail.gmail.com>
 <271383452.393605.1501951760102@mail.yahoo.com>
 <CAA48SF9rMMNSiN8U+d2xTr_gbe-N1vcD4E=6dOfTsUns7xCR5A@mail.gmail.com>
 <B5AC6626-196C-4A38-8F09-1CB410C6E4BE@uvic.ca>
Message-ID: <1919708237.437374.1501957422455@mail.yahoo.com>

Exactamundo Jody, and add to that we have designated this list as a discussion place for developers, and not for a new user looking for help, as far as I know we had a separate list for that, "matplotlib-users", or did that disappear when we switched to python.org for the list hosting?

Best,Ocean Wolf


      From: Klymak Jody <jklymak at uvic.ca>
 To: Thomas Caswell <tcaswell at gmail.com> 
Cc: OceanWolf <juichenieder-nabb at yahoo.co.uk>; matplotlib development list <matplotlib-devel at python.org>
 Sent: Saturday, 5 August 2017, 19:28
 Subject: Re: [Matplotlib-devel] list moderation
   
You can just make the bounce message nice. ?If you aren't a member of the list you can't expect to see the answer to your query anyways, so asking someone to be signed up for the list isnt particularly user hostile. ?And nowhere near as bad as getting no answer at all for three months ;-).?
Cheers. ?Jody.?

Sent from my iPhone
On Aug 5, 2017, at 10:18, Thomas Caswell <tcaswell at gmail.com> wrote:


We should try to be an open and welcoming community.? Getting bounced from the mailing list is not the best first impression to a new user looking for help!
Tom
On Sat, Aug 5, 2017 at 12:49 PM OceanWolf <juichenieder-nabb at yahoo.co.uk> wrote:

Why not c) just discard all emails rejected with a message back to the user as to the explanation.? Up to the user to correct the problem and try again.? If they weren't a member, then become a member.? If you spam with large graphics, then upload it somewhere else and insert a link instead.


      From: Thomas Caswell <tcaswell at gmail.com>
 To: matplotlib development list <matplotlib-devel at python.org> 
 Sent: Saturday, 5 August 2017, 18:41
 Subject: [Matplotlib-devel] list moderation
  
Folks,
We have a pretty high false-positive rate in the python.org mailing list moderation queues (mostly due to the 'must be a member to post' policy).? I just cleared them from May - now (which is why there is a huge spike in emails just now >:) )?
Do we want to:?a) relax that (at the cost of getting a bit more spam)?b) some more people volunteer to help moderate the list?
Tom_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel at python.org
https://mail.python.org/mailman/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/20170805/e53be4dc/attachment-0001.html>

From efiring at hawaii.edu  Sat Aug  5 14:50:59 2017
From: efiring at hawaii.edu (Eric Firing)
Date: Sat, 5 Aug 2017 08:50:59 -1000
Subject: [Matplotlib-devel] list moderation
In-Reply-To: <1919708237.437374.1501957422455@mail.yahoo.com>
References: <CAA48SF-Lv57b4bOe0jS4JYDXn1PuQ-Hm8LeV6boc+ADMHnYX8g@mail.gmail.com>
 <271383452.393605.1501951760102@mail.yahoo.com>
 <CAA48SF9rMMNSiN8U+d2xTr_gbe-N1vcD4E=6dOfTsUns7xCR5A@mail.gmail.com>
 <B5AC6626-196C-4A38-8F09-1CB410C6E4BE@uvic.ca>
 <1919708237.437374.1501957422455@mail.yahoo.com>
Message-ID: <a7edf59c-0da8-62e4-0b77-868151eb1244@hawaii.edu>

I think Tom is referring to the matplotlib-users list, not the devel 
list.  Nevertheless, I agree with Jody that a well-designed bounce 
message requesting signing up to the list, and including clear 
instructions, would be fine.

Eric

On 2017/08/05 8:23 AM, OceanWolf via Matplotlib-devel wrote:
> Exactamundo Jody, and add to that we have designated this list as a 
> discussion place for developers, and not for a new user looking for 
> help, as far as I know we had a separate list for that, 
> "matplotlib-users", or did that disappear when we switched to python.org 
> for the list hosting?
> 
> Best,
> Ocean Wolf
> 
> 
> 
> ------------------------------------------------------------------------
> *From:* Klymak Jody <jklymak at uvic.ca>
> *To:* Thomas Caswell <tcaswell at gmail.com>
> *Cc:* OceanWolf <juichenieder-nabb at yahoo.co.uk>; matplotlib development 
> list <matplotlib-devel at python.org>
> *Sent:* Saturday, 5 August 2017, 19:28
> *Subject:* Re: [Matplotlib-devel] list moderation
> 
> You can just make the bounce message nice.  If you aren't a member of 
> the list you can't expect to see the answer to your query anyways, so 
> asking someone to be signed up for the list isnt particularly user 
> hostile.  And nowhere near as bad as getting no answer at all for three 
> months ;-).
> 
> Cheers.  Jody.
> 
> Sent from my iPhone
> 
> On Aug 5, 2017, at 10:18, Thomas Caswell <tcaswell at gmail.com 
> <mailto:tcaswell at gmail.com>> wrote:
> 
>> We should try to be an open and welcoming community.  Getting bounced 
>> from the mailing list is not the best first impression to a new user 
>> looking for help!
>>
>> Tom
>>
>> On Sat, Aug 5, 2017 at 12:49 PM OceanWolf 
>> <juichenieder-nabb at yahoo.co.uk <mailto:juichenieder-nabb at yahoo.co.uk>> 
>> wrote:
>>
>>     Why not c) just discard all emails rejected with a message back to
>>     the user as to the explanation.  Up to the user to correct the
>>     problem and try again.  If they weren't a member, then become a
>>     member.  If you spam with large graphics, then upload it somewhere
>>     else and insert a link instead.
>>
>>
>>     ------------------------------------------------------------------------
>>     *From:* Thomas Caswell <tcaswell at gmail.com
>>     <mailto:tcaswell at gmail.com>>
>>     *To:* matplotlib development list <matplotlib-devel at python.org
>>     <mailto:matplotlib-devel at python.org>>
>>     *Sent:* Saturday, 5 August 2017, 18:41
>>     *Subject:* [Matplotlib-devel] list moderation
>>
>>     Folks,
>>
>>     We have a pretty high false-positive rate in the python.org
>>     <http://python.org/> mailing list moderation queues (mostly due to
>>     the 'must be a member to post' policy).  I just cleared them from
>>     May - now (which is why there is a huge spike in emails just now
>>     >:) )
>>
>>     Do we want to:
>>      a) relax that (at the cost of getting a bit more spam)
>>      b) some more people volunteer to help moderate the list
>>
>>     Tom
>>     _______________________________________________
>>     Matplotlib-devel mailing list
>>     Matplotlib-devel at python.org <mailto:Matplotlib-devel at python.org>
>>     https://mail.python.org/mailman/listinfo/matplotlib-devel
>>
>>
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Matplotlib-devel at python.org <mailto:Matplotlib-devel at python.org>
>> https://mail.python.org/mailman/listinfo/matplotlib-devel
> 
> 
> 
> 
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
> 


From chris.barker at noaa.gov  Sat Aug  5 17:22:15 2017
From: chris.barker at noaa.gov (Chris Barker)
Date: Sat, 5 Aug 2017 14:22:15 -0700
Subject: [Matplotlib-devel] step-by-step to installling from source
 using conda?
In-Reply-To: <EB4704F0-3BE6-4D40-8796-E41741BD237D@gmail.com>
References: <EB4704F0-3BE6-4D40-8796-E41741BD237D@gmail.com>
Message-ID: <CALGmxEJXmjBjhQwJJ-9qDqoa=WOGA-XMyqJD3F2yvORKan372A@mail.gmail.com>

This should be pretty straightforward, but MPL's dependencie are pretty
complex. IN thoery, simplyL

1) create an environment
2) install the dev dependencies
3) build away.

but in fact, step (2) there is not so straightforward, so here we go...

1) I recommend using conda-forge as a source of packages -- it is more up
to date than defaults, and you are developing....

conda config --add channels conda-forge

2)  create an environment for doing your development:

conda create -n mpl-dev python=3

3) activate that environment:

source activate mpl-dev

4) install the requirements of mpl:

OK -- this one is kinda messy for MPL. It has a lot of requirements that
depend someone on which sub-packages you are going to build.

but first you need pk-config, which MPL used to find/configure stuff on
*nix systems.

(you may have this from Brew already)

conda install pkg-config

python setup.py --requires doesn't work, as mpl does a lot of ative
configuration.

but:

python ./setup.py dry-run

will get you a good list:

REQUIRED DEPENDENCIES AND EXTENSIONS
                 numpy: yes [not found. pip may install it below.]
                   six: yes [six was not found.pip will attempt to install
                        it after matplotlib.]
              dateutil: yes [dateutil was not found. It is required for date
                        axis support. pip/easy_install may attempt to
                        install it after matplotlib.]
backports.functools_lru_cache: yes [Not required]
          subprocess32: yes [Not required]
                  pytz: yes [pytz was not found. pip/easy_install may
                        attempt to install it after matplotlib.]
                cycler: yes [cycler was not found. pip/easy_install may
                        attempt to install it after matplotlib.]
               tornado: yes [tornado was not found. It is required for the
                        WebAgg backend. pip/easy_install may attempt to
                        install it after matplotlib.]
             pyparsing: yes [pyparsing was not found. It is required for
                        mathtext support. pip/easy_install may attempt to
                        install it after matplotlib.]
                libagg: yes [pkg-config information for 'libagg' could not
                        be found. Using local copy.]
              freetype: no  [The C/C++ header for freetype2 (ft2build.h)
                        could not be found.  You may need to install the
                        development package.]
                   png: yes [version 1.6.26]
                 qhull: yes [pkg-config information for 'libqhull' could not
                        be found. Using local copy.]

you don't want pip to try to install anything, so I created a requirements
file (enclosed)

conda install --file conda_requirements_dev.txt

And now you should be able to build!

python setup.py build

Note that you won't get all the back-ends -- other dependencies need to be
installed for that.

BTW: it would be nice to have something like that conda_requirements_dev.txt
in the MPL repo -- the setup-tools stuff is way to tied into the
build/packaging/installing system.

HTH,

-CHB


On Tue, Jun 13, 2017 at 6:24 AM, Jody Klymak <jklymak at gmail.com> wrote:

>
> Hi all,
>
> I?m somewhat stymied trying to understand how to install matplotlib in a
> development environment using conda.
>
> I have MacOS, and I have brew gcc etc. I know how to set up a env in conda.
>
> I eventually want to be able to run the tests, so that I can stop
> uploading things with PEP8 errors etc.
>
> Sorry if this is too vague. I can start over again and send specific
> errors if that is easier, but I would bet someone has a step-by-step.
>
> Thanks, Jody
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
>


-- 

Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

Chris.Barker at noaa.gov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20170805/ee32c33e/attachment.html>
-------------- next part --------------
pkg-config
numpy
six
freetype
libpng # want the conda version

# run-time deps
# may be needed if you want to test stuff.
python-dateutil
pytz
cycler
tornado
pyparsing


From jklymak at uvic.ca  Sat Aug  5 17:33:30 2017
From: jklymak at uvic.ca (Klymak Jody)
Date: Sat, 5 Aug 2017 14:33:30 -0700
Subject: [Matplotlib-devel] step-by-step to installling from source
 using conda?
In-Reply-To: <CALGmxEJXmjBjhQwJJ-9qDqoa=WOGA-XMyqJD3F2yvORKan372A@mail.gmail.com>
References: <EB4704F0-3BE6-4D40-8796-E41741BD237D@gmail.com>
 <CALGmxEJXmjBjhQwJJ-9qDqoa=WOGA-XMyqJD3F2yvORKan372A@mail.gmail.com>
Message-ID: <2DA18638-B97C-462C-AC6C-FB1D1EB7EBF5@uvic.ca>

Hi Chris.  Thanks so much. That'll be useful

I think I was partially tricked by the fact that %matplotlib notebook wasn't working for master in a Jupiter notebook.   but I see now that it doesn't wrk for anyone so I guess I was installing things adequately ;-)

Thanks again.   Jody

Sent from my iPhone

> On Aug 5, 2017, at 14:22, Chris Barker <chris.barker at noaa.gov> wrote:
> 
> This should be pretty straightforward, but MPL's dependencie are pretty complex. IN thoery, simplyL
> 
> 1) create an environment
> 2) install the dev dependencies
> 3) build away.
> 
> but in fact, step (2) there is not so straightforward, so here we go...
> 
> 1) I recommend using conda-forge as a source of packages -- it is more up to date than defaults, and you are developing....
> 
> conda config --add channels conda-forge
> 
> 2)  create an environment for doing your development:
> 
> conda create -n mpl-dev python=3
> 
> 3) activate that environment:
> 
> source activate mpl-dev
> 
> 4) install the requirements of mpl:
> 
> OK -- this one is kinda messy for MPL. It has a lot of requirements that depend someone on which sub-packages you are going to build.
> 
> but first you need pk-config, which MPL used to find/configure stuff on *nix systems.
> 
> (you may have this from Brew already)
> 
> conda install pkg-config
> 
> python setup.py --requires doesn't work, as mpl does a lot of ative configuration.
> 
> but:
> 
> python ./setup.py dry-run
> 
> will get you a good list:
> 
> REQUIRED DEPENDENCIES AND EXTENSIONS
>                  numpy: yes [not found. pip may install it below.]
>                    six: yes [six was not found.pip will attempt to install
>                         it after matplotlib.]
>               dateutil: yes [dateutil was not found. It is required for date
>                         axis support. pip/easy_install may attempt to
>                         install it after matplotlib.]
> backports.functools_lru_cache: yes [Not required]
>           subprocess32: yes [Not required]
>                   pytz: yes [pytz was not found. pip/easy_install may
>                         attempt to install it after matplotlib.]
>                 cycler: yes [cycler was not found. pip/easy_install may
>                         attempt to install it after matplotlib.]
>                tornado: yes [tornado was not found. It is required for the
>                         WebAgg backend. pip/easy_install may attempt to
>                         install it after matplotlib.]
>              pyparsing: yes [pyparsing was not found. It is required for
>                         mathtext support. pip/easy_install may attempt to
>                         install it after matplotlib.]
>                 libagg: yes [pkg-config information for 'libagg' could not
>                         be found. Using local copy.]
>               freetype: no  [The C/C++ header for freetype2 (ft2build.h)
>                         could not be found.  You may need to install the
>                         development package.]
>                    png: yes [version 1.6.26]
>                  qhull: yes [pkg-config information for 'libqhull' could not
>                         be found. Using local copy.]
> 
> you don't want pip to try to install anything, so I created a requirements file (enclosed)
> 
> conda install --file conda_requirements_dev.txt
> 
> And now you should be able to build!
> 
> python setup.py build
> 
> Note that you won't get all the back-ends -- other dependencies need to be installed for that.
> 
> BTW: it would be nice to have something like that conda_requirements_dev.txt  in the MPL repo -- the setup-tools stuff is way to tied into the build/packaging/installing system.
> 
> HTH,
> 
> -CHB
> 
> 
>> On Tue, Jun 13, 2017 at 6:24 AM, Jody Klymak <jklymak at gmail.com> wrote:
>> 
>> Hi all,
>> 
>> I?m somewhat stymied trying to understand how to install matplotlib in a development environment using conda.
>> 
>> I have MacOS, and I have brew gcc etc. I know how to set up a env in conda.
>> 
>> I eventually want to be able to run the tests, so that I can stop uploading things with PEP8 errors etc.
>> 
>> Sorry if this is too vague. I can start over again and send specific errors if that is easier, but I would bet someone has a step-by-step.
>> 
>> Thanks, Jody
>> 
>> 
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Matplotlib-devel at python.org
>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>> 
> 
> 
> 
> 
> -- 
> 
> Christopher Barker, Ph.D.
> Oceanographer
> 
> Emergency Response Division
> NOAA/NOS/OR&R            (206) 526-6959   voice
> 7600 Sand Point Way NE   (206) 526-6329   fax
> Seattle, WA  98115       (206) 526-6317   main reception
> 
> Chris.Barker at noaa.gov
> <conda_requirements_dev.txt>
> _______________________________________________
> 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/20170805/c7dd4507/attachment-0001.html>

From tcaswell at gmail.com  Sat Aug  5 19:23:14 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Sat, 05 Aug 2017 23:23:14 +0000
Subject: [Matplotlib-devel] list moderation
In-Reply-To: <a7edf59c-0da8-62e4-0b77-868151eb1244@hawaii.edu>
References: <CAA48SF-Lv57b4bOe0jS4JYDXn1PuQ-Hm8LeV6boc+ADMHnYX8g@mail.gmail.com>
 <271383452.393605.1501951760102@mail.yahoo.com>
 <CAA48SF9rMMNSiN8U+d2xTr_gbe-N1vcD4E=6dOfTsUns7xCR5A@mail.gmail.com>
 <B5AC6626-196C-4A38-8F09-1CB410C6E4BE@uvic.ca>
 <1919708237.437374.1501957422455@mail.yahoo.com>
 <a7edf59c-0da8-62e4-0b77-868151eb1244@hawaii.edu>
Message-ID: <CAA48SF_-qYY6Zv3M4EV1mePY3c11BjnsQQ8EdB5K+y2mjrRnzg@mail.gmail.com>

I was thinking of the user list (
https://mail.python.org/mailman/listinfo/matplotlib-users which you should
totally join oceanwolf ;) )

Off list Jody volunteered to help with moderating and I set my self up to
get the moderation emails from the python.org lists.  With the two of us on
this I think we should be set (but if anyone else wants to help I will not
say no!).

Tom

On Sat, Aug 5, 2017 at 2:51 PM Eric Firing <efiring at hawaii.edu> wrote:

> I think Tom is referring to the matplotlib-users list, not the devel
> list.  Nevertheless, I agree with Jody that a well-designed bounce
> message requesting signing up to the list, and including clear
> instructions, would be fine.
>
> Eric
>
> On 2017/08/05 8:23 AM, OceanWolf via Matplotlib-devel wrote:
> > Exactamundo Jody, and add to that we have designated this list as a
> > discussion place for developers, and not for a new user looking for
> > help, as far as I know we had a separate list for that,
> > "matplotlib-users", or did that disappear when we switched to python.org
> > for the list hosting?
> >
> > Best,
> > Ocean Wolf
> >
> >
> >
> > ------------------------------------------------------------------------
> > *From:* Klymak Jody <jklymak at uvic.ca>
> > *To:* Thomas Caswell <tcaswell at gmail.com>
> > *Cc:* OceanWolf <juichenieder-nabb at yahoo.co.uk>; matplotlib development
> > list <matplotlib-devel at python.org>
> > *Sent:* Saturday, 5 August 2017, 19:28
> > *Subject:* Re: [Matplotlib-devel] list moderation
> >
> > You can just make the bounce message nice.  If you aren't a member of
> > the list you can't expect to see the answer to your query anyways, so
> > asking someone to be signed up for the list isnt particularly user
> > hostile.  And nowhere near as bad as getting no answer at all for three
> > months ;-).
> >
> > Cheers.  Jody.
> >
> > Sent from my iPhone
> >
> > On Aug 5, 2017, at 10:18, Thomas Caswell <tcaswell at gmail.com
> > <mailto:tcaswell at gmail.com>> wrote:
> >
> >> We should try to be an open and welcoming community.  Getting bounced
> >> from the mailing list is not the best first impression to a new user
> >> looking for help!
> >>
> >> Tom
> >>
> >> On Sat, Aug 5, 2017 at 12:49 PM OceanWolf
> >> <juichenieder-nabb at yahoo.co.uk <mailto:juichenieder-nabb at yahoo.co.uk>>
> >> wrote:
> >>
> >>     Why not c) just discard all emails rejected with a message back to
> >>     the user as to the explanation.  Up to the user to correct the
> >>     problem and try again.  If they weren't a member, then become a
> >>     member.  If you spam with large graphics, then upload it somewhere
> >>     else and insert a link instead.
> >>
> >>
> >>
>  ------------------------------------------------------------------------
> >>     *From:* Thomas Caswell <tcaswell at gmail.com
> >>     <mailto:tcaswell at gmail.com>>
> >>     *To:* matplotlib development list <matplotlib-devel at python.org
> >>     <mailto:matplotlib-devel at python.org>>
> >>     *Sent:* Saturday, 5 August 2017, 18:41
> >>     *Subject:* [Matplotlib-devel] list moderation
> >>
> >>     Folks,
> >>
> >>     We have a pretty high false-positive rate in the python.org
> >>     <http://python.org/> mailing list moderation queues (mostly due to
> >>     the 'must be a member to post' policy).  I just cleared them from
> >>     May - now (which is why there is a huge spike in emails just now
> >>     >:) )
> >>
> >>     Do we want to:
> >>      a) relax that (at the cost of getting a bit more spam)
> >>      b) some more people volunteer to help moderate the list
> >>
> >>     Tom
> >>     _______________________________________________
> >>     Matplotlib-devel mailing list
> >>     Matplotlib-devel at python.org <mailto:Matplotlib-devel at python.org>
> >>     https://mail.python.org/mailman/listinfo/matplotlib-devel
> >>
> >>
> >> _______________________________________________
> >> Matplotlib-devel mailing list
> >> Matplotlib-devel at python.org <mailto:Matplotlib-devel at python.org>
> >> https://mail.python.org/mailman/listinfo/matplotlib-devel
> >
> >
> >
> >
> > _______________________________________________
> > Matplotlib-devel mailing list
> > Matplotlib-devel at python.org
> > https://mail.python.org/mailman/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/20170805/f9426101/attachment.html>

From tcaswell at gmail.com  Sat Aug  5 19:27:24 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Sat, 05 Aug 2017 23:27:24 +0000
Subject: [Matplotlib-devel] step-by-step to installling from source
 using conda?
In-Reply-To: <2DA18638-B97C-462C-AC6C-FB1D1EB7EBF5@uvic.ca>
References: <EB4704F0-3BE6-4D40-8796-E41741BD237D@gmail.com>
 <CALGmxEJXmjBjhQwJJ-9qDqoa=WOGA-XMyqJD3F2yvORKan372A@mail.gmail.com>
 <2DA18638-B97C-462C-AC6C-FB1D1EB7EBF5@uvic.ca>
Message-ID: <CAA48SF9MZcb5GO-zYrm2J6tPeL=wCvOeF6EEcTdXPeJFHhU4_A@mail.gmail.com>

I sometimes take a blunter approach, install Matplotlib via conda and then
uninstall it which leaves behind the dependencies ;)

Tom

On Sat, Aug 5, 2017 at 5:33 PM Klymak Jody <jklymak at uvic.ca> wrote:

> Hi Chris.  Thanks so much. That'll be useful
>
> I think I was partially tricked by the fact that %matplotlib notebook
> wasn't working for master in a Jupiter notebook.   but I see now that it
> doesn't wrk for anyone so I guess I was installing things adequately ;-)
>
> Thanks again.   Jody
>
> Sent from my iPhone
>
> On Aug 5, 2017, at 14:22, Chris Barker <chris.barker at noaa.gov> wrote:
>
> This should be pretty straightforward, but MPL's dependencie are pretty
> complex. IN thoery, simplyL
>
> 1) create an environment
> 2) install the dev dependencies
> 3) build away.
>
> but in fact, step (2) there is not so straightforward, so here we go...
>
> 1) I recommend using conda-forge as a source of packages -- it is more up
> to date than defaults, and you are developing....
>
> conda config --add channels conda-forge
>
> 2)  create an environment for doing your development:
>
> conda create -n mpl-dev python=3
>
> 3) activate that environment:
>
> source activate mpl-dev
>
> 4) install the requirements of mpl:
>
> OK -- this one is kinda messy for MPL. It has a lot of requirements that
> depend someone on which sub-packages you are going to build.
>
> but first you need pk-config, which MPL used to find/configure stuff on
> *nix systems.
>
> (you may have this from Brew already)
>
> conda install pkg-config
>
> python setup.py --requires doesn't work, as mpl does a lot of ative
> configuration.
>
> but:
>
> python ./setup.py dry-run
>
> will get you a good list:
>
> REQUIRED DEPENDENCIES AND EXTENSIONS
>                  numpy: yes [not found. pip may install it below.]
>                    six: yes [six was not found.pip will attempt to install
>                         it after matplotlib.]
>               dateutil: yes [dateutil was not found. It is required for
> date
>                         axis support. pip/easy_install may attempt to
>                         install it after matplotlib.]
> backports.functools_lru_cache: yes [Not required]
>           subprocess32: yes [Not required]
>                   pytz: yes [pytz was not found. pip/easy_install may
>                         attempt to install it after matplotlib.]
>                 cycler: yes [cycler was not found. pip/easy_install may
>                         attempt to install it after matplotlib.]
>                tornado: yes [tornado was not found. It is required for the
>                         WebAgg backend. pip/easy_install may attempt to
>                         install it after matplotlib.]
>              pyparsing: yes [pyparsing was not found. It is required for
>                         mathtext support. pip/easy_install may attempt to
>                         install it after matplotlib.]
>                 libagg: yes [pkg-config information for 'libagg' could not
>                         be found. Using local copy.]
>               freetype: no  [The C/C++ header for freetype2 (ft2build.h)
>                         could not be found.  You may need to install the
>                         development package.]
>                    png: yes [version 1.6.26]
>                  qhull: yes [pkg-config information for 'libqhull' could
> not
>                         be found. Using local copy.]
>
> you don't want pip to try to install anything, so I created a requirements
> file (enclosed)
>
> conda install --file conda_requirements_dev.txt
>
> And now you should be able to build!
>
> python setup.py build
>
> Note that you won't get all the back-ends -- other dependencies need to be
> installed for that.
>
> BTW: it would be nice to have something like that
> conda_requirements_dev.txt  in the MPL repo -- the setup-tools stuff is
> way to tied into the build/packaging/installing system.
>
> HTH,
>
> -CHB
>
>
> On Tue, Jun 13, 2017 at 6:24 AM, Jody Klymak <jklymak at gmail.com> wrote:
>
>>
>> Hi all,
>>
>> I?m somewhat stymied trying to understand how to install matplotlib in a
>> development environment using conda.
>>
>> I have MacOS, and I have brew gcc etc. I know how to set up a env in
>> conda.
>>
>> I eventually want to be able to run the tests, so that I can stop
>> uploading things with PEP8 errors etc.
>>
>> Sorry if this is too vague. I can start over again and send specific
>> errors if that is easier, but I would bet someone has a step-by-step.
>>
>> Thanks, Jody
>>
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Matplotlib-devel at python.org
>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>
>>
>
>
> --
>
> Christopher Barker, Ph.D.
> Oceanographer
>
> Emergency Response Division
> NOAA/NOS/OR&R            (206) 526-6959   voice
> 7600 Sand Point Way NE   (206) 526-6329   fax
> Seattle, WA  98115       (206) 526-6317   main reception
>
> Chris.Barker at noaa.gov
>
> <conda_requirements_dev.txt>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/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/20170805/03fc6ea0/attachment-0001.html>

From juichenieder-nabb at yahoo.co.uk  Sat Aug  5 20:23:39 2017
From: juichenieder-nabb at yahoo.co.uk (OceanWolf)
Date: Sun, 6 Aug 2017 00:23:39 +0000 (UTC)
Subject: [Matplotlib-devel] list moderation
In-Reply-To: <CAA48SF_-qYY6Zv3M4EV1mePY3c11BjnsQQ8EdB5K+y2mjrRnzg@mail.gmail.com>
References: <CAA48SF-Lv57b4bOe0jS4JYDXn1PuQ-Hm8LeV6boc+ADMHnYX8g@mail.gmail.com>
 <271383452.393605.1501951760102@mail.yahoo.com>
 <CAA48SF9rMMNSiN8U+d2xTr_gbe-N1vcD4E=6dOfTsUns7xCR5A@mail.gmail.com>
 <B5AC6626-196C-4A38-8F09-1CB410C6E4BE@uvic.ca>
 <1919708237.437374.1501957422455@mail.yahoo.com>
 <a7edf59c-0da8-62e4-0b77-868151eb1244@hawaii.edu>
 <CAA48SF_-qYY6Zv3M4EV1mePY3c11BjnsQQ8EdB5K+y2mjrRnzg@mail.gmail.com>
Message-ID: <1131892917.554174.1501979019613@mail.yahoo.com>

Mwahahahahaha, I lurk on the #matplotlib channel on irc.freenode.net :).

      From: Thomas Caswell <tcaswell at gmail.com>
 To: Eric Firing <efiring at hawaii.edu>; matplotlib-devel at python.org 
 Sent: Sunday, 6 August 2017, 1:23
 Subject: Re: [Matplotlib-devel] list moderation
   
I was thinking of the user list (https://mail.python.org/mailman/listinfo/matplotlib-users?which you should totally join oceanwolf ;) )?
Off list Jody volunteered to help with moderating and I set my self up to get the moderation emails from the python.org lists.? With the two of us on this I think we should be set (but if anyone else wants to help I will not say no!).
Tom

On Sat, Aug 5, 2017 at 2:51 PM Eric Firing <efiring at hawaii.edu> wrote:

I think Tom is referring to the matplotlib-users list, not the devel
list.? Nevertheless, I agree with Jody that a well-designed bounce
message requesting signing up to the list, and including clear
instructions, would be fine.

Eric

On 2017/08/05 8:23 AM, OceanWolf via Matplotlib-devel wrote:
> Exactamundo Jody, and add to that we have designated this list as a
> discussion place for developers, and not for a new user looking for
> help, as far as I know we had a separate list for that,
> "matplotlib-users", or did that disappear when we switched to python.org
> for the list hosting?
>
> Best,
> Ocean Wolf
>
>
>
> ------------------------------------------------------------------------
> *From:* Klymak Jody <jklymak at uvic.ca>
> *To:* Thomas Caswell <tcaswell at gmail.com>
> *Cc:* OceanWolf <juichenieder-nabb at yahoo.co.uk>; matplotlib development
> list <matplotlib-devel at python.org>
> *Sent:* Saturday, 5 August 2017, 19:28
> *Subject:* Re: [Matplotlib-devel] list moderation
>
> You can just make the bounce message nice.? If you aren't a member of
> the list you can't expect to see the answer to your query anyways, so
> asking someone to be signed up for the list isnt particularly user
> hostile.? And nowhere near as bad as getting no answer at all for three
> months ;-).
>
> Cheers.? Jody.
>
> Sent from my iPhone
>
> On Aug 5, 2017, at 10:18, Thomas Caswell <tcaswell at gmail.com
> <mailto:tcaswell at gmail.com>> wrote:
>
>> We should try to be an open and welcoming community.? Getting bounced
>> from the mailing list is not the best first impression to a new user
>> looking for help!
>>
>> Tom
>>
>> On Sat, Aug 5, 2017 at 12:49 PM OceanWolf
>> <juichenieder-nabb at yahoo.co.uk <mailto:juichenieder-nabb at yahoo.co.uk>>
>> wrote:
>>
>>? ? ?Why not c) just discard all emails rejected with a message back to
>>? ? ?the user as to the explanation.? Up to the user to correct the
>>? ? ?problem and try again.? If they weren't a member, then become a
>>? ? ?member.? If you spam with large graphics, then upload it somewhere
>>? ? ?else and insert a link instead.
>>
>>
>>? ? ?------------------------------------------------------------------------
>>? ? ?*From:* Thomas Caswell <tcaswell at gmail.com
>>? ? ?<mailto:tcaswell at gmail.com>>
>>? ? ?*To:* matplotlib development list <matplotlib-devel at python.org
>>? ? ?<mailto:matplotlib-devel at python.org>>
>>? ? ?*Sent:* Saturday, 5 August 2017, 18:41
>>? ? ?*Subject:* [Matplotlib-devel] list moderation
>>
>>? ? ?Folks,
>>
>>? ? ?We have a pretty high false-positive rate in the python.org
>>? ? ?<http://python.org/> mailing list moderation queues (mostly due to
>>? ? ?the 'must be a member to post' policy).? I just cleared them from
>>? ? ?May - now (which is why there is a huge spike in emails just now
>>? ? ?>:) )
>>
>>? ? ?Do we want to:
>>? ? ? a) relax that (at the cost of getting a bit more spam)
>>? ? ? b) some more people volunteer to help moderate the list
>>
>>? ? ?Tom
>>? ? ?_______________________________________________
>>? ? ?Matplotlib-devel mailing list
>>? ? ?Matplotlib-devel at python.org <mailto:Matplotlib-devel at python.org>
>>? ? ?https://mail.python.org/mailman/listinfo/matplotlib-devel
>>
>>
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Matplotlib-devel at python.org <mailto:Matplotlib-devel at python.org>
>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
>
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>

_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel at python.org
https://mail.python.org/mailman/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/20170806/8094ee08/attachment.html>

From efiring at hawaii.edu  Sun Aug  6 13:29:49 2017
From: efiring at hawaii.edu (Eric Firing)
Date: Sun, 6 Aug 2017 07:29:49 -1000
Subject: [Matplotlib-devel] step-by-step to installling from source
 using conda?
In-Reply-To: <CAA48SF9MZcb5GO-zYrm2J6tPeL=wCvOeF6EEcTdXPeJFHhU4_A@mail.gmail.com>
References: <EB4704F0-3BE6-4D40-8796-E41741BD237D@gmail.com>
 <CALGmxEJXmjBjhQwJJ-9qDqoa=WOGA-XMyqJD3F2yvORKan372A@mail.gmail.com>
 <2DA18638-B97C-462C-AC6C-FB1D1EB7EBF5@uvic.ca>
 <CAA48SF9MZcb5GO-zYrm2J6tPeL=wCvOeF6EEcTdXPeJFHhU4_A@mail.gmail.com>
Message-ID: <ce8241f6-49a0-831d-20f0-348f855e6773@hawaii.edu>

That's what I do, also.  For the installation from source I now use 
either "pip install ." or "pip install -e .".  Depending on how much I 
am changing (e.g., switching from maintenance to master, or back), I do 
"pip uninstall matplotlib" and "git clean -dfx" (only with all desired 
changes committed, of course) to clean out the old version before 
installing the new.

At least on a Mac, there can still be some bogus test failures.

Eric

On 2017/08/05 1:27 PM, Thomas Caswell wrote:
> I sometimes take a blunter approach, install Matplotlib via conda and 
> then uninstall it which leaves behind the dependencies ;)
> 
> Tom
> 
> On Sat, Aug 5, 2017 at 5:33 PM Klymak Jody <jklymak at uvic.ca 
> <mailto:jklymak at uvic.ca>> wrote:
> 
>     Hi Chris.  Thanks so much. That'll be useful
> 
>     I think I was partially tricked by the fact that %matplotlib
>     notebook wasn't working for master in a Jupiter notebook.   but I
>     see now that it doesn't wrk for anyone so I guess I was installing
>     things adequately ;-)
> 
>     Thanks again.   Jody
> 
>     Sent from my iPhone
> 
>     On Aug 5, 2017, at 14:22, Chris Barker <chris.barker at noaa.gov
>     <mailto:chris.barker at noaa.gov>> wrote:
> 
>>     This should be pretty straightforward, but MPL's dependencie are
>>     pretty complex. IN thoery, simplyL
>>
>>     1) create an environment
>>     2) install the dev dependencies
>>     3) build away.
>>
>>     but in fact, step (2) there is not so straightforward, so here we
>>     go...
>>
>>     1) I recommend using conda-forge as a source of packages -- it is
>>     more up to date than defaults, and you are developing....
>>
>>     conda config --add channels conda-forge
>>
>>     2)  create an environment for doing your development:
>>
>>     conda create -n mpl-dev python=3
>>
>>     3) activate that environment:
>>
>>     source activate mpl-dev
>>
>>     4) install the requirements of mpl:
>>
>>     OK -- this one is kinda messy for MPL. It has a lot of
>>     requirements that depend someone on which sub-packages you are
>>     going to build.
>>
>>     but first you need pk-config, which MPL used to find/configure
>>     stuff on *nix systems.
>>
>>     (you may have this from Brew already)
>>
>>     conda install pkg-config
>>
>>     python setup.py --requires doesn't work, as mpl does a lot of
>>     ative configuration.
>>
>>     but:
>>
>>     python ./setup.py dry-run
>>
>>     will get you a good list:
>>
>>     REQUIRED DEPENDENCIES AND EXTENSIONS
>>                      numpy: yes [not found. pip may install it below.]
>>                        six: yes [six was not found.pip will attempt to
>>     install
>>                             it after matplotlib.]
>>                   dateutil: yes [dateutil was not found. It is
>>     required for date
>>                             axis support. pip/easy_install may attempt to
>>                             install it after matplotlib.]
>>     backports.functools_lru_cache: yes [Not required]
>>               subprocess32: yes [Not required]
>>                       pytz: yes [pytz was not found. pip/easy_install may
>>                             attempt to install it after matplotlib.]
>>                     cycler: yes [cycler was not found.
>>     pip/easy_install may
>>                             attempt to install it after matplotlib.]
>>                    tornado: yes [tornado was not found. It is required
>>     for the
>>                             WebAgg backend. pip/easy_install may
>>     attempt to
>>                             install it after matplotlib.]
>>                  pyparsing: yes [pyparsing was not found. It is
>>     required for
>>                             mathtext support. pip/easy_install may
>>     attempt to
>>                             install it after matplotlib.]
>>                     libagg: yes [pkg-config information for 'libagg'
>>     could not
>>                             be found. Using local copy.]
>>                   freetype: no  [The C/C++ header for freetype2
>>     (ft2build.h)
>>                             could not be found.  You may need to
>>     install the
>>                             development package.]
>>                        png: yes [version 1.6.26]
>>                      qhull: yes [pkg-config information for 'libqhull'
>>     could not
>>                             be found. Using local copy.]
>>
>>     you don't want pip to try to install anything, so I created a
>>     requirements file (enclosed)
>>
>>     conda install --file conda_requirements_dev.txt
>>
>>     And now you should be able to build!
>>
>>     python setup.py build
>>
>>     Note that you won't get all the back-ends -- other dependencies
>>     need to be installed for that.
>>
>>     BTW: it would be nice to have something like that
>>     conda_requirements_dev.txt  in the MPL repo -- the setup-tools
>>     stuff is way to tied into the build/packaging/installing system.
>>
>>     HTH,
>>
>>     -CHB
>>
>>
>>     On Tue, Jun 13, 2017 at 6:24 AM, Jody Klymak <jklymak at gmail.com
>>     <mailto:jklymak at gmail.com>> wrote:
>>
>>
>>         Hi all,
>>
>>         I?m somewhat stymied trying to understand how to install
>>         matplotlib in a development environment using conda.
>>
>>         I have MacOS, and I have brew gcc etc. I know how to set up a
>>         env in conda.
>>
>>         I eventually want to be able to run the tests, so that I can
>>         stop uploading things with PEP8 errors etc.
>>
>>         Sorry if this is too vague. I can start over again and send
>>         specific errors if that is easier, but I would bet someone has
>>         a step-by-step.
>>
>>         Thanks, Jody
>>
>>
>>         _______________________________________________
>>         Matplotlib-devel mailing list
>>         Matplotlib-devel at python.org <mailto:Matplotlib-devel at python.org>
>>         https://mail.python.org/mailman/listinfo/matplotlib-devel
>>
>>
>>
>>
>>     -- 
>>
>>     Christopher Barker, Ph.D.
>>     Oceanographer
>>
>>     Emergency Response Division
>>     NOAA/NOS/OR&R (206) 526-6959 <tel:%28206%29%20526-6959>   voice
>>     7600 Sand Point Way NE (206) 526-6329 <tel:%28206%29%20526-6329>   fax
>>     Seattle, WA  98115 (206) 526-6317 <tel:%28206%29%20526-6317>  
>>     main reception
>>
>>     Chris.Barker at noaa.gov <mailto:Chris.Barker at noaa.gov>
>>     <conda_requirements_dev.txt>
>>     _______________________________________________
>>     Matplotlib-devel mailing list
>>     Matplotlib-devel at python.org <mailto:Matplotlib-devel at python.org>
>>     https://mail.python.org/mailman/listinfo/matplotlib-devel
>     _______________________________________________
>     Matplotlib-devel mailing list
>     Matplotlib-devel at python.org <mailto:Matplotlib-devel at python.org>
>     https://mail.python.org/mailman/listinfo/matplotlib-devel
> 
> 
> 
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
> 


From chris.barker at noaa.gov  Sun Aug  6 16:18:53 2017
From: chris.barker at noaa.gov (Chris Barker - NOAA Federal)
Date: Sun, 6 Aug 2017 13:18:53 -0700
Subject: [Matplotlib-devel] step-by-step to installling from source
 using conda?
In-Reply-To: <ce8241f6-49a0-831d-20f0-348f855e6773@hawaii.edu>
References: <EB4704F0-3BE6-4D40-8796-E41741BD237D@gmail.com>
 <CALGmxEJXmjBjhQwJJ-9qDqoa=WOGA-XMyqJD3F2yvORKan372A@mail.gmail.com>
 <2DA18638-B97C-462C-AC6C-FB1D1EB7EBF5@uvic.ca>
 <CAA48SF9MZcb5GO-zYrm2J6tPeL=wCvOeF6EEcTdXPeJFHhU4_A@mail.gmail.com>
 <ce8241f6-49a0-831d-20f0-348f855e6773@hawaii.edu>
Message-ID: <1135667185655485257@unknownmsgid>

That's what I do, also.  For the installation from source I now use either
"pip install ." or "pip install -e .".


-e for development for sure. But pip will try to bring in missing
dependencies for you, which is less than ideal if you don't want a
conda-pip jumble.

I think pip -e has a --no-deps flag, or something like that, which is
useful.

On 2017/08/05 1:27 PM, Thomas Caswell wrote:

I sometimes take a blunter approach, install Matplotlib via conda and then
uninstall it which leaves behind the dependencies ;)


D-uh! I should have thought of that!

That may not get you all the build deps but it will be close.

Oh, and taking a look at the Vonda recipe would be a better way to get the
deps list:

https://github.com/conda-forge/matplotlib-feedstock/blob/master/recipe/meta.yaml

-CHB


Tom

On Sat, Aug 5, 2017 at 5:33 PM Klymak Jody <jklymak at uvic.ca <
mailto:jklymak at uvic.ca <jklymak at uvic.ca>>> wrote:

   Hi Chris.  Thanks so much. That'll be useful

   I think I was partially tricked by the fact that %matplotlib

   notebook wasn't working for master in a Jupiter notebook.   but I

   see now that it doesn't wrk for anyone so I guess I was installing

   things adequately ;-)

   Thanks again.   Jody

   Sent from my iPhone

   On Aug 5, 2017, at 14:22, Chris Barker <chris.barker at noaa.gov

   <mailto:chris.barker at noaa.gov <chris.barker at noaa.gov>>> wrote:

   This should be pretty straightforward, but MPL's dependencie are

   pretty complex. IN thoery, simplyL


   1) create an environment

   2) install the dev dependencies

   3) build away.


   but in fact, step (2) there is not so straightforward, so here we

   go...


   1) I recommend using conda-forge as a source of packages -- it is

   more up to date than defaults, and you are developing....


   conda config --add channels conda-forge


   2)  create an environment for doing your development:


   conda create -n mpl-dev python=3


   3) activate that environment:


   source activate mpl-dev


   4) install the requirements of mpl:


   OK -- this one is kinda messy for MPL. It has a lot of

   requirements that depend someone on which sub-packages you are

   going to build.


   but first you need pk-config, which MPL used to find/configure

   stuff on *nix systems.


   (you may have this from Brew already)


   conda install pkg-config


   python setup.py --requires doesn't work, as mpl does a lot of

   ative configuration.


   but:


   python ./setup.py dry-run


   will get you a good list:


   REQUIRED DEPENDENCIES AND EXTENSIONS

                    numpy: yes [not found. pip may install it below.]

                      six: yes [six was not found.pip will attempt to

   install

                           it after matplotlib.]

                 dateutil: yes [dateutil was not found. It is

   required for date

                           axis support. pip/easy_install may attempt to

                           install it after matplotlib.]

   backports.functools_lru_cache: yes [Not required]

             subprocess32: yes [Not required]

                     pytz: yes [pytz was not found. pip/easy_install may

                           attempt to install it after matplotlib.]

                   cycler: yes [cycler was not found.

   pip/easy_install may

                           attempt to install it after matplotlib.]

                  tornado: yes [tornado was not found. It is required

   for the

                           WebAgg backend. pip/easy_install may

   attempt to

                           install it after matplotlib.]

                pyparsing: yes [pyparsing was not found. It is

   required for

                           mathtext support. pip/easy_install may

   attempt to

                           install it after matplotlib.]

                   libagg: yes [pkg-config information for 'libagg'

   could not

                           be found. Using local copy.]

                 freetype: no  [The C/C++ header for freetype2

   (ft2build.h)

                           could not be found.  You may need to

   install the

                           development package.]

                      png: yes [version 1.6.26]

                    qhull: yes [pkg-config information for 'libqhull'

   could not

                           be found. Using local copy.]


   you don't want pip to try to install anything, so I created a

   requirements file (enclosed)


   conda install --file conda_requirements_dev.txt


   And now you should be able to build!


   python setup.py build


   Note that you won't get all the back-ends -- other dependencies

   need to be installed for that.


   BTW: it would be nice to have something like that

   conda_requirements_dev.txt  in the MPL repo -- the setup-tools

   stuff is way to tied into the build/packaging/installing system.


   HTH,


   -CHB



   On Tue, Jun 13, 2017 at 6:24 AM, Jody Klymak <jklymak at gmail.com

   <mailto:jklymak at gmail.com <jklymak at gmail.com>>> wrote:



       Hi all,


       I?m somewhat stymied trying to understand how to install

       matplotlib in a development environment using conda.


       I have MacOS, and I have brew gcc etc. I know how to set up a

       env in conda.


       I eventually want to be able to run the tests, so that I can

       stop uploading things with PEP8 errors etc.


       Sorry if this is too vague. I can start over again and send

       specific errors if that is easier, but I would bet someone has

       a step-by-step.


       Thanks, Jody



       _______________________________________________

       Matplotlib-devel mailing list

       Matplotlib-devel at python.org <mailto:Matplotlib-devel at python.org
<Matplotlib-devel at python.org>>

       https://mail.python.org/mailman/listinfo/matplotlib-devel





   --

   Christopher Barker, Ph.D.

   Oceanographer


   Emergency Response Division

   NOAA/NOS/OR&R (206) 526-6959 <tel:%28206%29%20526-6959
<%28206%29%20526-6959>>   voice

   7600 Sand Point Way NE (206) 526-6329 <tel:%28206%29%20526-6329
<%28206%29%20526-6329>>   fax

   Seattle, WA  98115 (206) 526-6317 <tel:%28206%29%20526-6317
<%28206%29%20526-6317>>      main reception


   Chris.Barker at noaa.gov <mailto:Chris.Barker at noaa.gov
<Chris.Barker at noaa.gov>>

   <conda_requirements_dev.txt>

   _______________________________________________

   Matplotlib-devel mailing list

   Matplotlib-devel at python.org <mailto:Matplotlib-devel at python.org
<Matplotlib-devel at python.org>>

   https://mail.python.org/mailman/listinfo/matplotlib-devel

   _______________________________________________

   Matplotlib-devel mailing list

   Matplotlib-devel at python.org <mailto:Matplotlib-devel at python.org
<Matplotlib-devel at python.org>>

   https://mail.python.org/mailman/listinfo/matplotlib-devel

_______________________________________________

Matplotlib-devel mailing list

Matplotlib-devel at python.org

https://mail.python.org/mailman/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/20170806/b90a1c70/attachment-0001.html>

From efiring at hawaii.edu  Sun Aug  6 21:54:49 2017
From: efiring at hawaii.edu (Eric Firing)
Date: Sun, 6 Aug 2017 15:54:49 -1000
Subject: [Matplotlib-devel] step-by-step to installling from source
 using conda?
In-Reply-To: <1135667185655485257@unknownmsgid>
References: <EB4704F0-3BE6-4D40-8796-E41741BD237D@gmail.com>
 <CALGmxEJXmjBjhQwJJ-9qDqoa=WOGA-XMyqJD3F2yvORKan372A@mail.gmail.com>
 <2DA18638-B97C-462C-AC6C-FB1D1EB7EBF5@uvic.ca>
 <CAA48SF9MZcb5GO-zYrm2J6tPeL=wCvOeF6EEcTdXPeJFHhU4_A@mail.gmail.com>
 <ce8241f6-49a0-831d-20f0-348f855e6773@hawaii.edu>
 <1135667185655485257@unknownmsgid>
Message-ID: <4c4fc531-54b1-c04d-4b7c-bdcde695fb9b@hawaii.edu>

On 2017/08/06 10:18 AM, Chris Barker - NOAA Federal wrote:
> But pip will try to bring in missing dependencies for you, which is less 
> than ideal if you don't want a conda-pip jumble.

Agreed, but using the conda install, conda uninstall method to get the 
dependencies, I haven't run into the problem of pip rudely installing 
things without asking.

Eric

From chris.barker at noaa.gov  Mon Aug  7 18:57:07 2017
From: chris.barker at noaa.gov (Chris Barker)
Date: Mon, 7 Aug 2017 18:57:07 -0400
Subject: [Matplotlib-devel] step-by-step to installling from source
 using conda?
In-Reply-To: <4c4fc531-54b1-c04d-4b7c-bdcde695fb9b@hawaii.edu>
References: <EB4704F0-3BE6-4D40-8796-E41741BD237D@gmail.com>
 <CALGmxEJXmjBjhQwJJ-9qDqoa=WOGA-XMyqJD3F2yvORKan372A@mail.gmail.com>
 <2DA18638-B97C-462C-AC6C-FB1D1EB7EBF5@uvic.ca>
 <CAA48SF9MZcb5GO-zYrm2J6tPeL=wCvOeF6EEcTdXPeJFHhU4_A@mail.gmail.com>
 <ce8241f6-49a0-831d-20f0-348f855e6773@hawaii.edu>
 <1135667185655485257@unknownmsgid>
 <4c4fc531-54b1-c04d-4b7c-bdcde695fb9b@hawaii.edu>
Message-ID: <CALGmxELGp6GxFDHRJuXAuAaC0watfhdtd8AR2vPVubtg==7McA@mail.gmail.com>

On Sun, Aug 6, 2017 at 9:54 PM, Eric Firing <efiring at hawaii.edu> wrote:

> On 2017/08/06 10:18 AM, Chris Barker - NOAA Federal wrote:
>
>> But pip will try to bring in missing dependencies for you, which is less
>> than ideal if you don't want a conda-pip jumble.
>>
>
> Agreed, but using the conda install, conda uninstall method to get the
> dependencies, I haven't run into the problem of pip rudely installing
> things without asking.


exactly -- you need to conda install everything needed first. Properly
built conda packages will have the proper meta-data so that pip knows it's
installed.

-CHB



-- 

Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

Chris.Barker at noaa.gov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20170807/1a00981f/attachment.html>

From tcaswell at gmail.com  Mon Aug 14 17:02:41 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Mon, 14 Aug 2017 21:02:41 +0000
Subject: [Matplotlib-devel] Phone call notes 2017-08-07
Message-ID: <CAA48SF8GyuO-R4kAN_5+uf46Y8Ly=BWCz73X8kGxEhLW_ZRGrA@mail.gmail.com>

Folks,

Sorry these are so late getting out.  Myself, Eric Firing, and Ryan May
where on the call.


 - talked about image interpolation PR, I have a todo list in a comment on
that one still
 - talked about unbreaking %matplotlib notebook
   - source of breaking is that it got upgraded to use ipywidegts, but v4
   - there have been many breaking changes between than and now
   - plan is to revert that PR and go back to injecting our own JS
     (because it works across notebook versions)
 - talked about long term fate of 'classic' mode
   - when we have to re-generate images for other reasons, switch those
tests to using the new default
 - discussed (and merged) #8949
 - discussed #8944
 - discussed #9002 and hi-dpi
   - it is a mess!
   - Eric's summary of what is going on
     - at rendering time, there is a 'true dpi' depending on renderer
       and what it is rendering too (what screen)
     - best case user only knows about 'physical' units
     - our renderers need to do best to go out pixelated output
       - in vector backends we are doing an intermediate rendering to their
represenation
     - in Agg we are doing both steps ourselves
     - maybe we should think of this as two stage process to get everything
to physical units and
       the second step
     - maybe we should add anothre layer to the transform stack

Tom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20170814/9c9e2f81/attachment.html>

From tcaswell at gmail.com  Mon Aug 14 17:03:57 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Mon, 14 Aug 2017 21:03:57 +0000
Subject: [Matplotlib-devel] Phone call notes 2017-08-14
Message-ID: <CAA48SF_ugeokQkWXY8FwEO5nvjiXckFT8-D_AG7jYmtE0Bo=qA@mail.gmail.com>

Folks,

My self, Eric Firing, Paul Hobson, Ryan May

 * notebook stuff
   - #9027 reverts back to our old js hacking method
   - we can not keep up with the ipywidget release cadence, move that to
ipympl
   - Tom will work with Steven Silvester and Sylvain Corlay at JupyterCon
to iterate on ipympl.
 * axesstack
   - drop tcaswell PR to fix merge of 7377
   - revert merge of 7377
   - deprecate the 'return an axes if one exsits' functionality
 * dpi ratio #9002
   - punt on proper fix involving transforms
 * window in front
   - GUIs are hard and all different
   - need to control focus and raising separately
   - each backend is a special
 * sundry triage and merging (mostly moving things to 2.2)
 * need to think about what policy to have for style sheets (and color maps)


Tom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20170814/d756bf02/attachment.html>

From millman at berkeley.edu  Fri Aug 18 15:53:09 2017
From: millman at berkeley.edu (Jarrod Millman)
Date: Fri, 18 Aug 2017 12:53:09 -0700
Subject: [Matplotlib-devel] NetworkX 2.0b1 released
Message-ID: <CAB6X4sj8=ukA0nn0J+=bGtEAgWLdJcMsvvpcsAR7eTNCzhKwWg@mail.gmail.com>

Hi All,

I am happy to announce the **beta** release of NetworkX 2.0! NetworkX
is a Python package for the creation, manipulation, and study of the
structure, dynamics, and functions of complex networks.

This release supports Python 2.7 and 3.4-3.6 and contains many new
features.  This release is the result of over two years of work with
over 600 pull requests by 85 contributors.  We have made **major
changes** to the methods in the Multi/Di/Graph classes and before the
2.0 release we need feedback on those changes.  If you have code that
imports networkx, please take some time to check that you are able to
update your code to work with the new release.

Please see the draft of the 2.0 release announcement:
  http://networkx.readthedocs.io/en/latest/news.html#networkx-2-0
In particular, we would like feedback on the migration guide from 1.X to 2.0:
  http://networkx.readthedocs.io/en/latest/release/migration_guide_from_1.x_to_2.0.html

Since it is a beta release, pip won't automatically install it.  So
  $ pip install networkx
still installs networkx-1.11 still.  But
  $ pip install --pre networkx
will install networkx-2.0b1.  If you already have networkx installed
then you need to do
  $ pip install --pre --upgrade networkx

For more information, please visit our `website
<http://networkx.github.io/>`_ and our `gallery of examples
<http://networkx.readthedocs.io/en/latest/auto_examples/index.html>`_.
Please send comments and questions to the `networkx-discuss mailing
list <http://groups.google.com/group/networkx-discuss>`_ or create an
issue `here <https://github.com/networkx/networkx/issues>`_.

Best regards,
Jarrod

From jklymak at uvic.ca  Fri Aug 25 13:20:15 2017
From: jklymak at uvic.ca (Jody Klymak)
Date: Fri, 25 Aug 2017 10:20:15 -0700
Subject: [Matplotlib-devel] Do we already parse units for sizes (i.e.
 padding)
Message-ID: <87454BC1-F402-422D-BD12-D1A205729F39@uvic.ca>

Hi all,

I?m trying to work out how to do the padding on my constrained_layout 
geometry manager (which is testable by the way if anyone wants to try to 
break it for me: https://github.com/matplotlib/matplotlib/pull/9082). 
Since I do the constraints in figure-normalized co-ordinates, my pad 
variable is figure-normalized, which maybe makes sense for some plots, 
but I can easily imagine it will set some people?s OCD off if the 
padding is thicker in the horizotnal than the vertical because the 
figure is wider than it is tall.

So I could do inches/cm, or pixels, or points. But I guess it?d be 
nice to do all four. Do we already have a units parser? I couldn?t 
find one. I think it?d be pretty simple: just strip the last two 
characters off for unit type and pass the rest as a float.

1.0px (=1.0 px; i.e. strip spaces)
1.0cm
1.0mm
1.0in
1.0pt

I don?t think em and en would make sense in this context because we 
wouldn?t know the font size, though maybe there is a sensible figure 
default we could use?

Then calls like pad=0.01 and pad=?5mm? would both be acceptable.

a) does this exist already?
b) if not, should it?

Thanks, Jody

From ben.v.root at gmail.com  Fri Aug 25 13:53:29 2017
From: ben.v.root at gmail.com (Benjamin Root)
Date: Fri, 25 Aug 2017 13:53:29 -0400
Subject: [Matplotlib-devel] Do we already parse units for sizes (i.e.
 padding)
In-Reply-To: <87454BC1-F402-422D-BD12-D1A205729F39@uvic.ca>
References: <87454BC1-F402-422D-BD12-D1A205729F39@uvic.ca>
Message-ID: <CANNq6Fm6k=duinkvUg7Yx6RjHFdTdCrpGG9KOy3uzx2G7dk34Q@mail.gmail.com>

a) no, it does not exist already
b) at first blush, yes, it would be awesome, and maybe pint might be able
to help us with that.

however... I would caution against getting side-tracked to add such a
feature at the moment. There is a lot of hidden complexities that I think
has not yet been fully appreciated yet. For example, inches and points are
very different from pixels, and would require diving into the transforms
system. We would also open ourselves to a fair amount of confusion from
users. One time, when I was teaching an intro to matplotlib, the tutorial
got derailed by the very first example by a person who was confused that a
figure that was specified to be 7in x 5in wasn't that size on his laptop
screen!

Ben


On Fri, Aug 25, 2017 at 1:20 PM, Jody Klymak <jklymak at uvic.ca> wrote:

> Hi all,
>
> I?m trying to work out how to do the padding on my constrained_layout
> geometry manager (which is testable by the way if anyone wants to try to
> break it for me: https://github.com/matplotlib/matplotlib/pull/9082).
> Since I do the constraints in figure-normalized co-ordinates, my pad
> variable is figure-normalized, which maybe makes sense for some plots, but
> I can easily imagine it will set some people?s OCD off if the padding is
> thicker in the horizotnal than the vertical because the figure is wider
> than it is tall.
>
> So I could do inches/cm, or pixels, or points. But I guess it?d be nice to
> do all four. Do we already have a units parser? I couldn?t find one. I
> think it?d be pretty simple: just strip the last two characters off for
> unit type and pass the rest as a float.
>
> 1.0px (=1.0 px; i.e. strip spaces)
> 1.0cm
> 1.0mm
> 1.0in
> 1.0pt
>
> I don?t think em and en would make sense in this context because we
> wouldn?t know the font size, though maybe there is a sensible figure
> default we could use?
>
> Then calls like pad=0.01 and pad=?5mm? would both be acceptable.
>
> a) does this exist already?
> b) if not, should it?
>
> Thanks, Jody
> _______________________________________________
> 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/20170825/5c9cf222/attachment.html>

From jklymak at uvic.ca  Fri Aug 25 16:16:59 2017
From: jklymak at uvic.ca (Jody Klymak)
Date: Fri, 25 Aug 2017 13:16:59 -0700
Subject: [Matplotlib-devel] Do we already parse units for sizes (i.e.
 padding)
In-Reply-To: <CANNq6Fm6k=duinkvUg7Yx6RjHFdTdCrpGG9KOy3uzx2G7dk34Q@mail.gmail.com>
References: <87454BC1-F402-422D-BD12-D1A205729F39@uvic.ca>
 <CANNq6Fm6k=duinkvUg7Yx6RjHFdTdCrpGG9KOy3uzx2G7dk34Q@mail.gmail.com>
Message-ID: <14252B08-2288-458A-BA0A-A3537AC9DBCD@uvic.ca>


Hi Ben,

On 25 Aug 2017, at 10:53, Benjamin Root wrote:

> a) no, it does not exist already
> b) at first blush, yes, it would be awesome, and maybe pint might be 
> able
> to help us with that.

I thought you were going to send me a beer?


> however... I would caution against getting side-tracked to add such a
> feature at the moment. There is a lot of hidden complexities that I 
> think
> has not yet been fully appreciated yet. For example, inches and points 
> are
> very different from pixels, and would require diving into the 
> transforms
> system.

First, I readily admit there is vast swaths of transforms and plotting 
things in backends I don?t appreciate!

Right now the `constrained_layout` manager needs to know about pixels 
versus figure co-ordinates, which I do now as:

```
invTransFig = fig.transFigure.inverted().transform_bbox
bbox = invTransFig(ax.get_tightbbox(renderer=fig.renderer))
```

so I?m already dealing with two of the three types of co-ordinates.  I 
was assuming I could get to inches from `pixels = inches * 
fig.renderer.dpi`, and I am certain I can figure out centimeters.  
However, I?ll look at the transforms, maybe there is already one that 
deals with the renderer dpi.

Perhaps a relevant question for me to move forward is: what (default) 
units should a pad between figure elements be?  `tight_layout` uses 
fraction of a font size (I assume fraction of `M`, though I haven?t 
checked).  Other packages do different things.   Even if we don?t want 
a flexible way of specifying lengths, having a consistent default would 
be good.

> We would also open ourselves to a fair amount of confusion from
> users. One time, when I was teaching an intro to matplotlib, the 
> tutorial
> got derailed by the very first example by a person who was confused 
> that a
> figure that was specified to be 7in x 5in wasn't that size on his 
> laptop
> screen!

If the figure size isn?t right, I?d assume that 12pt fonts don?t 
come out right either, yet I still think it makes sense to specify fonts 
in points (well I don?t actually - I?d much prefer mm or inches - 
but I doubt that?ll get much traction).  So I think its sensible to 
specify padding and other lengths in physical units.

Anyway, I?d propose that I write a little package to do what I think 
is right, and then use it with `constrained_layout`, but with a sensible 
floating-point default argument in a sensible unit for the padding.  If 
others think its a good idea then great, maybe it?d get adopted 
elsewhere. If not, I could remove it from `constrained_layout` for 
consistency and just use the sensible default.

Thanks,   Jody

>
> Ben
>
>
> On Fri, Aug 25, 2017 at 1:20 PM, Jody Klymak <jklymak at uvic.ca> wrote:
>
>> Hi all,
>>
>> I?m trying to work out how to do the padding on my 
>> constrained_layout
>> geometry manager (which is testable by the way if anyone wants to try 
>> to
>> break it for me: https://github.com/matplotlib/matplotlib/pull/9082).
>> Since I do the constraints in figure-normalized co-ordinates, my pad
>> variable is figure-normalized, which maybe makes sense for some 
>> plots, but
>> I can easily imagine it will set some people?s OCD off if the 
>> padding is
>> thicker in the horizotnal than the vertical because the figure is 
>> wider
>> than it is tall.
>>
>> So I could do inches/cm, or pixels, or points. But I guess it?d be 
>> nice to
>> do all four. Do we already have a units parser? I couldn?t find 
>> one. I
>> think it?d be pretty simple: just strip the last two characters off 
>> for
>> unit type and pass the rest as a float.
>>
>> 1.0px (=1.0 px; i.e. strip spaces)
>> 1.0cm
>> 1.0mm
>> 1.0in
>> 1.0pt
>>
>> I don?t think em and en would make sense in this context because we
>> wouldn?t know the font size, though maybe there is a sensible 
>> figure
>> default we could use?
>>
>> Then calls like pad=0.01 and pad=?5mm? would both be acceptable.
>>
>> a) does this exist already?
>> b) if not, should it?
>>
>> Thanks, Jody
>> _______________________________________________
>> 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/20170825/b1524fc2/attachment-0001.html>

From tcaswell at gmail.com  Fri Aug 25 22:34:03 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Sat, 26 Aug 2017 02:34:03 +0000
Subject: [Matplotlib-devel] final 2.1rc1 merges
Message-ID: <CAA48SF_a5Md62U4bjxcPr7pnCTjPLjZOJuN=9+zvKPZEfXt2bQ@mail.gmail.com>

Folks,

If there is anything not currently tagged 'release critical' that you think
needs go in for 2.1 please flag it now!  If you are not sure, err on the
side of marking it, we can always un-mark it.

Tom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20170826/b188683b/attachment.html>

From chris.barker at noaa.gov  Mon Aug 28 23:52:12 2017
From: chris.barker at noaa.gov (Chris Barker)
Date: Mon, 28 Aug 2017 20:52:12 -0700
Subject: [Matplotlib-devel] Do we already parse units for sizes (i.e.
 padding)
In-Reply-To: <14252B08-2288-458A-BA0A-A3537AC9DBCD@uvic.ca>
References: <87454BC1-F402-422D-BD12-D1A205729F39@uvic.ca>
 <CANNq6Fm6k=duinkvUg7Yx6RjHFdTdCrpGG9KOy3uzx2G7dk34Q@mail.gmail.com>
 <14252B08-2288-458A-BA0A-A3537AC9DBCD@uvic.ca>
Message-ID: <CALGmxE+SPi=-ZX26U85PB78PufK3xeLeJQEMv6PydfDG-WjMow@mail.gmail.com>

one thought:

Do not allow pixels to specify anything :-)

the final length-units (in, mm, points) to pixels conversion should only
happen at the last minute when you need to actually render to an image.

The user can change the ppi setting at any pint until then -- their layout
shouldn't change if they do.

Ideally, changing the dpi will result in exactly the same image -- other
than resolution.

-CHB




On Fri, Aug 25, 2017 at 1:16 PM, Jody Klymak <jklymak at uvic.ca> wrote:

> Hi Ben,
>
> On 25 Aug 2017, at 10:53, Benjamin Root wrote:
>
> a) no, it does not exist already
> b) at first blush, yes, it would be awesome, and maybe pint might be able
> to help us with that.
>
> I thought you were going to send me a beer?
>
> however... I would caution against getting side-tracked to add such a
> feature at the moment. There is a lot of hidden complexities that I think
> has not yet been fully appreciated yet. For example, inches and points are
> very different from pixels, and would require diving into the transforms
> system.
>
> First, I readily admit there is vast swaths of transforms and plotting
> things in backends I don?t appreciate!
>
> Right now the constrained_layout manager needs to know about pixels
> versus figure co-ordinates, which I do now as:
>
> invTransFig = fig.transFigure.inverted().transform_bbox
> bbox = invTransFig(ax.get_tightbbox(renderer=fig.renderer))
>
> so I?m already dealing with two of the three types of co-ordinates. I was
> assuming I could get to inches from pixels = inches * fig.renderer.dpi,
> and I am certain I can figure out centimeters. However, I?ll look at the
> transforms, maybe there is already one that deals with the renderer dpi.
>
> Perhaps a relevant question for me to move forward is: what (default)
> units should a pad between figure elements be? tight_layout uses fraction
> of a font size (I assume fraction of M, though I haven?t checked). Other
> packages do different things. Even if we don?t want a flexible way of
> specifying lengths, having a consistent default would be good.
>
> We would also open ourselves to a fair amount of confusion from
> users. One time, when I was teaching an intro to matplotlib, the tutorial
> got derailed by the very first example by a person who was confused that a
> figure that was specified to be 7in x 5in wasn't that size on his laptop
> screen!
>
> If the figure size isn?t right, I?d assume that 12pt fonts don?t come out
> right either, yet I still think it makes sense to specify fonts in points
> (well I don?t actually - I?d much prefer mm or inches - but I doubt that?ll
> get much traction). So I think its sensible to specify padding and other
> lengths in physical units.
>
> Anyway, I?d propose that I write a little package to do what I think is
> right, and then use it with constrained_layout, but with a sensible
> floating-point default argument in a sensible unit for the padding. If
> others think its a good idea then great, maybe it?d get adopted elsewhere.
> If not, I could remove it from constrained_layout for consistency and
> just use the sensible default.
>
> Thanks, Jody
>
> Ben
>
>
> On Fri, Aug 25, 2017 at 1:20 PM, Jody Klymak <jklymak at uvic.ca> wrote:
>
> Hi all,
>
> I?m trying to work out how to do the padding on my constrained_layout
> geometry manager (which is testable by the way if anyone wants to try to
> break it for me: https://github.com/matplotlib/matplotlib/pull/9082).
> Since I do the constraints in figure-normalized co-ordinates, my pad
> variable is figure-normalized, which maybe makes sense for some plots, but
> I can easily imagine it will set some people?s OCD off if the padding is
> thicker in the horizotnal than the vertical because the figure is wider
> than it is tall.
>
> So I could do inches/cm, or pixels, or points. But I guess it?d be nice to
> do all four. Do we already have a units parser? I couldn?t find one. I
> think it?d be pretty simple: just strip the last two characters off for
> unit type and pass the rest as a float.
>
> 1.0px (=1.0 px; i.e. strip spaces)
> 1.0cm
> 1.0mm
> 1.0in
> 1.0pt
>
> I don?t think em and en would make sense in this context because we
> wouldn?t know the font size, though maybe there is a sensible figure
> default we could use?
>
> Then calls like pad=0.01 and pad=?5mm? would both be acceptable.
>
> a) does this exist already?
> b) if not, should it?
>
> Thanks, Jody
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
>


-- 

Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

Chris.Barker at noaa.gov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20170828/d5c64d80/attachment.html>

From tcaswell at gmail.com  Tue Aug 29 21:43:13 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Wed, 30 Aug 2017 01:43:13 +0000
Subject: [Matplotlib-devel] Phone call 2017-08-30
Message-ID: <CAA48SF-r43VjKCxc481JbJj3gAq0oX0FzJSHLgW1kzS-dHC5Pw@mail.gmail.com>

Are people around for a phone call around 2100 EST tomorrow to try and wrap
up 2.1rc1 prep?

Tom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20170830/2ea3d766/attachment.html>

From efiring at hawaii.edu  Tue Aug 29 21:49:06 2017
From: efiring at hawaii.edu (Eric Firing)
Date: Tue, 29 Aug 2017 15:49:06 -1000
Subject: [Matplotlib-devel] Phone call 2017-08-30
In-Reply-To: <CAA48SF-r43VjKCxc481JbJj3gAq0oX0FzJSHLgW1kzS-dHC5Pw@mail.gmail.com>
References: <CAA48SF-r43VjKCxc481JbJj3gAq0oX0FzJSHLgW1kzS-dHC5Pw@mail.gmail.com>
Message-ID: <1bfaa05f-187f-d3b1-d3a9-a1737dc4ead6@hawaii.edu>

Did you mean 2100 EDT?  I should be getting out of a meeting about that 
time, so I might be available.

Eric

On 2017/08/29 3:43 PM, Thomas Caswell wrote:
> Are people around for a phone call around 2100 EST tomorrow to try and 
> wrap up 2.1rc1 prep?
> 
> Tom
> 
> 
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
> 


From tcaswell at gmail.com  Tue Aug 29 22:09:36 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Wed, 30 Aug 2017 02:09:36 +0000
Subject: [Matplotlib-devel] Phone call 2017-08-30
In-Reply-To: <1bfaa05f-187f-d3b1-d3a9-a1737dc4ead6@hawaii.edu>
References: <CAA48SF-r43VjKCxc481JbJj3gAq0oX0FzJSHLgW1kzS-dHC5Pw@mail.gmail.com>
 <1bfaa05f-187f-d3b1-d3a9-a1737dc4ead6@hawaii.edu>
Message-ID: <CAA48SF93u0P2aDNifSwRF-0wrku5L+hSgUkAJUdKGW+LCm9KQA@mail.gmail.com>

Yes, I did mean 2100EDT

On Tue, Aug 29, 2017 at 9:49 PM Eric Firing <efiring at hawaii.edu> wrote:

> Did you mean 2100 EDT?  I should be getting out of a meeting about that
> time, so I might be available.
>
> Eric
>
> On 2017/08/29 3:43 PM, Thomas Caswell wrote:
> > Are people around for a phone call around 2100 EST tomorrow to try and
> > wrap up 2.1rc1 prep?
> >
> > Tom
> >
> >
> > _______________________________________________
> > Matplotlib-devel mailing list
> > Matplotlib-devel at python.org
> > https://mail.python.org/mailman/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/20170830/bcc4f19c/attachment.html>

From tcaswell at gmail.com  Tue Aug 29 22:20:51 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Wed, 30 Aug 2017 02:20:51 +0000
Subject: [Matplotlib-devel] deprecate hold
Message-ID: <CAA48SF-CUasnz_HMNzf1nnuhy8-eux3nA7n4VMJDtQxEUQKxvw@mail.gmail.com>

Folks,

We deprecated 'hold' in 2.0, but did not set a version for removal.

I think it in now too close to squeeze it in for 2.1 so I propose we target
2.2 to fully remove it.

Tom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20170830/2902a57a/attachment.html>

From rmay31 at gmail.com  Wed Aug 30 11:05:44 2017
From: rmay31 at gmail.com (Ryan May)
Date: Wed, 30 Aug 2017 15:05:44 +0000
Subject: [Matplotlib-devel] Phone call 2017-08-30
In-Reply-To: <CAA48SF-r43VjKCxc481JbJj3gAq0oX0FzJSHLgW1kzS-dHC5Pw@mail.gmail.com>
References: <CAA48SF-r43VjKCxc481JbJj3gAq0oX0FzJSHLgW1kzS-dHC5Pw@mail.gmail.com>
Message-ID: <CAKH0P+XcQVKnZb9Di_RkPZCbRo7dF8n9EbSK1QeQiQLpCiSFQA@mail.gmail.com>

Yes, though I may only be able to stay for 30 minutes. (I can get back on
at 10 though)

Ryan

On Tue, Aug 29, 2017 at 7:43 PM Thomas Caswell <tcaswell at gmail.com> wrote:

> Are people around for a phone call around 2100 EST tomorrow to try and
> wrap up 2.1rc1 prep?
>
> Tom
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
-- 
Ryan May
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20170830/32bece15/attachment.html>

From tcaswell at gmail.com  Wed Aug 30 20:34:18 2017
From: tcaswell at gmail.com (Thomas Caswell)
Date: Thu, 31 Aug 2017 00:34:18 +0000
Subject: [Matplotlib-devel] Phone call 2017-08-30
In-Reply-To: <CAKH0P+XcQVKnZb9Di_RkPZCbRo7dF8n9EbSK1QeQiQLpCiSFQA@mail.gmail.com>
References: <CAA48SF-r43VjKCxc481JbJj3gAq0oX0FzJSHLgW1kzS-dHC5Pw@mail.gmail.com>
 <CAKH0P+XcQVKnZb9Di_RkPZCbRo7dF8n9EbSK1QeQiQLpCiSFQA@mail.gmail.com>
Message-ID: <CAA48SF8WVOp-mZL7-YVCnTaeVf2FAMarjWBei3uy50kpDQ4nBg@mail.gmail.com>

Hopefully this link will work:
https://hangouts.google.com/hangouts/_/x2gynw2cqndkrahhnaca6e2iyqe

Tom

On Wed, Aug 30, 2017 at 11:05 AM Ryan May <rmay31 at gmail.com> wrote:

> Yes, though I may only be able to stay for 30 minutes. (I can get back on
> at 10 though)
>
> Ryan
>
> On Tue, Aug 29, 2017 at 7:43 PM Thomas Caswell <tcaswell at gmail.com> wrote:
>
>> Are people around for a phone call around 2100 EST tomorrow to try and
>> wrap up 2.1rc1 prep?
>>
>> Tom
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Matplotlib-devel at python.org
>> https://mail.python.org/mailman/listinfo/matplotlib-devel
>>
> --
> Ryan May
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20170831/d2fe9488/attachment.html>