traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

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

nor a separate paragraph.
This commit is contained in:
Fred Drake 1999-02-02 18:02:48 +00:00
parent d0bceeeb59
commit 2116d983bf
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Doc/perl/python.perl
View File

@ -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.

6
Doc/texinputs/python.sty
View File

@ -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.