Thanks to visit codestin.com
Credit goes to github.com

Skip to content

next_whats_new

Directory actions

More options

Directory actions

More options

Latest commit

 

History

History

next_whats_new

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
3d_scales.rst
3d_scales.rst
 
 
3d_speedups.rst
3d_speedups.rst
 
 
README.rst
README.rst
 
 
axis_inversion.rst
axis_inversion.rst
 
 
bar_label_padding_update.rst
bar_label_padding_update.rst
 
 
barcontainer_properties.rst
barcontainer_properties.rst
 
 
box_arrow_size_controls.rst
box_arrow_size_controls.rst
 
 
broken_barh_align.rst
broken_barh_align.rst
 
 
callback_registry_disconnect_func.rst
callback_registry_disconnect_func.rst
 
 
color_cycle_from_sequence.rst
color_cycle_from_sequence.rst
 
 
colormap_bad_under_over.rst
colormap_bad_under_over.rst
 
 
colormap_with_alpha.rst
colormap_with_alpha.rst
 
 
cycler_rcparam_security.rst
cycler_rcparam_security.rst
 
 
depthshading_improvement.rst
depthshading_improvement.rst
 
 
figsize_unit.rst
figsize_unit.rst
 
 
font_alt_family_names.rst
font_alt_family_names.rst
 
 
font_features.rst
font_features.rst
 
 
gif_savefig.rst
gif_savefig.rst
 
 
grouped_bar.rst
grouped_bar.rst
 
 
hist_color.rst
hist_color.rst
 
 
ignore_system_fonts.rst
ignore_system_fonts.rst
 
 
last_resort_font.rst
last_resort_font.rst
 
 
legend_line_width.rst
legend_line_width.rst
 
 
libraqm.rst
libraqm.rst
 
 
log_contour_levels.rst
log_contour_levels.rst
 
 
logticks.rst
logticks.rst
 
 
mathnormal.rst
mathnormal.rst
 
 
new_rcparams_grid_options.rst
new_rcparams_grid_options.rst
 
 
okabe_ito_colormap.rst
okabe_ito_colormap.rst
 
 
partial_figsize_none.rst
partial_figsize_none.rst
 
 
patch_edgegapcolor.rst
patch_edgegapcolor.rst
 
 
patchcollection_legend.rst
patchcollection_legend.rst
 
 
pdf_fonts.rst
pdf_fonts.rst
 
 
pie_label.rst
pie_label.rst
 
 
pyplot-register-figure.rst
pyplot-register-figure.rst
 
 
radio_buttons_2d_grid.rst
radio_buttons_2d_grid.rst
 
 
scroll_to_zoom.rst
scroll_to_zoom.rst
 
 
separated_hatchcolor.rst
separated_hatchcolor.rst
 
 
six_and_eight_color_petroff_color_cycles.rst
six_and_eight_color_petroff_color_cycles.rst
 
 
sliders_callable_valfmt.rst
sliders_callable_valfmt.rst
 
 
snap_rotation.rst
snap_rotation.rst
 
 
stackplot_style_sequences.rst
stackplot_style_sequences.rst
 
 
streamplot_integration_control.rst
streamplot_integration_control.rst
 
 
streamplot_multiple_arrows.rst
streamplot_multiple_arrows.rst
 
 
subplots_adjust.rst
subplots_adjust.rst
 
 
tex_phantoms.rst
tex_phantoms.rst
 
 
text_language.rst
text_language.rst
 
 
ttc_fonts.rst
ttc_fonts.rst
 
 
twin_axes_zorder.rst
twin_axes_zorder.rst
 
 
type1_subset.rst
type1_subset.rst
 
 
underline-23616.rst
underline-23616.rst
 
 
updated_borderpad_parameter.rst
updated_borderpad_parameter.rst
 
 
violin_stats.rst
violin_stats.rst
 
 
violinplot_colors.rst
violinplot_colors.rst
 
 
webagg_capture_scroll.rst
webagg_capture_scroll.rst
 
 
xtick_ytick_rotation_modes.rst
xtick_ytick_rotation_modes.rst
 
 
zoom_boxes.rst
zoom_boxes.rst
 
 

README.rst

orphan:

Instructions for writing "What's new" entries

Each new feature (e.g. function, parameter, rcParam, config value, behavior, ...) must be described through a "What's new" entry.

Each entry is written into a separate file in the :file:`doc/release/next_whats_new/` directory. They are sorted and merged into :file:`whats_new.rst` during the release process.

When adding an entry please look at the currently existing files to see if you can extend any of them. If you create a file, name it something like :file:`cool_new_feature.rst` if you have added a brand new feature or something like :file:`updated_feature.rst` for extensions of existing features.

Include contents of the form:

Section title for feature
-------------------------

A description of the feature from the user perspective. This should include
what the feature allows users to do and how the feature is used. Technical
details should be left out when they do not impact usage, for example
implementation details.

The description may include a short instructive example, if it helps to
understand the feature.

Please avoid using references in section titles, as it causes links to be confusing in the table of contents. Instead, ensure that a reference is included in the descriptive text. Use inline literals (double backticks) to denote code objects in the title.