|
| 1 | +# SOME DESCRIPTIVE TITLE. |
| 2 | +# Copyright (C) 2001-2025, Python Software Foundation |
| 3 | +# This file is distributed under the same license as the Python package. |
| 4 | +# FIRST AUTHOR <EMAIL@ADDRESS>, 2025. |
| 5 | +# |
| 6 | +#, fuzzy |
| 7 | +msgid "" |
| 8 | +msgstr "" |
| 9 | +"Project-Id-Version: Python 3.13\n" |
| 10 | +"Report-Msgid-Bugs-To: \n" |
| 11 | +"POT-Creation-Date: 2025-03-04 13:08+0200\n" |
| 12 | +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" |
| 13 | +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" |
| 14 | +"Language: ro\n" |
| 15 | +"Language-Team: ro <LL@li.org>\n" |
| 16 | +"Plural-Forms: nplurals=3; plural=(n==1 ? 0 : (n==0 || (n%100 > 0 && n%100" |
| 17 | +" < 20)) ? 1 : 2);\n" |
| 18 | +"MIME-Version: 1.0\n" |
| 19 | +"Content-Type: text/plain; charset=utf-8\n" |
| 20 | +"Content-Transfer-Encoding: 8bit\n" |
| 21 | +"Generated-By: Babel 2.17.0\n" |
| 22 | + |
| 23 | +#: ../../tutorial/interpreter.rst:5 |
| 24 | +msgid "Using the Python Interpreter" |
| 25 | +msgstr "" |
| 26 | + |
| 27 | +#: ../../tutorial/interpreter.rst:11 |
| 28 | +msgid "Invoking the Interpreter" |
| 29 | +msgstr "" |
| 30 | + |
| 31 | +#: ../../tutorial/interpreter.rst:13 |
| 32 | +msgid "" |
| 33 | +"The Python interpreter is usually installed as " |
| 34 | +"|usr_local_bin_python_x_dot_y_literal| on those machines where it is " |
| 35 | +"available; putting :file:`/usr/local/bin` in your Unix shell's search " |
| 36 | +"path makes it possible to start it by typing the command:" |
| 37 | +msgstr "" |
| 38 | + |
| 39 | +#: ../../tutorial/interpreter.rst:17 |
| 40 | +msgid "python3.13" |
| 41 | +msgstr "" |
| 42 | + |
| 43 | +#: ../../tutorial/interpreter.rst:21 |
| 44 | +msgid "" |
| 45 | +"to the shell. [#]_ Since the choice of the directory where the " |
| 46 | +"interpreter lives is an installation option, other places are possible; " |
| 47 | +"check with your local Python guru or system administrator. (E.g., " |
| 48 | +":file:`/usr/local/python` is a popular alternative location.)" |
| 49 | +msgstr "" |
| 50 | + |
| 51 | +#: ../../tutorial/interpreter.rst:26 |
| 52 | +msgid "" |
| 53 | +"On Windows machines where you have installed Python from the " |
| 54 | +":ref:`Microsoft Store <windows-store>`, the |python_x_dot_y_literal| " |
| 55 | +"command will be available. If you have the :ref:`py.exe launcher " |
| 56 | +"<launcher>` installed, you can use the :file:`py` command. See :ref" |
| 57 | +":`setting-envvars` for other ways to launch Python." |
| 58 | +msgstr "" |
| 59 | + |
| 60 | +#: ../../tutorial/interpreter.rst:31 |
| 61 | +msgid "" |
| 62 | +"Typing an end-of-file character (:kbd:`Control-D` on Unix, " |
| 63 | +":kbd:`Control-Z` on Windows) at the primary prompt causes the interpreter" |
| 64 | +" to exit with a zero exit status. If that doesn't work, you can exit the" |
| 65 | +" interpreter by typing the following command: ``quit()``." |
| 66 | +msgstr "" |
| 67 | + |
| 68 | +#: ../../tutorial/interpreter.rst:36 |
| 69 | +msgid "" |
| 70 | +"The interpreter's line-editing features include interactive editing, " |
| 71 | +"history substitution and code completion on systems that support the `GNU" |
| 72 | +" Readline <https://tiswww.case.edu/php/chet/readline/rltop.html>`_ " |
| 73 | +"library. Perhaps the quickest check to see whether command line editing " |
| 74 | +"is supported is typing :kbd:`Control-P` to the first Python prompt you " |
| 75 | +"get. If it beeps, you have command line editing; see Appendix :ref:`tut-" |
| 76 | +"interacting` for an introduction to the keys. If nothing appears to " |
| 77 | +"happen, or if ``^P`` is echoed, command line editing isn't available; " |
| 78 | +"you'll only be able to use backspace to remove characters from the " |
| 79 | +"current line." |
| 80 | +msgstr "" |
| 81 | + |
| 82 | +#: ../../tutorial/interpreter.rst:46 |
| 83 | +msgid "" |
| 84 | +"The interpreter operates somewhat like the Unix shell: when called with " |
| 85 | +"standard input connected to a tty device, it reads and executes commands " |
| 86 | +"interactively; when called with a file name argument or with a file as " |
| 87 | +"standard input, it reads and executes a *script* from that file." |
| 88 | +msgstr "" |
| 89 | + |
| 90 | +#: ../../tutorial/interpreter.rst:51 |
| 91 | +msgid "" |
| 92 | +"A second way of starting the interpreter is ``python -c command [arg] " |
| 93 | +"...``, which executes the statement(s) in *command*, analogous to the " |
| 94 | +"shell's :option:`-c` option. Since Python statements often contain " |
| 95 | +"spaces or other characters that are special to the shell, it is usually " |
| 96 | +"advised to quote *command* in its entirety." |
| 97 | +msgstr "" |
| 98 | + |
| 99 | +#: ../../tutorial/interpreter.rst:57 |
| 100 | +msgid "" |
| 101 | +"Some Python modules are also useful as scripts. These can be invoked " |
| 102 | +"using ``python -m module [arg] ...``, which executes the source file for " |
| 103 | +"*module* as if you had spelled out its full name on the command line." |
| 104 | +msgstr "" |
| 105 | + |
| 106 | +#: ../../tutorial/interpreter.rst:61 |
| 107 | +msgid "" |
| 108 | +"When a script file is used, it is sometimes useful to be able to run the " |
| 109 | +"script and enter interactive mode afterwards. This can be done by " |
| 110 | +"passing :option:`-i` before the script." |
| 111 | +msgstr "" |
| 112 | + |
| 113 | +#: ../../tutorial/interpreter.rst:65 |
| 114 | +msgid "All command line options are described in :ref:`using-on-general`." |
| 115 | +msgstr "" |
| 116 | + |
| 117 | +#: ../../tutorial/interpreter.rst:71 |
| 118 | +msgid "Argument Passing" |
| 119 | +msgstr "" |
| 120 | + |
| 121 | +#: ../../tutorial/interpreter.rst:73 |
| 122 | +msgid "" |
| 123 | +"When known to the interpreter, the script name and additional arguments " |
| 124 | +"thereafter are turned into a list of strings and assigned to the ``argv``" |
| 125 | +" variable in the ``sys`` module. You can access this list by executing " |
| 126 | +"``import sys``. The length of the list is at least one; when no script " |
| 127 | +"and no arguments are given, ``sys.argv[0]`` is an empty string. When the" |
| 128 | +" script name is given as ``'-'`` (meaning standard input), " |
| 129 | +"``sys.argv[0]`` is set to ``'-'``. When :option:`-c` *command* is used, " |
| 130 | +"``sys.argv[0]`` is set to ``'-c'``. When :option:`-m` *module* is used, " |
| 131 | +"``sys.argv[0]`` is set to the full name of the located module. Options " |
| 132 | +"found after :option:`-c` *command* or :option:`-m` *module* are not " |
| 133 | +"consumed by the Python interpreter's option processing but left in " |
| 134 | +"``sys.argv`` for the command or module to handle." |
| 135 | +msgstr "" |
| 136 | + |
| 137 | +#: ../../tutorial/interpreter.rst:89 |
| 138 | +msgid "Interactive Mode" |
| 139 | +msgstr "" |
| 140 | + |
| 141 | +#: ../../tutorial/interpreter.rst:91 |
| 142 | +msgid "" |
| 143 | +"When commands are read from a tty, the interpreter is said to be in " |
| 144 | +"*interactive mode*. In this mode it prompts for the next command with " |
| 145 | +"the *primary prompt*, usually three greater-than signs (``>>>``); for " |
| 146 | +"continuation lines it prompts with the *secondary prompt*, by default " |
| 147 | +"three dots (``...``). The interpreter prints a welcome message stating " |
| 148 | +"its version number and a copyright notice before printing the first " |
| 149 | +"prompt:" |
| 150 | +msgstr "" |
| 151 | + |
| 152 | +#: ../../tutorial/interpreter.rst:98 |
| 153 | +msgid "" |
| 154 | +"$ python3.13\n" |
| 155 | +"Python 3.13 (default, April 4 2023, 09:25:04)\n" |
| 156 | +"[GCC 10.2.0] on linux\n" |
| 157 | +"Type \"help\", \"copyright\", \"credits\" or \"license\" for more " |
| 158 | +"information.\n" |
| 159 | +">>>" |
| 160 | +msgstr "" |
| 161 | + |
| 162 | +#: ../../tutorial/interpreter.rst:108 |
| 163 | +msgid "" |
| 164 | +"Continuation lines are needed when entering a multi-line construct. As an" |
| 165 | +" example, take a look at this :keyword:`if` statement::" |
| 166 | +msgstr "" |
| 167 | + |
| 168 | +#: ../../tutorial/interpreter.rst:111 |
| 169 | +msgid "" |
| 170 | +">>> the_world_is_flat = True\n" |
| 171 | +">>> if the_world_is_flat:\n" |
| 172 | +"... print(\"Be careful not to fall off!\")\n" |
| 173 | +"...\n" |
| 174 | +"Be careful not to fall off!" |
| 175 | +msgstr "" |
| 176 | + |
| 177 | +#: ../../tutorial/interpreter.rst:118 |
| 178 | +msgid "For more on interactive mode, see :ref:`tut-interac`." |
| 179 | +msgstr "" |
| 180 | + |
| 181 | +#: ../../tutorial/interpreter.rst:124 |
| 182 | +msgid "The Interpreter and Its Environment" |
| 183 | +msgstr "" |
| 184 | + |
| 185 | +#: ../../tutorial/interpreter.rst:130 |
| 186 | +msgid "Source Code Encoding" |
| 187 | +msgstr "" |
| 188 | + |
| 189 | +#: ../../tutorial/interpreter.rst:132 |
| 190 | +msgid "" |
| 191 | +"By default, Python source files are treated as encoded in UTF-8. In that" |
| 192 | +" encoding, characters of most languages in the world can be used " |
| 193 | +"simultaneously in string literals, identifiers and comments --- although " |
| 194 | +"the standard library only uses ASCII characters for identifiers, a " |
| 195 | +"convention that any portable code should follow. To display all these " |
| 196 | +"characters properly, your editor must recognize that the file is UTF-8, " |
| 197 | +"and it must use a font that supports all the characters in the file." |
| 198 | +msgstr "" |
| 199 | + |
| 200 | +#: ../../tutorial/interpreter.rst:140 |
| 201 | +msgid "" |
| 202 | +"To declare an encoding other than the default one, a special comment line" |
| 203 | +" should be added as the *first* line of the file. The syntax is as " |
| 204 | +"follows::" |
| 205 | +msgstr "" |
| 206 | + |
| 207 | +#: ../../tutorial/interpreter.rst:143 |
| 208 | +msgid "# -*- coding: encoding -*-" |
| 209 | +msgstr "" |
| 210 | + |
| 211 | +#: ../../tutorial/interpreter.rst:145 |
| 212 | +msgid "where *encoding* is one of the valid :mod:`codecs` supported by Python." |
| 213 | +msgstr "" |
| 214 | + |
| 215 | +#: ../../tutorial/interpreter.rst:147 |
| 216 | +msgid "" |
| 217 | +"For example, to declare that Windows-1252 encoding is to be used, the " |
| 218 | +"first line of your source code file should be::" |
| 219 | +msgstr "" |
| 220 | + |
| 221 | +#: ../../tutorial/interpreter.rst:150 |
| 222 | +msgid "# -*- coding: cp1252 -*-" |
| 223 | +msgstr "" |
| 224 | + |
| 225 | +#: ../../tutorial/interpreter.rst:152 |
| 226 | +msgid "" |
| 227 | +"One exception to the *first line* rule is when the source code starts " |
| 228 | +"with a :ref:`UNIX \"shebang\" line <tut-scripts>`. In this case, the " |
| 229 | +"encoding declaration should be added as the second line of the file. For" |
| 230 | +" example::" |
| 231 | +msgstr "" |
| 232 | + |
| 233 | +#: ../../tutorial/interpreter.rst:156 |
| 234 | +msgid "" |
| 235 | +"#!/usr/bin/env python3\n" |
| 236 | +"# -*- coding: cp1252 -*-" |
| 237 | +msgstr "" |
| 238 | + |
| 239 | +#: ../../tutorial/interpreter.rst:160 |
| 240 | +msgid "Footnotes" |
| 241 | +msgstr "" |
| 242 | + |
| 243 | +#: ../../tutorial/interpreter.rst:161 |
| 244 | +msgid "" |
| 245 | +"On Unix, the Python 3.x interpreter is by default not installed with the " |
| 246 | +"executable named ``python``, so that it does not conflict with a " |
| 247 | +"simultaneously installed Python 2.x executable." |
| 248 | +msgstr "" |
| 249 | + |
0 commit comments