[matplotlib-devel] Matplotlib 1.0.1 release schedule (again)
Hey all, Not so long ago there was a brief discussion concerning the release schedule for 1.0.1[1]. As an Ubuntu user, I would really a mechanism for excluding examples requiring downloaded data from being built for the doc target. This would bring matplotlib into compliance with Debian packaging policy[3]. Cheers, - Ben [1] http://sourceforge.net/mailarchive/forum.php?thread_name=01aa01cb76eb$0d1d7ea0$27587be0$%40net&forum_name=matplotlib-devel [2] https://bugs.launchpad.net/ubuntu/+source/matplotlib/+bug/607395 [3] http://thread.gmane.org/gmane.comp.python.matplotlib.devel/8865 -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Matplotlib 1.0.1 release schedule (again)
On Sun, Nov 7, 2010 at 3:25 AM, Jouni K. Seppänen wrote: > So now on the 1.0 maintenance branch (coming soon to trunk, once I'm > done wrangling with svnmerge) you can set new rc parameters > examples.download to False and examples.directory to the directory where > you have a checkout of the sample data¹. Then get_sample_data will only > look in this directory and not download anything. > > Does this help with the Debian and Ubuntu builds? > I believe that should help. Hopefully someone on the bug with more knowledge of the policy will comment to confirm. - Ben -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Matplotlib 1.0.1 release schedule (again)
On Sun, 07 Nov 2010 10:25:13 +0200, Jouni K. Seppänen wrote: > So now on the 1.0 maintenance branch (coming soon to trunk, once I'm > done wrangling with svnmerge) you can set new rc parameters > examples.download to False and examples.directory to the directory where > you have a checkout of the sample data¹. Then get_sample_data will only > look in this directory and not download anything. > How would one set these during the build process? Is there a way to pass in rc parameters via environment variable? Perhaps we should just patch matplotlibrc.template in the tree? Any ideas would be appreciated, - Ben -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] Building documentation and matplotlibrc
This weekend I put a bit of time into bringing the Debian packaging[1] for the matplotlib 1.0 series up to date. In the tree it seems there is a matplotlibrc in the /doc directory. Judging from the documentation, it looks like matplotlib will first use a matplotlibrc in the current directory. This works very well for the case of packaging for Debian, since I can simply override the examples.* options here to avoid downloading the samples while building the documentation. In practice, however, I have run into a few issues. First, the comment regarding examples.directory indicates that this path must be absolute. Is this really true? For obvious reasons we don't know the absolute path of the samples until we actually build the package. I suppose an 'echo' in the packaging makefile could dynamically patch this path in, but a relative path would be far simpler. Secondly, it seems that the doc/matplotlibrc file is completely ignored. When I tried building with "examples.directory=../sampledata", I still saw multiple failed download attempts in the package build log. Indeed, even putting an invalid line in doc/matplotlibrc doesn't result in an error. For the record, the documentation build process is invoked with, cd doc ; MATPLOTLIBDATA=../lib/matplotlib/mpl-data/ \ PYTHONPATH=../build/lib.$(PY_PLATFORM)-$(DEFPY) ./make.py --small all Any suggestions would be greatly appreciated. - Ben [1] https://launchpad.net/~bgamari/+archive/matplotlib-unofficial -- What happens now with your Lotus Notes apps - do you make another costly upgrade, or settle for being marooned without product support? Time to move off Lotus Notes and onto the cloud with Force.com, apps are easier to build, use, and manage than apps on traditional platforms. Sign up for the Lotus Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Matplotlib 1.0.1 release schedule (again)
On Mon, 8 Nov 2010 14:01:26 -0600, John Hunter wrote: > I will try and get to the release ASAP and set the sample_data up this way... > Any news on this? A release would be very nice. I did the bulk of the work[1] to get the debian packaging working with the 1.0 series but I can't really do much else until there is an actual release to work against. - Ben [1] https://launchpad.net/~bgamari/+archive/matplotlib-unofficial Although this isn't quite working yet. More about this in another thread. -- What happens now with your Lotus Notes apps - do you make another costly upgrade, or settle for being marooned without product support? Time to move off Lotus Notes and onto the cloud with Force.com, apps are easier to build, use, and manage than apps on traditional platforms. Sign up for the Lotus Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Building documentation and matplotlibrc
On Sun, 05 Dec 2010 23:03:02 +0200, Jouni K. Seppänen wrote: > Ben Gamari > writes: > > > In practice, however, I have run into a few issues. First, the comment > > regarding examples.directory indicates that this path must be > > absolute. Is this really true? > > The comment is wrong: a relative path will work (I just tried this). > Awesome. Perhaps this should be corrected in the tree so it doesn't look like I'm blatantly violating the documentation? > > Secondly, it seems that the doc/matplotlibrc file is completely > > ignored. > > I am not intimately familiar with the doc build system, but the way that > the "html" function in make.py copies matplotlibrc from mpl-data to > _static, I suspect that it is trying to ensure that that particular file > is used. > Anyone else have further guidance? - Ben -- What happens now with your Lotus Notes apps - do you make another costly upgrade, or settle for being marooned without product support? Time to move off Lotus Notes and onto the cloud with Force.com, apps are easier to build, use, and manage than apps on traditional platforms. Sign up for the Lotus Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Building documentation and matplotlibrc
On Sun, 05 Dec 2010 23:03:02 +0200, Jouni K. Seppänen wrote: > Ben Gamari > writes: > > > In practice, however, I have run into a few issues. First, the comment > > regarding examples.directory indicates that this path must be > > absolute. Is this really true? > > The comment is wrong: a relative path will work (I just tried this). > Awesome. Perhaps this should be corrected in the tree so it doesn't look like I'm blatantly violating the documentation? > > Secondly, it seems that the doc/matplotlibrc file is completely > > ignored. > > I am not intimately familiar with the doc build system, but the way that > the "html" function in make.py copies matplotlibrc from mpl-data to > _static, I suspect that it is trying to ensure that that particular file > is used. > Anyone else have further guidance? - Ben -- This SF Dev2Dev email is sponsored by: WikiLeaks The End of the Free Internet http://p.sf.net/sfu/therealnews-com ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Building documentation and matplotlibrc
Sorry to the Benjamin Drung, Scott Kitterman, and Sandro Tosi for not including you in this thread earlier. I am trying to bring the matplotlib 1.0.1 packaging into compliance with the debian packaging requirements. Unfortunately, matplotlib now includes out-of-tree sample data which is downloaded during the documentation build process. To avoid this we need to override a setting in matplotlibrc during the documentation build and package these data in a separate source tarball. Most of this work has been done (see my PPA[1]) but unfortunately the configuration changes are non-trivial. On Sun, 5 Dec 2010 17:16:44 -0600, John Hunter wrote: > On Sun, Dec 5, 2010 at 3:14 PM, Ben Gamari wrote: > >> I am not intimately familiar with the doc build system, but the way that > >> the "html" function in make.py copies matplotlibrc from mpl-data to > >> _static, I suspect that it is trying to ensure that that particular file > >> is used. > >> > > Anyone else have further guidance? > > No, that is there so that the link from the customizing page > > http://matplotlib.sourceforge.net/users/customizing.html > > to the "download matplotlibrc" link > > http://matplotlib.sourceforge.net/_static/matplotlibrc > > works and gives an update matplotlibrc. It is not used in the doc > build to customize the settings of the docs. The files in _static are > just copied up to the web server but can be linked to from withing > rest. > I'm glad to hear that this file isn't used. This should make packaging much easier. That being said, I've tracked down the reason for the configuration in doc/matplotlibrc not being used. It seems that sphinx runs the examples in their current directory (I suppose this is to be expected). It seems that there is a (as far as I can tell undocumented, please fix this) MATPLOTLIBRC environment variable which can be used to override the location of the matplotlibrc used. This could be useful in specifying the matplotlibrc used during the documentation build process but unfortunately this would require an absolute path which, again, complicates the packaging (i.e. I don't know the best way to accomplish this). Suggestions? Thanks, - Ben [1] https://launchpad.net/~bgamari/+archive/matplotlib-unofficial -- This SF Dev2Dev email is sponsored by: WikiLeaks The End of the Free Internet http://p.sf.net/sfu/therealnews-com ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Building documentation and matplotlibrc
On Thu, 09 Dec 2010 18:37:34 +0200, Jouni K. Seppänen wrote:
> Ben Gamari writes:
>
> > That being said, I've tracked down the reason for the configuration in
> > doc/matplotlibrc not being used. It seems that sphinx runs the examples
> > in their current directory (I suppose this is to be expected).
> >
> > It seems that there is a (as far as I can tell undocumented, please fix
> > this) MATPLOTLIBRC environment variable which can be used to override
> > the location of the matplotlibrc used. This could be useful in
> > specifying the matplotlibrc used during the documentation build process
> > but unfortunately this would require an absolute path which, again,
> > complicates the packaging (i.e. I don't know the best way to accomplish
> > this). Suggestions?
>
> I don't see why the path must be absolute, though I haven't tried. Is
> there some problem having a different global matplotlibrc
> $HOME/.matplotlib/matplotlibrc or $MATPLOTLIBDATA/matplotlibrc,
> possibly setting $HOME or $MATPLOTLIBDATA from your build script?
An absolute path is necesary because the current working directory
changes for each example. To check this I added,
import sys
sys.stderr.write('SAMPLE cwd=%s\n'%os.getcwd())
sys.stderr.write('SAMPLE matplotlibrc=%s\n'%matplotlib.matplotlib_fname())
to the beginning of cbook.get_sample_data(). During the documentation
build I then saw output like,
reading sources... [ 12%] examples/api/date_demo
SAMPLE cwd=/home/bgamari/trees/matplotlib/matplotlib-1.0.1/examples/api
SAMPLE matplotlibrc=/home/bgamari/.matplotlib/matplotlibrc
reading sources... [ 12%] examples/api/date_index_formatter
SAMPLE cwd=/home/bgamari/trees/matplotlib/matplotlib-1.0.1/examples/api
SAMPLE matplotlibrc=/home/bgamari/.matplotlib/matplotlibrc
I suppose the only way around this is to patch the absolute path into
doc/matplotlibrc with sed, and then invoke doc/make.py with
MATPLOTLIBRC="$(CURDIR)/doc/matplotlibrc". I'm very confused how you
found that specifying a relative path in download.path worked. If the
cwd changes as seen above then the documentation was entirely correct in
claiming an absolute path is necessary. I really do wish there as a way
to prevent spinx from changing the cwd.
- Ben
--
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Building documentation and matplotlibrc
On Thu, 09 Dec 2010 20:00:39 +0200, Jouni K. Seppänen wrote: > Ben Gamari writes: > > > An absolute path is necesary because the current working directory > > changes for each example. > > Oh, right, the examples are in a lot of different subdirectories. > Precisely, this is the problem. Regardless, after making the necessary changes to use absolute paths (after painfully realizing that the MATPLOTLIB environment variable expects the directory of the desired matplotlibrc, not the file path; documentation would have been nice here) the configuration is _still_ having no effect. While matplotlib.matplotlib_fname() seems to be reporting the correct matplotlibrc path, examples.download is still True despite setting this to False in the file. I've placed a debug message writing to sys.stderr at the beginning of matplotlib.rc_params(), but unfortunately I have seen no output from it. Considering the rest of my debugging output works just fine, I'm quite confused. Is this function not invoked? Cheers, - Ben -- ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Building documentation and matplotlibrc
On Thu, 9 Dec 2010 12:57:49 -0600, John Hunter wrote: > On Thu, Dec 9, 2010 at 12:34 PM, Ben Gamari wrote: > > > Regardless, after making the necessary changes to use absolute paths > > (after painfully realizing that the MATPLOTLIB environment variable > > expects the directory of the desired matplotlibrc, not the file path; > > documentation would have been nice here) the configuration is _still_ > > having no effect. While matplotlib.matplotlib_fname() seems to be > > reporting the correct matplotlibrc path, examples.download is still True > > despite setting this to False in the file. > > Sorry to be joining this a bit late. Why do you need to set the > MATPLOTLIBRC variable. The file doc/matplotlibrc is used by the doc > build process, so if you patch in your changes there, you should be > good. It seems that this may have been broken from the beginning. After noticing that my changes were not taking effect, I added some debug output and found that sphinx was changing the current working directory (every example gets built with its own directory being the working directory). I fail to see how doc/matplotlibrc could be currently used given most examples are not built from doc/. > and these are picked up at build time since the rest table formatting > of the API docs depends on the latter setting. > Are you certain this configuration isn't leaking in from some other source? > And yes, the relative paths in sphinx doc builds are a major headache. Are you referring to the fact that sphinx's above-mentioned chdir behavior? Cheers, - Ben -- ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Building documentation and matplotlibrc
On Thu, 9 Dec 2010 13:39:41 -0600, John Hunter wrote: > On Thu, Dec 9, 2010 at 1:12 PM, Ben Gamari wrote: > > > It seems that this may have been broken from the beginning. After > > noticing that my changes were not taking effect, I added some debug > > output and found that sphinx was changing the current working directory > > (every example gets built with its own directory being the working > > directory). I fail to see how doc/matplotlibrc could be currently used > > given most examples are not built from doc/. > > Well, the matplotlibrc file is checked for when the python process is > started, and the current directory when matplotlib is imported is > used. Since we launch the build process in the doc directory next to > make.py, doc is the current working directory when the plot directive > extension is imported and this is used to build the examples. So it > is not the directory that the example is in that is important, but the > current directory when matplotlib is imported. > Ahh, so matplotlib is not reimported with every example? I was under the impression sphinx operated more like make (1 process per target). I suppose that explains it then. > On import the matplotlib.rc_params function is called to set > matplotlib.rcParams. The rc_params function in turn calls > matplotlib_fname, which does the following search > Any idea why my debugging messages are ineffective? Or, even better, any idea why setting the examples.download in doc/matplotlibrc isn't being reflected in rc_params? I'll examine this more closely in about 30 minutes once I make it to the office. Cheers, - Ben -- ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Building documentation and matplotlibrc
On Thu, 9 Dec 2010 14:09:41 -0600, John Hunter wrote: > On Thu, Dec 9, 2010 at 1:52 PM, Ben Gamari wrote: > > > Any idea why my debugging messages are ineffective? Or, even better, any > > idea why setting the examples.download in doc/matplotlibrc isn't being > > reflected in rc_params? I'll examine this more closely in about 30 > > minutes once I make it to the office. > > I am not sure. Perhaps it is working but in the confusion you never > had everything set right at the same time. Try setting in > doc/matplotlibrc > > examples.download : False > examples.directory : somedir/relative/to/doc > Already done. > Then flush the sphinx build directory and try again. Perhaps stick > some debug print in matplotlib.matplotlib_fname and > cbook.get_sample_data and let us know. I have already done this. This is how I know that rc_examples.download is set to True in get_sample_data(). It turns out the debugging messages I made reference to in my last message were being output and I just missed them in the noise. Right after matplotlib is initialized with matplotlib.rc_params() it seems that rcParams['examples.download'] is set to False as expected. By the time execution makes it to get_sample_data(), however, this value has somehow been set to True. To try identifying where this happens I have tried putting some debug output in RcParams.__setitem__(). Unfortunately this doesn't show anyone setting examples.download after the initial loading of matplotlibrc. Any ideas how/where this might get overridden? - Ben -- ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Building documentation and matplotlibrc
On Thu, 09 Dec 2010 15:42:18 -0500, Ben Gamari wrote: > To try identifying where this happens I have tried putting some debug > output in RcParams.__setitem__(). Unfortunately this doesn't show anyone > setting examples.download after the initial loading of matplotlibrc. Any > ideas how/where this might get overridden? > Found it! It seems that matplotlib's sphinx extension calls matplotlib.rcdefaults() after rendering each figure, thus resetting examples.download to True (as set in rcsetup.py). The documentation claims that this function will "Restore the default rc params - the ones that were created at matplotlib load time." Despite the apparent attempt at clarification in this docstring, it's still not clear what the "default rc params" actually are. Is this supposed to be the parameters loaded from matplotlibrc (which seems to be what the sphinx extension expects) or the factory default values? rcdefaults()'s implementation appears to implement the latter, updating rcParams from rcParamsDefault in rcsetup.py, which appears to describe the factory default values. Perhaps we should rcParamsDefault.update(rcParams) after loading matplotlibrc? - Ben -- ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Building documentation and matplotlibrc
On Thu, 09 Dec 2010 16:44:37 -0500, Ben Gamari wrote: > rcdefaults()'s implementation appears to implement the latter, updating > rcParams from rcParamsDefault in rcsetup.py, which appears to describe > the factory default values. Perhaps we should > rcParamsDefault.update(rcParams) after loading matplotlibrc? > As expected, doing the update of rcParamsDefault proposed above (patch below) allows the examples.download setting to persist throughout the documentation build. It seems like either the documentation build process or rcParamsDefault has been badly broken for a very long time. Is rcParamsDefault really supposed to be the factory defaults or is this just a bug? If the former, we will need to introduce a variant of matplotlib.rcdefaults() to reset the configuration to that specified in matplotlibrc. - Ben diff --git a/lib/matplotlib/__init__.py b/lib/matplotlib/__init__.py --- a/lib/matplotlib/__init__.py +++ b/lib/matplotlib/__init__.py @@ -764,13 +772,13 @@ Please do not ask for support with these customizations active. # this is the instance used by the matplotlib classes rcParams = rc_params() - -rcParamsDefault = RcParams([ (key, default) for key, (default, converter) in \ -defaultParams.iteritems() ]) - rcParams['ps.usedistiller'] = checkdep_ps_distiller(rcParams['ps.usedistiller']) rcParams['text.usetex'] = checkdep_usetex(rcParams['text.usetex']) +rcParamsDefault = RcParams([ (key, default) for key, (default, converter) in \ + defaultParams.iteritems() ]) +rcParamsDefault.update(rcParams) + def rc(group, **kwargs): """ Set the current rc params. Group is the grouping for the rc, eg. -- ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Building documentation and matplotlibrc
On Thu, 09 Dec 2010 23:55:05 +0200, Jouni K. Seppänen wrote: > Ben Gamari writes: > > > It seems that matplotlib's sphinx extension calls > > matplotlib.rcdefaults() after rendering each figure, thus resetting > > examples.download to True (as set in rcsetup.py). > > Right, and it sets figure.figsize after it. I guess you will want to set > examples.download in the same function. > NAK. This seems like an _awful_ hack. If the user specifies in matplotlibrc that they don't want to download sample data (or any preference for that matter), then they _really_ don't want to download sample data and we should take their word for this. It's one-time hacks like this that make matplotlib the nightmare to package that it is. Wholesale overriding of the user's preferences seems like a big no-no, even when it comes to generating documentation. If a particular example _absolutely needs_ to override a specific rc option then it should modify that option and only that option. After this, the configuration should be returned to the user's default. > > The documentation claims that this function will "Restore the default rc > > params - the ones that were created at matplotlib load time." > > > rcdefaults()'s implementation appears to implement the latter, updating > > rcParams from rcParamsDefault in rcsetup.py, which appears to describe > > the factory default values. Perhaps we should > > rcParamsDefault.update(rcParams) after loading matplotlibrc? > > I think you're better off modifying the sphinx extension. rcdefaults has > a useful purpose, and the extension is trying to use it for that > purpose: to avoid having the user's configuration mess up the > documentation. If you were to update rcParamsDefault with the > matplotlibrc parameters, you might accidentally change the example > output. > I'm not sure I understand what this purpose might be. If the user sets a preference, then they want that preference to be reflected in _all_ matplotlib output, including the examples. By overriding matplotlibrc, we are doing nothing but setting ourselves up to thoroughly confuse the user (not to mention lowly packagers like me). If the user takes a block of code from an example then he expects that the output in ipython will be identical to that generated in the documentation. If it is not, he's forced to embark on a wild goose chase through the code looking for the line where some developer thought their example was too good for my carefully chosen preferences (or simply give up in frustration). - Ben -- ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] 1.0.1 release
Hey all, Can we please have a 1.0.1 release? It would be really nice to finally have official 1.0 packages for ubuntu/debian. Cheers, - Ben -- Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] 1.0.1 release
On Sat, 18 Dec 2010 06:41:43 -0500, Ben Gamari wrote: > Hey all, > > Can we please have a 1.0.1 release? It would be really nice to finally > have official 1.0 packages for ubuntu/debian. > Pretty please with sugar on top? Cheers, - Ben -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] 1.0.1 release
On Sat, 1 Jan 2011 21:32:16 -0600, John Hunter wrote: > Sorry for the repeated delays. I have been out of the country (scipy india) > and then catching up and Christmas and New Years... I will try and block > out some time tomorrow for an rc... > Awesome. Thanks! - Ben -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] matplotlib 1.0.1rc available for testing, building
On Sun, 2 Jan 2011 23:25:12 +0100, Sandro Tosi wrote: > Maybe I just missed them, but I can't find in the tarball the data > files needed to run the examples without internet connection. I > thought it was decided to ship them directly in the tarball and so use > the examples.directory rc option to point to them at build-time and > avoid to download, but if they're not in the tarball :) > You might consider looking at my Ubuntu PPA[1] if you are going to work on packaging. I seem to have everything working at this point, so perhaps that can save you some work. Cheers, - Ben [1] https://launchpad.net/~bgamari/+archive/matplotlib-unofficial -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Building documentation and matplotlibrc
On Wed, 5 Jan 2011 16:00:40 -0600, John Hunter wrote: > Strange -- I'll try and test tonight with a machine disconnected from > the internet. Out of curiosity, what command/tool are you using to > monitor the internet requests? Ben, are you seeing the same problems? > It took me a long time to finally figure out how to get matplotlib to respect the wishes of the packaging. Ultimately I believe I got it working but unfortunately, it's been a while, so I'm not entirely sure what was necessary. If it helps, I believe the package in my PPA builds correctly. Sorry I don't have more time to investigate; things are quite hectic at the moment. Cheers, - Ben -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Empty scatter plot
On Tue, 15 Feb 2011 11:40:01 -0600, Benjamin Root wrote: > So, the question is, is this a bug or a feature? I personally believe that > empty data is a perfectly valid scenario and given that other matplotlib > functions handle it gracefully, we should make the collections object more > friendly to empty data. > I agree that this is certainly a bug. For instance, I have a short script which reads a stream of data from stdin and plots in realtime. Unfortunately this bug made it prohibitively difficult to add support for scatter plots. I'd definitely appreciate it if this were fixed. Cheers, - Ben -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] Website needs love
The website is quite out of date. Not only does it claim that the latest release is 1.0.0, but the link to the github repository appears to be broken (has unneeded .git at the end of it). Cheers, - Ben -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Website needs love
On Mon, 23 May 2011 09:35:57 -0400, Michael Droettboom wrote: > Generating the thumbnails has no additional requirements (it uses > matplotlib's image module to scale the images). However, it may be a > problem with multiprocessing -- the thumbnails are generated in parallel > on multi-core machines. I haven't had problems myself, but it seems > multiprocessing doesn't always work in certain environments. > > Can you do me a favor? Can you edit gen_gallery.py and replace the line > beginning with "pool.map" to just "map" and let me know if that resolves > this issue? If it does, perhaps we should not use multiprocessing here. > Given this seems to be one of the longer stages of the build process, I'd appreciate if if we identified and fixed the underlying problem and not simply sweep it under the rug. - Ben -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] [WISHLIST] Module documentation table of contents
Perhaps my greatest annoyance with the matplotlib HTML documentation is the simply absurd length of some of the module pages. For instance, the reference for the axes module[1] amounts to more than 150 printed pages (for lack of a better measure). Despite this length, there is no table of contents summarizing the methods in the module. Due to this I (and no doubt others) have spent innumerable hours wandering aimlessly looking for the function whose name I can't quite remember. Is there some way to get sphinx to produce a table of contents on each page produced? The current layout makes the HTML documentation completely unapproachable without Google. Cheers, - Ben -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
