matplotlib-devel Mailing List for matplotlib

On Wed, Dec 5, 2012 at 10:23 PM, Paul Ivanov <piv...@gm...> wrote:
> On Wed, Dec 5, 2012 at 1:52 PM, Nathaniel Smith <nj...@po...> wrote:
>> If you're defining your own warning class, you might consider using
>> FutureWarning instead of UserWarning.
>>
>> We had a discussion about this issue for numpy recently:
>> http://mail.scipy.org/pipermail/numpy-discussion/2012-May/062460.html
>> What we eventually ended up with:
>> http://mail.scipy.org/pipermail/numpy-discussion/2012-May/062468.html
>
> Thanks for the pointers, Nathaniel. Though I think I disagree with
> continuing to use DeprecationWarnings for features that will go away
> and just break code - shouldn't users be given ample opportunity of
> coming changes without having to find out by having their code break
> at a future release?
Yeah, there aren't any perfect solutions here. That's why I didn't
express an opinion on what you ought to do :-).
Basically what the debate comes down to is, deprecation warnings are
useful to developers, and annoying and scary to users. (And users can
easily end up seeing them, e.g. if they use a package which depends on
matplotlib, and then upgrade matplotlib, their existing package may
suddenly start spewing scary warnings, and that package's developers
can't do anything about this because this version of matplotlib is
newer than anything that existed when they released their package.)
This problem becomes worse the lower your package is in the stack, and
the more widely used it is by third-party packages.
It's easier to tell developers how to turn on deprecation warnings
than it is to tell users how to turn them off, so that's why the
Python stdlib turned them off by default, and similarly numpy.
The main thing I took from this personally is that I went and added
'export PYTHONWARNINGS=default' to all my package's test scripts, to
ensure deprecation warnings would be enabled...
-n

On Mon, Dec 10, 2012 at 5:51 PM, Paul Hobson <pmh...@gm...> wrote:
> On Mon, Dec 10, 2012 at 2:18 PM, Tony Yu <ts...@gm...> wrote:
>
>> Hi all,
>>
>> I'm not sure if non-core-developers are allowed to post MEPs, but I just
>> did ;). MEP 12 outlines the reorganization of the example gallery and
>> subsequent clean up of the examples:
>>
>> https://github.com/matplotlib/matplotlib/wiki/MEP12
>>
>> In my opinion, there are two open questions in the MEP:
>>
>> * Section names (may seem trivial to some, but I think it's really
>> important)
>> * Guidelines for cleaning up examples
>>
>> I've added proposed section names and clean-up guidelines to the MEP, but
>> I'm sure these will evolve over time.
>>
>> Best,
>> -Tony
>>
>>
> Here here! I've been waiting for a really nasty, cold, and rainy weekend
> here in Portland to make some PRs at least cleaning up the code contained
> within the examples. Just hasn't happened yet ;)
>
> Tony, if you make your own branch for this, I'd be happy to contribute.
> -paul
>
Awesome! I'm hoping we can quickly converge on some clean-up guidelines and
section headings.
I was envisioning a single PR that adds new gallery sections. After that
examples would be updated over a long period of time in multiple PRs that
change a few examples at a time. Do you think that all the work should be
done on a parallel branch and merged in one big PR?
Best,
-Tony

thanks Tony. I didn't know this before.
On Mon, Dec 10, 2012 at 11:32 PM, Chao YUE <cha...@gm...> wrote:
> The gallry will not include everything, could we also have somewhere to
> let "non-core" users freely share the code? like some features that are
> nice to have but not easily found in the galery? but hope this will not
> lead to overcrowded.
>
> Chao
>
> On Mon, Dec 10, 2012 at 11:18 PM, Tony Yu <ts...@gm...> wrote:
>
>> Hi all,
>>
>> I'm not sure if non-core-developers are allowed to post MEPs, but I just
>> did ;). MEP 12 outlines the reorganization of the example gallery and
>> subsequent clean up of the examples:
>>
>> https://github.com/matplotlib/matplotlib/wiki/MEP12
>>
>> In my opinion, there are two open questions in the MEP:
>>
>> * Section names (may seem trivial to some, but I think it's really
>> important)
>> * Guidelines for cleaning up examples
>>
>> I've added proposed section names and clean-up guidelines to the MEP, but
>> I'm sure these will evolve over time.
>>
>> Best,
>> -Tony
>>
>>
>> ------------------------------------------------------------------------------
>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>> Remotely access PCs and mobile devices and provide instant support
>> Improve your efficiency, and focus on delivering more value-add services
>> Discover what IT Professionals Know. Rescue delivers
>> http://p.sf.net/sfu/logmein_12329d2d
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>
>>
>
>
> --
>
> ***********************************************************************************
> Chao YUE
> Laboratoire des Sciences du Climat et de l'Environnement (LSCE-IPSL)
> UMR 1572 CEA-CNRS-UVSQ
> Batiment 712 - Pe 119
> 91191 GIF Sur YVETTE Cedex
> Tel: (33) 01 69 08 29 02; Fax:01.69.08.77.16
>
> ************************************************************************************
>
>
-- 
***********************************************************************************
Chao YUE
Laboratoire des Sciences du Climat et de l'Environnement (LSCE-IPSL)
UMR 1572 CEA-CNRS-UVSQ
Batiment 712 - Pe 119
91191 GIF Sur YVETTE Cedex
Tel: (33) 01 69 08 29 02; Fax:01.69.08.77.16
************************************************************************************

