Repository navigation
Conversation
|
This also addresses the doc issues in #8885 @choldgraf |
|
Nice! I'll give it a look when I'm back in Berkeley and will give some comments! (if you're looking for something to work on quickly, I noticed that you use single tickmarks for comments, while rST uses double backticks (``). Also make sure that you've always got whitespace around operators (e.g., |
| # it to keep the codes aligned with the vertices | ||
| ############################################################################### | ||
| # Here comes the tricky part -- we have to set up the vertex and path codes | ||
| # arrays using `plt.Path.MOVETO`, `plt.Path.LINETO` and `plt.Path.CLOSEPOLY` |
There was a problem hiding this comment.
`` double backticks for rST (do this here and in all subsequent uses of backticks)
| # v4 to our initial vertex (the `MOVETO` vertex), in order to close the | ||
| # polygon. | ||
| # | ||
| # Note: the vertex for `CLOSEPOLY` is ignored, but we still need a placeholder |
| # First we'll generate some sample data, in this case, four offset sine | ||
| # curves. | ||
| x = np.linspace(0, 2 * np.pi, 50) | ||
| offsets = np.linspace(0, 2*np.pi, 4, endpoint=False) |
| print(yy.shape) | ||
|
|
||
| ############################################################################### | ||
| # So `yy[:,i]` will give you the `i`-th offset sine curve. Let's set the |
There was a problem hiding this comment.
space after :, (sorry I'm being persnickety about this)
|
|
||
| ############################################################################### | ||
| # So `yy[:,i]` will give you the `i`-th offset sine curve. Let's set the | ||
| # default prop_cycle using `plt.rc`. We'll combine a color cycler and a |
There was a problem hiding this comment.
here could you try linking to rc with an rST :func: (or maybe just a :ref: since I believe rc isn't actually a function)? I think that'll make it link nicely in the docs
| ax0.plot(yy) | ||
| ax0.set_title('Set default color cycle to rgby') | ||
|
|
||
| ############################################################################### |
There was a problem hiding this comment.
We probably don't want the line of ###### here since we're plotting on the same figure
There was a problem hiding this comment.
just to clarify, in general we shouldn't split a single figure between two ####### blocks of code
|
Just had a closer look - it looks really nice. A few styling comments to take care of and then once the tests pass I'm +1. Lemme know when you take care of that @johnh2o2 |
|
Ping! This definitely would be a nice improvement to have. Let us know if you are having difficulties with rebasing. |
Remove start_event_loop_default. Let pause() run the event loop for all backends.
Fix matplotlib corrupting PySide
Fix matplotlib corrupting PySide
Fix osx busy cursor
- put draw_idle in the base canvas resize event - re-order our resize handling and Qt's resize handling (let Qt go first) - do not call processEvents from inside of the paint event (this maybe the critical fix)
CI: Tweak conda installation on appveyor
Convert tick-setting methods to docstrings
Don't fail on empty autoscale_None.
Convert tick-setting methods to docstrings
|
pinging @johnh2o2 :-) |
* deleted circled in green * deleted space * removed blue box
Errorbar bugfix
Update doc strings
DOC: Add descriptions for remaining event handling examples
Fix typo of pixels in legend_handler.py
Update descriptions for images_contours_and_fields
FIX: poorly done deprecation in image.py.
Fix edgecolor being only applied to first bar.
… to tutorials, edit to animations/histogram
…ow. Edited whats_new_1.5.rst to reflect changed location of the color_cycle.py from color/ to tutorials/02_intermediate
…termediate folder
|
Hey @choldgraf , so I'm not sure that I've done things correctly with the rebasing....I apologize if I've caused more problems... (I THINK) I've rebased with the upstream/master branch, but now running Not sure if this is a result of failed rebasing or if these are acceptable warnings or what. Let me know what I should (or shouldn't) do on my end. Thanks! John |
|
whoah! it looks like there are now 636 files changed so that is almost certainly not correct haha. To be honest I think your best bet is to copy the test from the example that you've added (AKA the changes that were part of this initial PR), and start from scratch. I know that's a pain but it sounds like something very strange happened with the rebase. How did you do the rebase? The correct commands from your fork would have been: |
PR Summary
Scipy 2017 sprint! Working on improving the documentation with better
sphinx-gallery integration. I've added some more documentation to
the
examples/animation/animated_histogramand theexamples/color/color_cyclesections. I've also moved thecolor_cyclefromexamples/colortotutorials/02_Intermediate, since it seemed more like something users would be interested in doing regularly, and I've worded it more like a tutorial. Not sure how people feel about that.PR Checklist