[matplotlib-devel] Is cbook public?

2013-01-07 Thread Nelle Varoquaux
Hello everyone, I was recently looking at the cbook module, and I was wondering whether this module was public or not. I think there are several unused method in it, such as ``unmasked_index_ranges``. If this isn't public, it may be worth cleaning the module a bit and removing the unused method.

Re: [matplotlib-devel] Is cbook public?

2013-01-07 Thread Benjamin Root
Yes, it is public, but it is geared for internal use. -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200

Re: [matplotlib-devel] Is cbook public?

2013-01-07 Thread Michael Droettboom
I know there's a lot of code in the wild that treats cbook as public and would probably be affected by it going away. However, there hasn't been much care taken within that module as to what we want to support publicly and what would be better left as private. Many things in it, of course, ar

Re: [matplotlib-devel] Is cbook public?

2013-01-07 Thread Nelle Varoquaux
On 7 January 2013 16:38, Michael Droettboom wrote: > I know there's a lot of code in the wild that treats cbook as public and > would probably be affected by it going away. However, there hasn't been > much care taken within that module as to what we want to support > publicly and what would be b

[matplotlib-devel] autoconf+python

2013-01-07 Thread Benjamin Root
I was just reading some comments from Richard Stallman on ./ when I noticed that he pointed out a useful autoconf feature that was added somewhat recently. Essentially, this feature would allow one to do a build/install of a python module using the "./configure; make install" approach, if one choo

Re: [matplotlib-devel] autoconf+python

2013-01-07 Thread Thomas Kluyver
On 7 January 2013 16:57, Benjamin Root wrote: > I was just reading some comments from Richard Stallman on ./ when I > noticed that he pointed out a useful autoconf feature that was added > somewhat recently. Essentially, this feature would allow one to do a > build/install of a python module usi

Re: [matplotlib-devel] autoconf+python

2013-01-07 Thread Benjamin Root
On Mon, Jan 7, 2013 at 12:11 PM, Thomas Kluyver wrote: > On 7 January 2013 16:57, Benjamin Root wrote: > >> I was just reading some comments from Richard Stallman on ./ when I >> noticed that he pointed out a useful autoconf feature that was added >> somewhat recently. Essentially, this feature

Re: [matplotlib-devel] Is cbook public?

2013-01-07 Thread Michael Droettboom
On 01/07/2013 11:05 AM, Nelle Varoquaux wrote: > On 7 January 2013 16:38, Michael Droettboom wrote: >> I know there's a lot of code in the wild that treats cbook as public and >> would probably be affected by it going away. However, there hasn't been >> much care taken within that module as to wh

Re: [matplotlib-devel] autoconf+python

2013-01-07 Thread Eric Firing
On 2013/01/07 7:24 AM, Benjamin Root wrote: > > > On Mon, Jan 7, 2013 at 12:11 PM, Thomas Kluyver > wrote: > > On 7 January 2013 16:57, Benjamin Root > wrote: > > I was just reading some comments from Richard Stallman on ./ >

Re: [matplotlib-devel] autoconf+python

2013-01-07 Thread Michael Droettboom
On 01/07/2013 12:24 PM, Benjamin Root wrote: On Mon, Jan 7, 2013 at 12:11 PM, Thomas Kluyver > wrote: On 7 January 2013 16:57, Benjamin Root mailto:ben.r...@ou.edu>> wrote: I was just reading some comments from Richard Stallman on ./ when I no

Re: [matplotlib-devel] autoconf+python

2013-01-07 Thread Eric Firing
On 2013/01/07 7:29 AM, Michael Droettboom wrote: > I, also, am not too much up on the details --- but I think if it's > possible for "make install" to just call "python setup.py install" under > the hood, I'd have no objections. I think I would even object to that. What would be the point of it?

Re: [matplotlib-devel] autoconf+python

2013-01-07 Thread Matěj Týč
On Po, 2013-01-07 at 07:38 -1000, Eric Firing wrote: > On 2013/01/07 7:29 AM, Michael Droettboom wrote: > > I, also, am not too much up on the details --- but I think if it's > > possible for "make install" to just call "python setup.py install" under > > the hood, I'd have no objections. > > I t

Re: [matplotlib-devel] autoconf+python

2013-01-07 Thread Michael Droettboom
On 01/07/2013 12:38 PM, Eric Firing wrote: > On 2013/01/07 7:29 AM, Michael Droettboom wrote: >> I, also, am not too much up on the details --- but I think if it's >> possible for "make install" to just call "python setup.py install" under >> the hood, I'd have no objections. > I think I would even

Re: [matplotlib-devel] autoconf+python

2013-01-07 Thread Michiel de Hoon
If we use autoconf for matplotlib, we may end up using a different compiler (or compiler options) than what was used to compile Python itself. This can lead to incompatibilities that will be very hard to figure out. As far as I understand, using setup.py by default uses the same compiler and app