Make \versionadded and \versionchanged less prominant -- neither bold

freddrake · freddrake · commit 2116d983bfb2 · 1999-02-02T18:02:48.000Z
nor a separate paragraph.
diff --git a/Doc/perl/python.perl b/Doc/perl/python.perl
@@ -219,14 +219,14 @@ sub do_cmd_versionadded{
     # one parameter:  \versionadded{version}
     local($_) = @_;
     my $release = next_argument();
-    return "<b>New in version $release.</b><p>" . $_;
+    return "\nNew in version $release.\n" . $_;
 }
 
 sub do_cmd_versionchanged{
     # one parameter:  \versionchanged{version}
     local($_) = @_;
     my $release = next_argument();
-    return "<b>Changed in version $release.</b><p>" . $_;
+    return "\nChanged in version $release.\n" . $_;
 }
 
 # file and samp are at the end of this file since they screw up fontlock.
diff --git a/Doc/texinputs/python.sty b/Doc/texinputs/python.sty
@@ -746,15 +746,15 @@
 % This should be used to mark things which have been added to the
 % development tree but that aren't in the release, but are documented.
 % This allows release of documentation that already includes updated
-% descriptions.
+% descriptions.  Place at end of descriptor environment.
 %
 % Example:
 %  \versionadded{1.5.2}
 %
 \newcommand{\versionadded}[1]{%
-  \strong{New in version #1.}\par}
+  {  New in version #1.  }}
 \newcommand{\versionchanged}[1]{%
-  \strong{Changed in version #1.}\par}
+  {  Changed in version #1.  }}
 
 
 % Tables.
