re-wrap before merging

Author: nedbat

developer-workflow/lang-changes.rst

@@ -4,21 +4,18 @@
 Changing Python
 ===============
 
-On occasion people come up with an idea for changing or improving Python.
-This page explains how to propose changes and what to expect during the
-process.
+On occasion people come up with an idea for changing or improving Python.  This
+page explains how to propose changes and what to expect during the process.
 
 
 Considerations
 --------------
 
-First, understand that changes to Python
-are difficult to make. When the language changes,
-**every** Python programmer and all Python programmers to
+First, understand that changes to Python are difficult to make. When the
+language changes, **every** Python programmer and all Python programmers to
 come will end up eventually learning about the change you want to propose.
 Books will need updating, code will be changed, and a new way to do things will
-need to be learned. Changes to Python are never taken
-lightly.
+need to be learned. Changes to Python are never taken lightly.
 
 Backward compatibility is a significant concern.  Existing Python code has to
 continue to work.  There are exceptions to this rule, but they are very rare
@@ -29,8 +26,9 @@ Because of the seriousness of changing the language, any change must be
 beneficial to many Python users. If the change only helps a small percentage of
 Python developers then the change will not be made. A good way to see if your
 idea would work for a large portion of the Python community is to discuss it in
-the `Ideas category in Discourse <ideas_>`_.  You can also look in Python's standard
-library to find examples of code which would benefit from your proposed change.
+the `Ideas category in Discourse <ideas_>`_.  You can also look in Python's
+standard library to find examples of code which would benefit from your
+proposed change.
 
 .. important::
    For all of these reasons, most proposed changes to Python are rejected.  This
@@ -58,9 +56,9 @@ Proposing a change involves the following steps:
 Describe your idea
 ^^^^^^^^^^^^^^^^^^
 
-The `Ideas category in Discourse <ideas_>`_ is specifically intended for discussion
-of new features and language changes. Make your proposal as a `new topic
-<ideas_>`_ there.
+The `Ideas category in Discourse <ideas_>`_ is specifically intended for
+discussion of new features and language changes. Make your proposal as a `new
+topic <ideas_>`_ there.
 
 Your proposal needs to be **detailed**. Describe the change you want to make,
 why you want to make it, and what benefits it will bring to Python users. Be
@@ -112,9 +110,9 @@ part of the process. Other people's perspectives will help explore the full
 impact of the idea and find strengths or weaknesses you may not have
 considered.
 
-You will almost always get at least some push-back.  Don't be disappointed, and don't take it personally.
-As the long list of :pep:`Withdrawn and Rejected PEPs
-<0#rejected-superseded-and-withdrawn-peps>` in the :pep:`PEP Index <0>`
+You will almost always get at least some push-back.  Don't be disappointed, and
+don't take it personally.  As the long list of :pep:`Withdrawn and Rejected
+PEPs <0#rejected-superseded-and-withdrawn-peps>` in the :pep:`PEP Index <0>`
 attests, and as befits a mature programming language, getting significant
 changes into Python isn't a simple task.