'import pylab' works, plotting still fails #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…port removing import that is prone to circular imports
This adds a independent callback for units changes that both updates the data limits (relim) as well as the view limits (autoscale_view).
Cleanup to image.py.
Fix two cases of signed integer overflow.
…ions Api callback exceptions
Avoid having to compute a repr of the entire array whenever calling to_rgba_array with an array input (that repr would be generated when the call to to_rgba fails and needs to generate an error message; instead, first check whether the input is already an array). See comments for detail. Slightly improves the performance of wire3d_animation on mpl_cairo.
Making this explicit improves error message when user provides two args to the function.
Fix `text.set(bbox=None)`.
…mesg [MAINT] savefig only takes one args
Also fixes a bug in fill_between with masked data. In the modified test figures, the area in green is supposed to correspond to the part of the hatched area where the curve is below y=2. The new behavior is the correct one. Also fixes cbook._reshape2D for scalar object inputs. Before the fix, `plt.hist(None)` would fail with `x must have 2 or fewer dimensions`, which it does have. Now it fails with a bit later with `unsupported operands type(s) for +: 'NoneType' and 'float'`, which is hopefully clearer.
DOC: New style for fast plotting, updated performance docs
Don't pretend to support Google App Engine.
…_array Micro-optimization of to_rgba_array.
fix leaked exception in RRuleLocator.tick_values
Let dpi be set when saving JPEG using Agg backend
BLD: Drop python 3.3 from setup.py
ENH: Polar tick improvements
by checking file hash before exiting the download loop.
Fix download of freetype 2.6.1.
The logic with uniform_offsets seems a bit crazy but let's just reproduce it for now...
Fix passing shape (2,) input to Collections.set_offsets.
DOC: Update instructions on pandas converters
…ript Remove some unused scripts
Remove four unused variables in src/_path.h.
Move CONTRIBUTING.md to .github/ to declutter the root folder (https://help.github.com/articles/setting-guidelines-for-repository-contributors/) Ask for the backend in the ISSUE_TEMPLATE.md.
Minor fixes to github templates.
…tive-precode-default DOC: Include the default of "plot_pre_code" of the plot directive in the documentation
The profiled values are way outdated (they were computed back in 2008, so even the rendering strategy has changed), and if we want to have some speed benchmarks they should go to some more prominent place than a comment at the top of an example.
DOC: Remove scatter_profile example.
…me}. Docstrings: Emphasize the downsampling. Clarify when the defaults for rstride and cstride apply. Passing an infinite rcount and ccount is the easiest way to ensure the data does not get downsampled (which I still think is a misfeature, but that's a battle for another day), but would result in a stride of zero; instead, ensure that the stride is at least 1.
plot_surface docstring + edge case fix
This should prevent the automatic backports to be tested both when the branch is pushed by the backport bot, and when the PR is opened. Hopefully the PR will be still be tested (that's unclear from the AppVeyor docs). This was discussed in matplotlib#9283 (comment) And likely need to be also applied to other CI, but Appveyor is the most annoying.
CI: Ask Appveyor to ignore certain branches.
This should make it easier to debug exceptions falling out of the C++ code, as the C++ runtime will print the error message (the `what()` of the exception) on its way to aborting the program. Did a regex replace; removed the `char*` handler in CALL_CPP_FULL; and remove a bunch of extra whitespace.
Fix documents of semilogx and semilogy.
MNT: Throw std::runtime_exception instead of char* in C++ code
…nite x, y - Changed warning to verbose
We document pytest>=3.0 and it's easy enough to replace.
Don't use pytest.filterwarings, which needs pytest>=3.2.
In text, warn and return instead of raise exception for non-finite x, y
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
22 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
'import pylab' works using the pypy-hack branch from https://github.com/mattip/numpy
but fails when trying to plot, added min_depth, max_depth to pypy trunk to try to improve this