##// END OF EJS Templates
Backport PR #2384: Adapt inline backend to changes in matplotlib...
Backport PR #2384: Adapt inline backend to changes in matplotlib Matplotlib recently merged https://github.com/matplotlib/matplotlib/pull/1125 that makes it simpler to use objective oriented figure creation by automatically creating the right canvas for the backend. To solve that all backends must provide a backend_xxx.FigureCanvas. This is obviosly missing from the inline backend. The change is needed to make the inline backend work with mpl's 1.2.x branch which is due to released soon. Simply setting the default canvas equal to a Agg canvas appears to work for both svg and png figures but I'm not sure weather that is the right approach. Should the canvas depend on the figure format and provide a svg canvas for a svg figure? (Note that before this change to matplotlib the canvas from a plt.figure call seams to be a agg type in all cases) Edit: I made the pull request against 0.13.1 since it would be good to have this in the stable branch for when mpl is released. Just let me know and I can rebase it against master

File last commit:

r4131:a7815b94
r8562:7d16877a
Show More
license_and_copyright.txt
97 lines | 3.6 KiB | text/plain | TextLexer
/ docs / source / about / license_and_copyright.txt
.. _license:
=====================
License and Copyright
=====================
License
=======
IPython is licensed under the terms of the new or revised BSD license, as
follows::
Copyright (c) 2011, IPython Development Team
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
Neither the name of the IPython Development Team nor the names of its
contributors may be used to endorse or promote products derived from this
software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
About the IPython Development Team
==================================
Fernando Perez began IPython in 2001 based on code from Janko Hauser
<jhauser-AT-zscout.de> and Nathaniel Gray <n8gray-AT-caltech.edu>. Fernando is still
the project lead.
The IPython Development Team is the set of all contributors to the IPython
project. This includes all of the IPython subprojects. Here is a list of the
currently active contributors:
* Matthieu Brucher
* Ondrej Certik
* Laurent Dufrechou
* Robert Kern
* Thomas Kluyver
* Brian E. Granger
* Evan Patterson
* Fernando Perez (project leader)
* Benjamin Ragan-Kelley
* Ville M. Vainio
* Gael Varoququx
* Stefan van der Walt
* Barry Wark
If your name is missing, please add it.
Our Copyright Policy
====================
IPython uses a shared copyright model. Each contributor maintains copyright
over their contributions to IPython. But, it is important to note that these
contributions are typically only changes (diffs/commits) to the repositories.
Thus, the IPython source code, in its entirety is not the copyright of any
single person or institution. Instead, it is the collective copyright of the
entire IPython Development Team. If individual contributors want to maintain a
record of what changes/contributions they have specific copyright on, they
should indicate their copyright in the commit message of the change, when they
commit the change to one of the IPython repositories.
Any new code contributed to IPython must be licensed under the BSD license or
a similar (MIT) open source license.
Miscellaneous
=============
Some files (DPyGetOpt.py, for example) may be licensed under different
conditions. Ultimately each file indicates clearly the conditions under which
its author/authors have decided to publish the code.
Versions of IPython up to and including 0.6.3 were released under the GNU
Lesser General Public License (LGPL), available at
http://www.gnu.org/copyleft/lesser.html.