Skip to content

Doc v2 release notes #6994

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 27 commits into from
Sep 5, 2016
Merged

Conversation

tacaswell
Copy link
Member

This started out trying to write the release docs for v2.0 and I ended up re-arranging the documentation pretty aggressively.

This has the 3 commits from #6993 (which is what made iterating on this bearable).

@tacaswell tacaswell added this to the 2.0 (style change major release) milestone Aug 28, 2016
CocoaAgg backend removed
````````````````````````

The deprecated and not fully functional CocoaAgg backend has been removed
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing period.

@tacaswell
Copy link
Member Author

@QuLogic @efiring I am mostly working in dflt_style_changes.rst, can you do PRs with those changes?

however, the origin is from the (right, top) of the figure or axes,
analogous to negative indexing of sequences.

Optionally, you can specify arrow properties which draws an arrow
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"which draws" -> "for adding"

@tacaswell tacaswell force-pushed the doc_v2_release_notes branch from 959b812 to 89add4c Compare September 4, 2016 23:51
@efiring
Copy link
Member

efiring commented Sep 5, 2016

May I go ahead and merge this if it passes the tests? It's getting unwieldy; I think it would be better to make any additional related changes in another PR.

@tacaswell
Copy link
Member Author

Sure!

@efiring efiring merged commit a569f11 into matplotlib:v2.x Sep 5, 2016
@tacaswell tacaswell deleted the doc_v2_release_notes branch September 5, 2016 02:10
@tacaswell
Copy link
Member Author

@efiring can you do the v2.x merge into master so that devdocs will pick this up?

@efiring
Copy link
Member

efiring commented Sep 5, 2016

Sure, I'll try it right now. How bad could it be?...

@tacaswell
Copy link
Member Author

It looks like there are conflicts (as my new PR does not cleanly merge to master)...

@efiring
Copy link
Member

efiring commented Sep 5, 2016

Yes, at least one of them is easy; moving on to the others.

To use these for images where categories are specified as integers, for
instance, use::

plt.imshow(x, cmap='Dark2', norm=colors.NoNorm())
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the purpose of NoNorm in this example?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It just passes the values though without changing them instead of trying to normalize them to [0, 1].

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This helped me http://stackoverflow.com/questions/3034363/displaying-a-colored-2d-array-in-matplotlib-in-python:

The norm=NoNorm() argument avoids any scaling of the matrix values, so that 0 gets the first color in the list, 1 the second, etc.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you add NoNorm to this page: http://matplotlib.org/users/colormapnorms.html

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I'll have a look.

On Tue, Sep 6, 2016 at 1:39 AM, Thomas A Caswell notifications@github.com
wrote:

In doc/api/api_changes.rst
#6994 (comment):

+will be taken from matplotlib.rcParams. The previously-existing
+framealpha kwarg still controls the alpha transparency of the
+patch.
+
+
+Qualitative colormaps
+---------------------
+
+Colorbrewer's qualitative/discrete colormaps ("Accent", "Dark2", "Paired",
+"Pastel1", "Pastel2", "Set1", "Set2", "Set3") are now implemented as
+ListedColormap instead of LinearSegmentedColormap.
+
+To use these for images where categories are specified as integers, for
+instance, use::
+

  • plt.imshow(x, cmap='Dark2', norm=colors.NoNorm())

Could you add NoNorm to this page: http://matplotlib.org/users/
colormapnorms.html


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/matplotlib/matplotlib/pull/6994/files/6d97f09cd95ebb90d1aadb67238ca7eb121fa7c7#r77559531,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAMm9YuAaU42p7_fG3lsXM_5OPteN_3Bks5qnKg3gaJpZM4JvC49
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants