svn path=/trunk/matplotlib/; revision=8404

When matplotlib is compiled without -DNDEBUG, we get this error on one of the example:$ python stix_fonts_demo.pypython2.6: CXX/cxx_extensions.cxx:1320: virtual Py::PythonExtensionBase::~PythonExtensionBase(): Assertion `ob_refcnt == 0' failed.Abortedsvn path=/trunk/matplotlib/; revision=8405

svn path=/trunk/matplotlib/; revision=8406

svn path=/trunk/matplotlib/; revision=8407

svn path=/trunk/matplotlib/; revision=8408

svn path=/trunk/matplotlib/; revision=8411

svn path=/trunk/matplotlib/; revision=8412

…h by C. Gohlke.svn path=/trunk/matplotlib/; revision=8413

…covered by Jason Grout in the mailing list thread "Plots shifted up or to the left a pixel or so"svn path=/trunk/matplotlib/; revision=8414

…l-snapping.svn path=/trunk/matplotlib/; revision=8415

src/path_cleanup.cpp in revision 6897.svn path=/trunk/matplotlib/; revision=8416

…stead.svn path=/trunk/matplotlib/; revision=8417

… to Erik Tollerudsvn path=/trunk/matplotlib/; revision=8418

svn path=/trunk/matplotlib/; revision=8419

… mode.By default, the behavior of show() is unchanged--it does not block, andit forces interactive mode on.  show(block=True) is intended to makeit behave the same as in the other common backends, blocking untilall figures have been closed.svn path=/trunk/matplotlib/; revision=8420

svn path=/trunk/matplotlib/; revision=8421

svn path=/trunk/matplotlib/; revision=8422

svn path=/trunk/matplotlib/; revision=8423

It closes all windows; in the case of Tk, this calls the root.destroy()function, which should prevent the PyEval_RestoreThread error on Win.  Seehttp://mail.python.org/pipermail/python-bugs-list/2002-November/014207.htmlThis changeset also refactors the close() functionality intothree Gcf methods, fixing a bug (or inconsistency) in which callingclose with a figure number failed to call mpl_disconnect.svn path=/trunk/matplotlib/; revision=8424

svn path=/trunk/matplotlib/; revision=8425

svn path=/trunk/matplotlib/; revision=8426

svn path=/trunk/matplotlib/; revision=8427

…talion)svn path=/trunk/matplotlib/; revision=8428

svn path=/trunk/matplotlib/; revision=8429

svn path=/trunk/matplotlib/; revision=8430

svn path=/trunk/matplotlib/; revision=8431

…nd Winsvn path=/trunk/matplotlib/; revision=8432

Reported by Huziy Oleksandr.svn path=/trunk/matplotlib/; revision=8433

Also convert some imports to absolute.svn path=/trunk/matplotlib/; revision=8434

…next timesvn path=/trunk/matplotlib/; revision=8435

svn path=/branches/v1_0_maint/; revision=8884

…64-bit Pythons, and deprecated for Python 3.svn path=/branches/v1_0_maint/; revision=8886

…youtsvn path=/branches/v1_0_maint/; revision=8889

…d to the development branch.This fixes a math domain error when using log scales.svn path=/branches/v1_0_maint/; revision=8891

…ramssvn path=/branches/v1_0_maint/; revision=8892

svn path=/branches/v1_0_maint/; revision=8893

svn path=/branches/v1_0_maint/; revision=8895

svn path=/branches/v1_0_maint/; revision=8897

svn path=/branches/v1_0_maint/; revision=8899

…ould get one release too many.svn path=/branches/v1_0_maint/; revision=8902

svn path=/branches/v1_0_maint/; revision=8906

svn path=/branches/v1_0_maint/; revision=8907

svn path=/branches/v1_0_maint/; revision=8908

…880692.svn path=/branches/v1_0_maint/; revision=8911

svn path=/branches/v1_0_maint/; revision=8913

svn path=/branches/v1_0_maint/; revision=8917

…847.To avoid misplaced boundaries and artifacts with alpha < 1, we do notstroke the pcolor and contourf patch boundaries by default; but withoutthat stroking, antialiasing produces boundary artifacts that tend tobe visually disturbing.  Therefore we sacrifice antialiasing for thesepatches.svn path=/branches/v1_0_maint/; revision=8920

svn path=/branches/v1_0_maint/; revision=8926

…rmap (values between -1 and 0 were being made positive due to an int cast).Thanks to Eoghan Harrington for discovering and supplying the patch!svn path=/branches/v1_0_maint/; revision=8931

…ere not initialized properly.Thanks to LittleBigBrain for reporting and Friedrich Romstedt for making the original patch.svn path=/branches/v1_0_maint/; revision=8933

svn path=/branches/v1_0_maint/; revision=8939

svn path=/branches/v1_0_maint/; revision=8953

svn path=/branches/v1_0_maint/; revision=8955

This marks all commits in v0.91.x, v0.98.x, and v0.99.x as mergedinto v1.0.x.