Skip to content

Fix Latin abbreviations in http.cookiejar and optparse docs #145291

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Anandesh-Sharma wants to merge 1 commit into
base: main
Choose a base branch
from
+7 −7
Open

Fix Latin abbreviations in http.cookiejar and optparse docs #145291

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions Doc/library/http.cookiejar.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down Expand Up @@ -574,15 +574,15 @@ 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).


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

Expand Down Expand Up @@ -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`.


Expand All @@ -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
Expand Down
4 changes: 2 additions & 2 deletions Doc/library/optparse.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
Loading