From db6be30ae341f6fd3e7732f02dfa70201bc4538e Mon Sep 17 00:00:00 2001 From: Anandesh Sharma Date: Fri, 27 Feb 2026 04:10:25 +0530 Subject: [PATCH] =?UTF-8?q?Fix=20Latin=20abbreviations:=20"eg."=20?= =?UTF-8?q?=E2=86=92=20"e.g."=20and=20"ie."=20=E2=86=92=20"i.e."=20in=20do?= =?UTF-8?q?cs?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The Latin abbreviations "e.g." (exempli gratia) and "i.e." (id est) require periods after each letter. Fix instances in http.cookiejar and optparse documentation. Co-Authored-By: Claude Opus 4.6 --- Doc/library/http.cookiejar.rst | 10 +++++----- Doc/library/optparse.rst | 4 ++-- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/Doc/library/http.cookiejar.rst b/Doc/library/http.cookiejar.rst index 5ee783b7fae950..25f4fdb806acba 100644 --- a/Doc/library/http.cookiejar.rst +++ b/Doc/library/http.cookiejar.rst @@ -26,7 +26,7 @@ introduced with RFC 2965. .. note:: The various named parameters found in :mailheader:`Set-Cookie` and - :mailheader:`Set-Cookie2` headers (eg. ``domain`` and ``expires``) are + :mailheader:`Set-Cookie2` headers (e.g. ``domain`` and ``expires``) are conventionally referred to as :dfn:`attributes`. To distinguish them from Python attributes, the documentation for this module uses the term :dfn:`cookie-attribute` instead. @@ -574,7 +574,7 @@ both flags are set). .. attribute:: DefaultCookiePolicy.DomainStrictNoDots - When setting cookies, the 'host prefix' must not contain a dot (eg. + When setting cookies, the 'host prefix' must not contain a dot (e.g. ``www.foo.bar.com`` can't set a cookie for ``.bar.com``, because ``www.foo`` contains a dot). @@ -582,7 +582,7 @@ both flags are set). .. attribute:: DefaultCookiePolicy.DomainStrictNonDomain Cookies that did not explicitly specify a ``domain`` cookie-attribute can only - be returned to a domain equal to the domain that set the cookie (eg. + be returned to a domain equal to the domain that set the cookie (e.g. ``spam.example.com`` won't be returned cookies from ``example.com`` that had no ``domain`` cookie-attribute). @@ -642,7 +642,7 @@ internal consistency, so you should know what you're doing if you do that. .. attribute:: Cookie.port - String representing a port or a set of ports (eg. '80', or '80,8080'), or + String representing a port or a set of ports (e.g. '80', or '80,8080'), or :const:`None`. @@ -653,7 +653,7 @@ internal consistency, so you should know what you're doing if you do that. .. attribute:: Cookie.path - Cookie path (a string, eg. ``'/acme/rocket_launchers'``). + Cookie path (a string, e.g. ``'/acme/rocket_launchers'``). .. attribute:: Cookie.secure diff --git a/Doc/library/optparse.rst b/Doc/library/optparse.rst index 905212965bd70f..ab96ab9d894bba 100644 --- a/Doc/library/optparse.rst +++ b/Doc/library/optparse.rst @@ -1770,13 +1770,13 @@ where you can access some other interesting data through its instance attributes: ``parser.largs`` - the current list of leftover arguments, ie. arguments that have been + the current list of leftover arguments, i.e. arguments that have been consumed but are neither options nor option arguments. Feel free to modify ``parser.largs``, e.g. by adding more arguments to it. (This list will become ``args``, the second return value of :meth:`~OptionParser.parse_args`.) ``parser.rargs`` - the current list of remaining arguments, ie. with ``opt_str`` and + the current list of remaining arguments, i.e. with ``opt_str`` and ``value`` (if applicable) removed, and only the arguments following them still there. Feel free to modify ``parser.rargs``, e.g. by consuming more arguments.