On Mon, Dec 10, 2012 at 2:18 PM, Tony Yu <ts...@gm...> wrote:
> Hi all,
>
> I'm not sure if non-core-developers are allowed to post MEPs, but I just
> did ;). MEP 12 outlines the reorganization of the example gallery and
> subsequent clean up of the examples:
>
> https://github.com/matplotlib/matplotlib/wiki/MEP12
>
> In my opinion, there are two open questions in the MEP:
>
> * Section names (may seem trivial to some, but I think it's really
> important)
> * Guidelines for cleaning up examples
>
> I've added proposed section names and clean-up guidelines to the MEP, but
> I'm sure these will evolve over time.
>
> Best,
> -Tony
>
>
Here here! I've been waiting for a really nasty, cold, and rainy weekend
here in Portland to make some PRs at least cleaning up the code contained
within the examples. Just hasn't happened yet ;)
 Tony, if you make your own branch for this, I'd be happy to contribute.
-paul

On Mon, Dec 10, 2012 at 5:32 PM, Chao YUE <cha...@gm...> wrote:
> The gallry will not include everything, could we also have somewhere to
> let "non-core" users freely share the code? like some features that are
> nice to have but not easily found in the galery? but hope this will not
> lead to overcrowded.
>
> Chao
>
Hi Chao,
This MEP only concerns the main gallery. I think user-contributed examples
were (are?) the intended focus of SciPy Central:
 http://scipy-central.org/
(and before that, the SciPy Cookbook). I'm not sure about the status of
SciPy Central. There was talk of a redesign, but I haven't seen any
progress since then.
 Best,
-Tony
> On Mon, Dec 10, 2012 at 11:18 PM, Tony Yu <ts...@gm...> wrote:
>
>> Hi all,
>>
>> I'm not sure if non-core-developers are allowed to post MEPs, but I just
>> did ;). MEP 12 outlines the reorganization of the example gallery and
>> subsequent clean up of the examples:
>>
>> https://github.com/matplotlib/matplotlib/wiki/MEP12
>>
>> In my opinion, there are two open questions in the MEP:
>>
>> * Section names (may seem trivial to some, but I think it's really
>> important)
>> * Guidelines for cleaning up examples
>>
>> I've added proposed section names and clean-up guidelines to the MEP, but
>> I'm sure these will evolve over time.
>>
>> Best,
>> -Tony
>>
>>
>> ------------------------------------------------------------------------------
>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>> Remotely access PCs and mobile devices and provide instant support
>> Improve your efficiency, and focus on delivering more value-add services
>> Discover what IT Professionals Know. Rescue delivers
>> http://p.sf.net/sfu/logmein_12329d2d
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>
>>
>
>
> --
>
> ***********************************************************************************
> Chao YUE
> Laboratoire des Sciences du Climat et de l'Environnement (LSCE-IPSL)
> UMR 1572 CEA-CNRS-UVSQ
> Batiment 712 - Pe 119
> 91191 GIF Sur YVETTE Cedex
> Tel: (33) 01 69 08 29 02; Fax:01.69.08.77.16
>
> ************************************************************************************
>
>

The gallry will not include everything, could we also have somewhere to let
"non-core" users freely share the code? like some features that are nice to
have but not easily found in the galery? but hope this will not lead to
overcrowded.
Chao
On Mon, Dec 10, 2012 at 11:18 PM, Tony Yu <ts...@gm...> wrote:
> Hi all,
>
> I'm not sure if non-core-developers are allowed to post MEPs, but I just
> did ;). MEP 12 outlines the reorganization of the example gallery and
> subsequent clean up of the examples:
>
> https://github.com/matplotlib/matplotlib/wiki/MEP12
>
> In my opinion, there are two open questions in the MEP:
>
> * Section names (may seem trivial to some, but I think it's really
> important)
> * Guidelines for cleaning up examples
>
> I've added proposed section names and clean-up guidelines to the MEP, but
> I'm sure these will evolve over time.
>
> Best,
> -Tony
>
>
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
-- 
***********************************************************************************
Chao YUE
Laboratoire des Sciences du Climat et de l'Environnement (LSCE-IPSL)
UMR 1572 CEA-CNRS-UVSQ
Batiment 712 - Pe 119
91191 GIF Sur YVETTE Cedex
Tel: (33) 01 69 08 29 02; Fax:01.69.08.77.16
************************************************************************************

Hi all,
I'm not sure if non-core-developers are allowed to post MEPs, but I just
did ;). MEP 12 outlines the reorganization of the example gallery and
subsequent clean up of the examples:
 https://github.com/matplotlib/matplotlib/wiki/MEP12
In my opinion, there are two open questions in the MEP:
 * Section names (may seem trivial to some, but I think it's really
important)
 * Guidelines for cleaning up examples
I've added proposed section names and clean-up guidelines to the MEP, but
I'm sure these will evolve over time.
Best,
-Tony