python-docs-tr/howto/argparse.po at 3.11 · python/python-docs-tr

541 lines (448 loc) · 15.3 KB
# Python Documentation Turkish Translation
# Copyright (C) 2001-2023, Python Software Foundation
# This file is distributed under the same license as the Python package.
"Project-Id-Version: Python 3.11\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-09-18 19:05+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: \n"
"Language-Team: TURKISH <python.docs.tr@gmail.com>\n"
"Language: tr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: howto/argparse.rst:5
msgid "Argparse Tutorial"
#: howto/argparse.rst:0
msgid "author"
#: howto/argparse.rst:7
msgid "Tshepang Lekhonkhobe"
#: howto/argparse.rst:11
"This tutorial is intended to be a gentle introduction to :mod:`argparse`, "
"the recommended command-line parsing module in the Python standard library."
#: howto/argparse.rst:16
"There are two other modules that fulfill the same task, namely :mod:`getopt` "
"(an equivalent for ``getopt()`` from the C language) and the deprecated :mod:"
"`optparse`. Note also that :mod:`argparse` is based on :mod:`optparse`, and "
"therefore very similar in terms of usage."
#: howto/argparse.rst:24
msgid "Concepts"
#: howto/argparse.rst:26
"Let's show the sort of functionality that we are going to explore in this "
"introductory tutorial by making use of the :command:`ls` command:"
#: howto/argparse.rst:48
msgid "A few concepts we can learn from the four commands:"
#: howto/argparse.rst:50
"The :command:`ls` command is useful when run without any options at all. It "
"defaults to displaying the contents of the current directory."
#: howto/argparse.rst:53
"If we want beyond what it provides by default, we tell it a bit more. In "
"this case, we want it to display a different directory, ``pypy``. What we "
"did is specify what is known as a positional argument. It's named so because "
"the program should know what to do with the value, solely based on where it "
"appears on the command line. This concept is more relevant to a command "
"like :command:`cp`, whose most basic usage is ``cp SRC DEST``. The first "
"position is *what you want copied,* and the second position is *where you "
"want it copied to*."
#: howto/argparse.rst:62
"Now, say we want to change behaviour of the program. In our example, we "
"display more info for each file instead of just showing the file names. The "
"``-l`` in that case is known as an optional argument."
#: howto/argparse.rst:66
"That's a snippet of the help text. It's very useful in that you can come "
"across a program you have never used before, and can figure out how it works "
"simply by reading its help text."
#: howto/argparse.rst:72
msgid "The basics"
#: howto/argparse.rst:74
msgid "Let us start with a very simple example which does (almost) nothing::"
#: howto/argparse.rst:188 howto/argparse.rst:209
msgid "Following is a result of running the code:"
#: howto/argparse.rst:254 howto/argparse.rst:298
msgid "Here is what is happening:"
#: howto/argparse.rst:99
"Running the script without any options results in nothing displayed to "
"stdout. Not so useful."
#: howto/argparse.rst:102
"The second one starts to display the usefulness of the :mod:`argparse` "
"module. We have done almost nothing, but already we get a nice help message."
#: howto/argparse.rst:105
"The ``--help`` option, which can also be shortened to ``-h``, is the only "
"option we get for free (i.e. no need to specify it). Specifying anything "
"else results in an error. But even then, we do get a useful usage message, "
"also for free."
#: howto/argparse.rst:112
msgid "Introducing Positional arguments"
#: howto/argparse.rst:114
msgid "An example::"
#: howto/argparse.rst:122
msgid "And running the code:"
#: howto/argparse.rst:140
msgid "Here is what's happening:"
#: howto/argparse.rst:142
"We've added the :meth:`~ArgumentParser.add_argument` method, which is what "
"we use to specify which command-line options the program is willing to "
"accept. In this case, I've named it ``echo`` so that it's in line with its "
"function."
#: howto/argparse.rst:146
msgid "Calling our program now requires us to specify an option."
#: howto/argparse.rst:148
"The :meth:`~ArgumentParser.parse_args` method actually returns some data "
"from the options specified, in this case, ``echo``."
#: howto/argparse.rst:151
"The variable is some form of 'magic' that :mod:`argparse` performs for free "
"(i.e. no need to specify which variable that value is stored in). You will "
"also notice that its name matches the string argument given to the method, "
"``echo``."
#: howto/argparse.rst:156
"Note however that, although the help display looks nice and all, it "
"currently is not as helpful as it can be. For example we see that we got "
"``echo`` as a positional argument, but we don't know what it does, other "
"than by guessing or by reading the source code. So, let's make it a bit more "
#: howto/argparse.rst:167
msgid "And we get:"
#: howto/argparse.rst:180
msgid "Now, how about doing something even more useful::"
#: howto/argparse.rst:198
"That didn't go so well. That's because :mod:`argparse` treats the options we "
"give it as strings, unless we tell it otherwise. So, let's tell :mod:"
"`argparse` to treat that input as an integer::"
#: howto/argparse.rst:219
"That went well. The program now even helpfully quits on bad illegal input "
"before proceeding."
#: howto/argparse.rst:224
msgid "Introducing Optional arguments"
#: howto/argparse.rst:226
"So far we have been playing with positional arguments. Let us have a look on "
"how to add optional ones::"
#: howto/argparse.rst:282 howto/argparse.rst:432
msgid "And the output:"
#: howto/argparse.rst:256
"The program is written so as to display something when ``--verbosity`` is "
"specified and display nothing when not."
#: howto/argparse.rst:259
"To show that the option is actually optional, there is no error when running "
"the program without it. Note that by default, if an optional argument isn't "
"used, the relevant variable, in this case ``args.verbosity``, is given "
"``None`` as a value, which is the reason it fails the truth test of the :"
"keyword:`if` statement."
#: howto/argparse.rst:265
msgid "The help message is a bit different."
#: howto/argparse.rst:267
"When using the ``--verbosity`` option, one must also specify some value, any "
#: howto/argparse.rst:270
"The above example accepts arbitrary integer values for ``--verbosity``, but "
"for our simple program, only two values are actually useful, ``True`` or "
"``False``. Let's modify the code accordingly::"
#: howto/argparse.rst:300
"The option is now more of a flag than something that requires a value. We "
"even changed the name of the option to match that idea. Note that we now "
"specify a new keyword, ``action``, and give it the value ``\"store_true\"``. "
"This means that, if the option is specified, assign the value ``True`` to "
"``args.verbose``. Not specifying it implies ``False``."
#: howto/argparse.rst:307
"It complains when you specify a value, in true spirit of what flags actually "
#: howto/argparse.rst:310
msgid "Notice the different help text."
#: howto/argparse.rst:314
msgid "Short options"
#: howto/argparse.rst:316
"If you are familiar with command line usage, you will notice that I haven't "
"yet touched on the topic of short versions of the options. It's quite "
#: howto/argparse.rst:328
msgid "And here goes:"
#: howto/argparse.rst:341
msgid "Note that the new ability is also reflected in the help text."
#: howto/argparse.rst:345
msgid "Combining Positional and Optional arguments"
#: howto/argparse.rst:347
msgid "Our program keeps growing in complexity::"
#: howto/argparse.rst:362
msgid "And now the output:"
#: howto/argparse.rst:376
msgid "We've brought back a positional argument, hence the complaint."
#: howto/argparse.rst:378
msgid "Note that the order does not matter."
#: howto/argparse.rst:380
"How about we give this program of ours back the ability to have multiple "
"verbosity values, and actually get to use them::"
#: howto/argparse.rst:414
"These all look good except the last one, which exposes a bug in our program. "
"Let's fix it by restricting the values the ``--verbosity`` option can "
#: howto/argparse.rst:450
"Note that the change also reflects both in the error message as well as the "
"help string."
#: howto/argparse.rst:453
"Now, let's use a different approach of playing with verbosity, which is "
"pretty common. It also matches the way the CPython executable handles its "
"own verbosity argument (check the output of ``python --help``)::"
#: howto/argparse.rst:472
"We have introduced another action, \"count\", to count the number of "
"occurrences of specific options."
#: howto/argparse.rst:501
"Yes, it's now more of a flag (similar to ``action=\"store_true\"``) in the "
"previous version of our script. That should explain the complaint."
#: howto/argparse.rst:504
msgid "It also behaves similar to \"store_true\" action."
#: howto/argparse.rst:506
"Now here's a demonstration of what the \"count\" action gives. You've "
"probably seen this sort of usage before."
#: howto/argparse.rst:509
"And if you don't specify the ``-v`` flag, that flag is considered to have "
"``None`` value."
#: howto/argparse.rst:512
"As should be expected, specifying the long form of the flag, we should get "
"the same output."
#: howto/argparse.rst:515
"Sadly, our help output isn't very informative on the new ability our script "
"has acquired, but that can always be fixed by improving the documentation "
"for our script (e.g. via the ``help`` keyword argument)."
#: howto/argparse.rst:519
msgid "That last output exposes a bug in our program."
#: howto/argparse.rst:522
msgid "Let's fix::"
#: howto/argparse.rst:541
msgid "And this is what it gives:"
#: howto/argparse.rst:556
"First output went well, and fixes the bug we had before. That is, we want "
"any value >= 2 to be as verbose as possible."
#: howto/argparse.rst:559
msgid "Third output not so good."
#: howto/argparse.rst:561
msgid "Let's fix that bug::"
#: howto/argparse.rst:578
"We've just introduced yet another keyword, ``default``. We've set it to "
"``0`` in order to make it comparable to the other int values. Remember that "
"by default, if an optional argument isn't specified, it gets the ``None`` "
"value, and that cannot be compared to an int value (hence the :exc:"
"`TypeError` exception)."
#: howto/argparse.rst:585
msgid "And:"
#: howto/argparse.rst:592
"You can go quite far just with what we've learned so far, and we have only "
"scratched the surface. The :mod:`argparse` module is very powerful, and "
"we'll explore a bit more of it before we end this tutorial."
#: howto/argparse.rst:599
msgid "Getting a little more advanced"
#: howto/argparse.rst:601
"What if we wanted to expand our tiny program to perform other powers, not "
"just squares::"
#: howto/argparse.rst:656
msgid "Output:"
#: howto/argparse.rst:639
"Notice that so far we've been using verbosity level to *change* the text "
"that gets displayed. The following example instead uses verbosity level to "
"display *more* text instead::"
#: howto/argparse.rst:670
msgid "Conflicting options"
#: howto/argparse.rst:672
"So far, we have been working with two methods of an :class:`argparse."
"ArgumentParser` instance. Let's introduce a third one, :meth:"
"`~ArgumentParser.add_mutually_exclusive_group`. It allows for us to specify "
"options that conflict with each other. Let's also change the rest of the "
"program so that the new functionality makes more sense: we'll introduce the "
"``--quiet`` option, which will be the opposite of the ``--verbose`` one::"
#: howto/argparse.rst:698
"Our program is now simpler, and we've lost some functionality for the sake "
"of demonstration. Anyways, here's the output:"
#: howto/argparse.rst:716
"That should be easy to follow. I've added that last output so you can see "
"the sort of flexibility you get, i.e. mixing long form options with short "
"form ones."
#: howto/argparse.rst:720
"Before we conclude, you probably want to tell your users the main purpose of "
"your program, just in case they don't know::"
#: howto/argparse.rst:741
"Note that slight difference in the usage text. Note the ``[-v | -q]``, which "
"tells us that we can either use ``-v`` or ``-q``, but not both at the same "
#: howto/argparse.rst:763
msgid "How to translate the argparse output"
#: howto/argparse.rst:765
"The output of the :mod:`argparse` module such as its help text and error "
"messages are all made translatable using the :mod:`gettext` module. This "
"allows applications to easily localize messages produced by :mod:`argparse`. "
"See also :ref:`i18n-howto`."
#: howto/argparse.rst:770
msgid "For instance, in this :mod:`argparse` output:"
#: howto/argparse.rst:788
"The strings ``usage:``, ``positional arguments:``, ``options:`` and ``show "
"this help message and exit`` are all translatable."
#: howto/argparse.rst:791
"In order to translate these strings, they must first be extracted into a ``."
"po`` file. For example, using `Babel <https://babel.pocoo.org/>`__, run this "
#: howto/argparse.rst:799
"This command will extract all translatable strings from the :mod:`argparse` "
"module and output them into a file named ``messages.po``. This command "
"assumes that your Python installation is in ``/usr/lib``."
#: howto/argparse.rst:803
"You can find out the location of the :mod:`argparse` module on your system "
"using this script::"
#: howto/argparse.rst:809
"Once the messages in the ``.po`` file are translated and the translations "
"are installed using :mod:`gettext`, :mod:`argparse` will be able to display "
"the translated messages."
#: howto/argparse.rst:813
"To translate your own strings in the :mod:`argparse` output, use :mod:"
"`gettext`."
#: howto/argparse.rst:816
msgid "Conclusion"
#: howto/argparse.rst:818
"The :mod:`argparse` module offers a lot more than shown here. Its docs are "
"quite detailed and thorough, and full of examples. Having gone through this "
"tutorial, you should easily digest them without feeling overwhelmed."
Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

FilesExpand file tree

argparse.po

Latest commit

History

argparse.po

File metadata and controls
