FazBrowse GitHub Viewer
|
Trending
|
URL:
|
Home
Tools:
[Download Repo ZIP]
[View Raw Code]
[Original HTTPS Page]
python-docs-pt-br/reference/lexical_analysis.po at 3.10 · python-doc-ja/python-docs-pt-br · GitHub
python-doc-ja
python-docs-pt-br
Repository navigation
Code
Pull requests
Actions
Projects
Security and quality
Insights
Expand file tree
Breadcrumbs
python-docs-pt-br
/
reference
/
lexical_analysis.po
Copy path
More file actions
More file actions
Latest commit
History
History
History
1158 lines (971 loc) · 42.5 KB
Breadcrumbs
python-docs-pt-br
/
reference
/
lexical_analysis.po
Copy path
File metadata and controls
1158 lines (971 loc) · 42.5 KB
Raw
Copy raw file
Download raw file
Open symbols panel
Edit and raw actions
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
#
SOME DESCRIPTIVE TITLE.
#
Copyright (C) 2001-2021, Python Software Foundation
#
This file is distributed under the same license as the Python package.
#
FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#
Translators:
#
Rafael Fontenelle <rffontenelle@gmail.com>, 2021
#
Welington Carlos <wcarlos3@gmail.com>, 2021
#
Claudio Rogerio Carvalho Filho <excriptbrasil@gmail.com>, 2021
#
(Douglas da Silva) <dementikovalev@yandex.ru>, 2021
#
Misael borges <misael@planosassessoria.com.br>, 2021
#
Vinicius Gubiani Ferreira <vini.g.fer@gmail.com>, 2021
#
Alexsandro Matias de Almeida <matiasalexsandro@gmail.com>, 2021
#
#,
fuzzy
msgid ""
msgstr ""
"
Project-Id-Version
:
Python 3.10\n
"
"
Report-Msgid-Bugs-To
:
\n
"
"
POT-Creation-Date
:
2021-06-29 12:56+0000\n
"
"
PO-Revision-Date
:
2021-06-28 01:49+0000\n
"
"
Last-Translator
:
Alexsandro Matias de Almeida <matiasalexsandro@gmail.com>,
"
"
2021\n
"
"
Language-Team
:
Portuguese (Brazil) (https://www.transifex.com/python-doc/
"
"
teams/5390/pt_BR/)\n
"
"
MIME-Version
:
1.0\n
"
"
Content-Type
:
text/plain; charset=UTF-8\n
"
"
Content-Transfer-Encoding
:
8bit\n
"
"
Language
:
pt_BR\n
"
"
Plural-Forms
:
nplurals=2; plural=(n > 1);\n
"
#:
../../reference/lexical_analysis.rst:6
msgid
"Lexical analysis"
msgstr
"Análise léxica"
#:
../../reference/lexical_analysis.rst:10
msgid
""
"A Python program is read by a *parser*. Input to the parser is a stream of "
"*tokens*, generated by the *lexical analyzer*. This chapter describes how "
"the lexical analyzer breaks a file into tokens."
msgstr
""
"Um programa Python é lido por um *analisador*. A entrada para o analisador é "
"um fluxo de *tokens*, gerado pelo *analisador lexical*. Este capítulo "
"descreve como o analisador lexical divide um arquivo em tokens."
#:
../../reference/lexical_analysis.rst:14
msgid
""
"Python reads program text as Unicode code points; the encoding of a source "
"file can be given by an encoding declaration and defaults to UTF-8, see :pep:"
"`3120` for details. If the source file cannot be decoded, a :exc:"
"`SyntaxError` is raised."
msgstr
""
"Python lê o texto do programa como pontos de código Unicode; a codificação "
"de um arquivo de origem pode ser fornecida por uma declaração de codificação "
"que por padrão é UTF-8, consulte :pep:`3120` para obter detalhes. Se o "
"arquivo de origem não puder ser decodificado, um :exc:`SyntaxError` será "
"gerado."
#:
../../reference/lexical_analysis.rst:23
msgid
"Line structure"
msgstr
"Estrutura das linhas"
#:
../../reference/lexical_analysis.rst:27
msgid
"A Python program is divided into a number of *logical lines*."
msgstr
"Um programa Python é dividido em uma série de *linhas lógicas*."
#:
../../reference/lexical_analysis.rst:33
msgid
"Logical lines"
msgstr
"Linhas lógicas"
#:
../../reference/lexical_analysis.rst:37
msgid
""
"The end of a logical line is represented by the token NEWLINE. Statements "
"cannot cross logical line boundaries except where NEWLINE is allowed by the "
"syntax (e.g., between statements in compound statements). A logical line is "
"constructed from one or more *physical lines* by following the explicit or "
"implicit *line joining* rules."
msgstr
""
"O fim de uma linha lógica é representado pelo token NEWLINE. As declarações "
"não podem cruzar os limites da linha lógica, exceto onde NEWLINE for "
"permitido pela sintaxe (por exemplo, entre as declarações de declarações "
"compostas). Uma linha lógica é construída a partir de uma ou mais *linhas "
"físicas* seguindo a linha explícita ou implícita que *junta as linhas* das "
"regras."
#:
../../reference/lexical_analysis.rst:47
msgid
"Physical lines"
msgstr
"Linhas físicas"
#:
../../reference/lexical_analysis.rst:49
msgid
""
"A physical line is a sequence of characters terminated by an end-of-line "
"sequence. In source files and strings, any of the standard platform line "
"termination sequences can be used - the Unix form using ASCII LF (linefeed), "
"the Windows form using the ASCII sequence CR LF (return followed by "
"linefeed), or the old Macintosh form using the ASCII CR (return) character. "
"All of these forms can be used equally, regardless of platform. The end of "
"input also serves as an implicit terminator for the final physical line."
msgstr
""
"Uma linha física é uma sequência de caracteres terminados por uma sequência "
"de quebra de linha. Nos arquivos de origem e cadeias de caracteres, qualquer "
"uma das sequências de terminação de linha de plataforma padrão pode ser "
"usada - o formato Unix usando ASCII LF (linefeed), o formato Windows usando "
"a sequência ASCII CR LF (return followed by linefeed) ou o antigo formato "
"Macintosh usando o caractere ASCII CR (return). Todos esses formatos podem "
"ser usados igualmente, independentemente da plataforma. O final da entrada "
"também serve como um finalizador implícito para a linha física final."
#:
../../reference/lexical_analysis.rst:57
msgid
""
"When embedding Python, source code strings should be passed to Python APIs "
"using the standard C conventions for newline characters (the ``
\\
n`` "
"character, representing ASCII LF, is the line terminator)."
msgstr
""
"Ao incorporar o Python, o código-fonte das Strings devem ser passadas para "
"APIs do Python usando as convenções C padrão para caracteres de nova linha "
"(o caractere ``
\\
n``, representando ASCII LF, será o terminador de linha)."
#:
../../reference/lexical_analysis.rst:65
msgid
"Comments"
msgstr
"Comentários"
#:
../../reference/lexical_analysis.rst:70
msgid
""
"A comment starts with a hash character (``#``) that is not part of a string "
"literal, and ends at the end of the physical line. A comment signifies the "
"end of the logical line unless the implicit line joining rules are invoked. "
"Comments are ignored by the syntax."
msgstr
""
#:
../../reference/lexical_analysis.rst:79
msgid
"Encoding declarations"
msgstr
"Declarações de codificação"
#:
../../reference/lexical_analysis.rst:84
msgid
""
"If a comment in the first or second line of the Python script matches the "
"regular expression ``coding[=:]
\\
s*([-
\\
w.]+)``, this comment is processed "
"as an encoding declaration; the first group of this expression names the "
"encoding of the source code file. The encoding declaration must appear on a "
"line of its own. If it is the second line, the first line must also be a "
"comment-only line. The recommended forms of an encoding expression are ::"
msgstr
""
#:
../../reference/lexical_analysis.rst:93
msgid
"which is recognized also by GNU Emacs, and ::"
msgstr
"que é reconhecido também por GNU Emacs, e ::"
#:
../../reference/lexical_analysis.rst:97
msgid
"which is recognized by Bram Moolenaar's VIM."
msgstr
"que é reconhecido pelo VIM de Bram Moolenaar."
#:
../../reference/lexical_analysis.rst:99
msgid
""
"If no encoding declaration is found, the default encoding is UTF-8. In "
"addition, if the first bytes of the file are the UTF-8 byte-order mark "
"(``b'
\\
xef
\\
xbb
\\
xbf'``), the declared file encoding is UTF-8 (this is "
"supported, among others, by Microsoft's :program:`notepad`)."
msgstr
""
#:
../../reference/lexical_analysis.rst:104
msgid
""
"If an encoding is declared, the encoding name must be recognized by Python. "
"The encoding is used for all lexical analysis, including string literals, "
"comments and identifiers."
msgstr
""
#:
../../reference/lexical_analysis.rst:114
msgid
"Explicit line joining"
msgstr
"Junção de linha explícita"
#:
../../reference/lexical_analysis.rst:118
msgid
""
"Two or more physical lines may be joined into logical lines using backslash "
"characters (``
\\
``), as follows: when a physical line ends in a backslash "
"that is not part of a string literal or comment, it is joined with the "
"following forming a single logical line, deleting the backslash and the "
"following end-of-line character. For example::"
msgstr
""
#:
../../reference/lexical_analysis.rst:129
msgid
""
"A line ending in a backslash cannot carry a comment. A backslash does not "
"continue a comment. A backslash does not continue a token except for string "
"literals (i.e., tokens other than string literals cannot be split across "
"physical lines using a backslash). A backslash is illegal elsewhere on a "
"line outside a string literal."
msgstr
""
#:
../../reference/lexical_analysis.rst:139
msgid
"Implicit line joining"
msgstr
"Junção de linha implícita"
#:
../../reference/lexical_analysis.rst:141
msgid
""
"Expressions in parentheses, square brackets or curly braces can be split "
"over more than one physical line without using backslashes. For example::"
msgstr
""
#:
../../reference/lexical_analysis.rst:149
msgid
""
"Implicitly continued lines can carry comments. The indentation of the "
"continuation lines is not important. Blank continuation lines are allowed. "
"There is no NEWLINE token between implicit continuation lines. Implicitly "
"continued lines can also occur within triple-quoted strings (see below); in "
"that case they cannot carry comments."
msgstr
""
#:
../../reference/lexical_analysis.rst:159
msgid
"Blank lines"
msgstr
"Linhas em branco"
#:
../../reference/lexical_analysis.rst:163
msgid
""
"A logical line that contains only spaces, tabs, formfeeds and possibly a "
"comment, is ignored (i.e., no NEWLINE token is generated). During "
"interactive input of statements, handling of a blank line may differ "
"depending on the implementation of the read-eval-print loop. In the "
"standard interactive interpreter, an entirely blank logical line (i.e. one "
"containing not even whitespace or a comment) terminates a multi-line "
"statement."
msgstr
""
#:
../../reference/lexical_analysis.rst:174
msgid
"Indentation"
msgstr
"Indentação"
#:
../../reference/lexical_analysis.rst:178
msgid
""
"Leading whitespace (spaces and tabs) at the beginning of a logical line is "
"used to compute the indentation level of the line, which in turn is used to "
"determine the grouping of statements."
msgstr
""
#:
../../reference/lexical_analysis.rst:182
msgid
""
"Tabs are replaced (from left to right) by one to eight spaces such that the "
"total number of characters up to and including the replacement is a multiple "
"of eight (this is intended to be the same rule as used by Unix). The total "
"number of spaces preceding the first non-blank character then determines the "
"line's indentation. Indentation cannot be split over multiple physical "
"lines using backslashes; the whitespace up to the first backslash determines "
"the indentation."
msgstr
""
#:
../../reference/lexical_analysis.rst:190
msgid
""
"Indentation is rejected as inconsistent if a source file mixes tabs and "
"spaces in a way that makes the meaning dependent on the worth of a tab in "
"spaces; a :exc:`TabError` is raised in that case."
msgstr
""
#:
../../reference/lexical_analysis.rst:194
msgid
""
"**Cross-platform compatibility note:** because of the nature of text editors "
"on non-UNIX platforms, it is unwise to use a mixture of spaces and tabs for "
"the indentation in a single source file. It should also be noted that "
"different platforms may explicitly limit the maximum indentation level."
msgstr
""
#:
../../reference/lexical_analysis.rst:199
msgid
""
"A formfeed character may be present at the start of the line; it will be "
"ignored for the indentation calculations above. Formfeed characters "
"occurring elsewhere in the leading whitespace have an undefined effect (for "
"instance, they may reset the space count to zero)."
msgstr
""
#:
../../reference/lexical_analysis.rst:206
msgid
""
"The indentation levels of consecutive lines are used to generate INDENT and "
"DEDENT tokens, using a stack, as follows."
msgstr
""
#:
../../reference/lexical_analysis.rst:209
msgid
""
"Before the first line of the file is read, a single zero is pushed on the "
"stack; this will never be popped off again. The numbers pushed on the stack "
"will always be strictly increasing from bottom to top. At the beginning of "
"each logical line, the line's indentation level is compared to the top of "
"the stack. If it is equal, nothing happens. If it is larger, it is pushed on "
"the stack, and one INDENT token is generated. If it is smaller, it *must* "
"be one of the numbers occurring on the stack; all numbers on the stack that "
"are larger are popped off, and for each number popped off a DEDENT token is "
"generated. At the end of the file, a DEDENT token is generated for each "
"number remaining on the stack that is larger than zero."
msgstr
""
#:
../../reference/lexical_analysis.rst:220
msgid
""
"Here is an example of a correctly (though confusingly) indented piece of "
"Python code::"
msgstr
""
#:
../../reference/lexical_analysis.rst:235
msgid
"The following example shows various indentation errors::"
msgstr
""
#:
../../reference/lexical_analysis.rst:245
msgid
""
"(Actually, the first three errors are detected by the parser; only the last "
"error is found by the lexical analyzer --- the indentation of ``return r`` "
"does not match a level popped off the stack.)"
msgstr
""
#:
../../reference/lexical_analysis.rst:253
msgid
"Whitespace between tokens"
msgstr
"Espaços em branco entre tokens"
#:
../../reference/lexical_analysis.rst:255
msgid
""
"Except at the beginning of a logical line or in string literals, the "
"whitespace characters space, tab and formfeed can be used interchangeably to "
"separate tokens. Whitespace is needed between two tokens only if their "
"concatenation could otherwise be interpreted as a different token (e.g., ab "
"is one token, but a b is two tokens)."
msgstr
""
#:
../../reference/lexical_analysis.rst:265
msgid
"Other tokens"
msgstr
"Outros tokens"
#:
../../reference/lexical_analysis.rst:267
msgid
""
"Besides NEWLINE, INDENT and DEDENT, the following categories of tokens "
"exist: *identifiers*, *keywords*, *literals*, *operators*, and *delimiters*. "
"Whitespace characters (other than line terminators, discussed earlier) are "
"not tokens, but serve to delimit tokens. Where ambiguity exists, a token "
"comprises the longest possible string that forms a legal token, when read "
"from left to right."
msgstr
""
#:
../../reference/lexical_analysis.rst:277
msgid
"Identifiers and keywords"
msgstr
"Identificadores e palavras-chave"
#:
../../reference/lexical_analysis.rst:281
msgid
""
"Identifiers (also referred to as *names*) are described by the following "
"lexical definitions."
msgstr
""
#:
../../reference/lexical_analysis.rst:284
msgid
""
"The syntax of identifiers in Python is based on the Unicode standard annex "
"UAX-31, with elaboration and changes as defined below; see also :pep:`3131` "
"for further details."
msgstr
""
#:
../../reference/lexical_analysis.rst:288
msgid
""
"Within the ASCII range (U+0001..U+007F), the valid characters for "
"identifiers are the same as in Python 2.x: the uppercase and lowercase "
"letters ``A`` through ``Z``, the underscore ``_`` and, except for the first "
"character, the digits ``0`` through ``9``."
msgstr
""
#:
../../reference/lexical_analysis.rst:293
msgid
""
"Python 3.0 introduces additional characters from outside the ASCII range "
"(see :pep:`3131`). For these characters, the classification uses the "
"version of the Unicode Character Database as included in the :mod:"
"`unicodedata` module."
msgstr
""
#:
../../reference/lexical_analysis.rst:297
msgid
"Identifiers are unlimited in length. Case is significant."
msgstr
""
#:
../../reference/lexical_analysis.rst:306
msgid
"The Unicode category codes mentioned above stand for:"
msgstr
""
#:
../../reference/lexical_analysis.rst:308
msgid
"*Lu* - uppercase letters"
msgstr
"*Lu* - letras maiúsculas"
#:
../../reference/lexical_analysis.rst:309
msgid
"*Ll* - lowercase letters"
msgstr
"*Ll* - letras minúsculas"
#:
../../reference/lexical_analysis.rst:310
msgid
"*Lt* - titlecase letters"
msgstr
"*Lt* - letras em titlecase"
#:
../../reference/lexical_analysis.rst:311
msgid
"*Lm* - modifier letters"
msgstr
"*Lm* - letras modificadoras"
#:
../../reference/lexical_analysis.rst:312
msgid
"*Lo* - other letters"
msgstr
"*Lo* - outras letras"
#:
../../reference/lexical_analysis.rst:313
msgid
"*Nl* - letter numbers"
msgstr
"*Nl* - letras numéricas"
#:
../../reference/lexical_analysis.rst:314
msgid
"*Mn* - nonspacing marks"
msgstr
"*Mn* - marcas sem espaçamento"
#:
../../reference/lexical_analysis.rst:315
msgid
"*Mc* - spacing combining marks"
msgstr
"*Mc* - marcas de combinação de espaçamento"
#:
../../reference/lexical_analysis.rst:316
msgid
"*Nd* - decimal numbers"
msgstr
"*Nd* - números decimais"
#:
../../reference/lexical_analysis.rst:317
msgid
"*Pc* - connector punctuations"
msgstr
"*Pc* - pontuações de conectores"
#:
../../reference/lexical_analysis.rst:318
msgid
""
"*Other_ID_Start* - explicit list of characters in `PropList.txt <https://www."
"unicode.org/Public/13.0.0/ucd/PropList.txt>`_ to support backwards "
"compatibility"
msgstr
""
#:
../../reference/lexical_analysis.rst:321
msgid
"*Other_ID_Continue* - likewise"
msgstr
"*Other_ID_Continue* - igualmente"
#:
../../reference/lexical_analysis.rst:323
msgid
""
"All identifiers are converted into the normal form NFKC while parsing; "
"comparison of identifiers is based on NFKC."
msgstr
""
#:
../../reference/lexical_analysis.rst:326
msgid
""
"A non-normative HTML file listing all valid identifier characters for "
"Unicode 4.1 can be found at https://www.unicode.org/Public/13.0.0/ucd/"
"DerivedCoreProperties.txt"
msgstr
""
#:
../../reference/lexical_analysis.rst:334
msgid
"Keywords"
msgstr
"Palavras-chave"
#:
../../reference/lexical_analysis.rst:340
msgid
""
"The following identifiers are used as reserved words, or *keywords* of the "
"language, and cannot be used as ordinary identifiers. They must be spelled "
"exactly as written here:"
msgstr
""
#:
../../reference/lexical_analysis.rst:358
msgid
"Soft Keywords"
msgstr
""
#:
../../reference/lexical_analysis.rst:364
msgid
""
"Some identifiers are only reserved under specific contexts. These are known "
"as *soft keywords*. The identifiers ``match``, ``case`` and ``_`` can "
"syntactically act as keywords in contexts related to the pattern matching "
"statement, but this distinction is done at the parser level, not when "
"tokenizing."
msgstr
""
#:
../../reference/lexical_analysis.rst:370
msgid
""
"As soft keywords, their use with pattern matching is possible while still "
"preserving compatibility with existing code that uses ``match``, ``case`` "
"and ``_`` as identifier names."
msgstr
""
#:
../../reference/lexical_analysis.rst:381
msgid
"Reserved classes of identifiers"
msgstr
"Classes reservadas de identificadores"
#:
../../reference/lexical_analysis.rst:383
msgid
""
"Certain classes of identifiers (besides keywords) have special meanings. "
"These classes are identified by the patterns of leading and trailing "
"underscore characters:"
msgstr
""
"Certas classes de identificadores (além de keywords) possuem significados "
"especiais. Essas classes são identificadas pelos padrões de caracteres de "
"sublinhado principais e à direita:"
#:
../../reference/lexical_analysis.rst:397
msgid
"``_*``"
msgstr
"``_*``"
#:
../../reference/lexical_analysis.rst:388
msgid
""
"Not imported by ``from module import *``. The special identifier ``_`` is "
"used in the interactive interpreter to store the result of the last "
"evaluation; it is stored in the :mod:`builtins` module. When not in "
"interactive mode, ``_`` has no special meaning and is not defined. See "
"section :ref:`import`."
msgstr
""
#:
../../reference/lexical_analysis.rst:395
msgid
""
"The name ``_`` is often used in conjunction with internationalization; refer "
"to the documentation for the :mod:`gettext` module for more information on "
"this convention."
msgstr
""
#:
../../reference/lexical_analysis.rst:405
msgid
"``__*__``"
msgstr
"``__*__``"
#:
../../reference/lexical_analysis.rst:400
msgid
""
"System-defined names, informally known as
\"
dunder
\"
names. These names are "
"defined by the interpreter and its implementation (including the standard "
"library). Current system names are discussed in the :ref:`specialnames` "
"section and elsewhere. More will likely be defined in future versions of "
"Python. *Any* use of ``__*__`` names, in any context, that does not follow "
"explicitly documented use, is subject to breakage without warning."
msgstr
""
#:
../../reference/lexical_analysis.rst:412
msgid
"``__*``"
msgstr
"``__*``"
#:
../../reference/lexical_analysis.rst:408
msgid
""
"Class-private names. Names in this category, when used within the context "
"of a class definition, are re-written to use a mangled form to help avoid "
"name clashes between
\"
private
\"
attributes of base and derived classes. See "
"section :ref:`atom-identifiers`."
msgstr
""
#:
../../reference/lexical_analysis.rst:417
msgid
"Literals"
msgstr
"Literais"
#:
../../reference/lexical_analysis.rst:421
msgid
"Literals are notations for constant values of some built-in types."
msgstr
""
"Os literais são notações para valores constantes de alguns tipos embutidos."
#:
../../reference/lexical_analysis.rst:432
msgid
"String and Bytes literals"
msgstr
"Literais de string e bytes"
#:
../../reference/lexical_analysis.rst:434
msgid
"String literals are described by the following lexical definitions:"
msgstr
""
#:
../../reference/lexical_analysis.rst:459
msgid
""
"One syntactic restriction not indicated by these productions is that "
"whitespace is not allowed between the :token:`stringprefix` or :token:"
"`bytesprefix` and the rest of the literal. The source character set is "
"defined by the encoding declaration; it is UTF-8 if no encoding declaration "
"is given in the source file; see section :ref:`encodings`."
msgstr
""
#:
../../reference/lexical_analysis.rst:469
msgid
""
"In plain English: Both types of literals can be enclosed in matching single "
"quotes (``'``) or double quotes (``
\"
``). They can also be enclosed in "
"matching groups of three single or double quotes (these are generally "
"referred to as *triple-quoted strings*). The backslash (``
\\
``) character "
"is used to escape characters that otherwise have a special meaning, such as "
"newline, backslash itself, or the quote character."
msgstr
""
#:
../../reference/lexical_analysis.rst:480
msgid
""
"Bytes literals are always prefixed with ``'b'`` or ``'B'``; they produce an "
"instance of the :class:`bytes` type instead of the :class:`str` type. They "
"may only contain ASCII characters; bytes with a numeric value of 128 or "
"greater must be expressed with escapes."
msgstr
""
#:
../../reference/lexical_analysis.rst:489
msgid
""
"Both string and bytes literals may optionally be prefixed with a letter "
"``'r'`` or ``'R'``; such strings are called :dfn:`raw strings` and treat "
"backslashes as literal characters. As a result, in string literals, "
"``'
\\
U'`` and ``'
\\
u'`` escapes in raw strings are not treated specially. "
"Given that Python 2.x's raw unicode literals behave differently than Python "
"3.x's the ``'ur'`` syntax is not supported."
msgstr
""
#:
../../reference/lexical_analysis.rst:496
msgid
""
"The ``'rb'`` prefix of raw bytes literals has been added as a synonym of "
"``'br'``."
msgstr
""
#:
../../reference/lexical_analysis.rst:500
msgid
""
"Support for the unicode legacy literal (``u'value'``) was reintroduced to "
"simplify the maintenance of dual Python 2.x and 3.x codebases. See :pep:"
"`414` for more information."
msgstr
""
#:
../../reference/lexical_analysis.rst:509
msgid
""
"A string literal with ``'f'`` or ``'F'`` in its prefix is a :dfn:`formatted "
"string literal`; see :ref:`f-strings`. The ``'f'`` may be combined with "
"``'r'``, but not with ``'b'`` or ``'u'``, therefore raw formatted strings "
"are possible, but formatted bytes literals are not."
msgstr
""
#:
../../reference/lexical_analysis.rst:514
msgid
""
"In triple-quoted literals, unescaped newlines and quotes are allowed (and "
"are retained), except that three unescaped quotes in a row terminate the "
"literal. (A
\"
quote
\"
is the character used to open the literal, i.e. "
"either ``'`` or ``
\"
``.)"
msgstr
""
#:
../../reference/lexical_analysis.rst:533
msgid
""
"Unless an ``'r'`` or ``'R'`` prefix is present, escape sequences in string "
"and bytes literals are interpreted according to rules similar to those used "
"by Standard C. The recognized escape sequences are:"
msgstr
""
#:
../../reference/lexical_analysis.rst:538
#:
../../reference/lexical_analysis.rst:571
msgid
"Escape Sequence"
msgstr
"Sequência de escape"
#:
../../reference/lexical_analysis.rst:538
#:
../../reference/lexical_analysis.rst:571
msgid
"Meaning"
msgstr
"Significado"
#:
../../reference/lexical_analysis.rst:538
#:
../../reference/lexical_analysis.rst:571
msgid
"Notes"
msgstr
"Notas"
#:
../../reference/lexical_analysis.rst:540
msgid
"``
\\
newline``"
msgstr
"``
\\
newline``"
#:
../../reference/lexical_analysis.rst:540
msgid
"Backslash and newline ignored"
msgstr
"A barra invertida e a nova linha foram ignoradas"
#:
../../reference/lexical_analysis.rst:542
msgid
"``
\\\\
``"
msgstr
"``
\\\\
``"
#:
../../reference/lexical_analysis.rst:542
msgid
"Backslash (``
\\
``)"
msgstr
"Backslash (``
\\
``)"
#:
../../reference/lexical_analysis.rst:544
msgid
"``
\\
'``"
msgstr
"``
\\
'``"
#:
../../reference/lexical_analysis.rst:544
msgid
"Single quote (``'``)"
msgstr
"Aspas Simples (``'``)"
#:
../../reference/lexical_analysis.rst:546
msgid
"``
\\\"
``"
msgstr
"``
\\\"
``"
#:
../../reference/lexical_analysis.rst:546
msgid
"Double quote (``
\"
``)"
msgstr
"Aspas Dupla (``
\"
``)"
#:
../../reference/lexical_analysis.rst:548
msgid
"``
\\
a``"
msgstr
"``
\\
a``"
#:
../../reference/lexical_analysis.rst:548
msgid
"ASCII Bell (BEL)"
msgstr
"ASCII Bell (BEL)"
#:
../../reference/lexical_analysis.rst:550
msgid
"``
\\
b``"
msgstr
"``
\\
b``"
#:
../../reference/lexical_analysis.rst:550
msgid
"ASCII Backspace (BS)"
msgstr
"ASCII Backspace (BS)"
#:
../../reference/lexical_analysis.rst:552
msgid
"``
\\
f``"
msgstr
"``
\\
f``"
#:
../../reference/lexical_analysis.rst:552
msgid
"ASCII Formfeed (FF)"
msgstr
"ASCII Formfeed (FF)"
#:
../../reference/lexical_analysis.rst:554
msgid
"``
\\
n``"
msgstr
"``
\\
n``"
#:
../../reference/lexical_analysis.rst:554
msgid
"ASCII Linefeed (LF)"
msgstr
"ASCII Linefeed (LF)"
#:
../../reference/lexical_analysis.rst:556
msgid
"``
\\
r``"
msgstr
"``
\\
r``"
#:
../../reference/lexical_analysis.rst:556
msgid
"ASCII Carriage Return (CR)"
msgstr
"ASCII Carriage Return (CR)"
#:
../../reference/lexical_analysis.rst:558
msgid
"``
\\
t``"
msgstr
"``
\\
t``"
#:
../../reference/lexical_analysis.rst:558
msgid
"ASCII Horizontal Tab (TAB)"
msgstr
"ASCII Horizontal Tab (TAB)"
#:
../../reference/lexical_analysis.rst:560
msgid
"``
\\
v``"
msgstr
"``
\\
v``"
#:
../../reference/lexical_analysis.rst:560
msgid
"ASCII Vertical Tab (VT)"
msgstr
"ASCII Vertical Tab (VT)"
#:
../../reference/lexical_analysis.rst:562
msgid
"``
\\
ooo``"
msgstr
"``
\\
ooo``"
#:
../../reference/lexical_analysis.rst:562
msgid
"Character with octal value *ooo*"
msgstr
"Caráter com valor octal *ooo*"
#:
../../reference/lexical_analysis.rst:562
msgid
"(1,3)"
msgstr
"(1,3)"
#:
../../reference/lexical_analysis.rst:565
msgid
"``
\\
xhh``"
msgstr
"``
\\
xhh``"
#:
../../reference/lexical_analysis.rst:565
msgid
"Character with hex value *hh*"
msgstr
"Caráter com valor hexadecimal *hh*"
#:
../../reference/lexical_analysis.rst:565
msgid
"(2,3)"
msgstr
"(2,3)"
#:
../../reference/lexical_analysis.rst:568
msgid
"Escape sequences only recognized in string literals are:"
msgstr
""
"As sequências de escape apenas reconhecidas em literais de Strings são:"
#:
../../reference/lexical_analysis.rst:573
msgid
"``
\\
N{name}``"
msgstr
"``
\\
N{name}``"
#:
../../reference/lexical_analysis.rst:573
msgid
"Character named *name* in the Unicode database"
msgstr
"Caractere chamado *name* no banco de dados Unicode"
#:
../../reference/lexical_analysis.rst:573
msgid
"
\\
(4)"
msgstr
"
\\
(4)"
#:
../../reference/lexical_analysis.rst:576
msgid
"``
\\
uxxxx``"
msgstr
"``
\\
uxxxx``"
#:
../../reference/lexical_analysis.rst:576
msgid
"Character with 16-bit hex value *xxxx*"
msgstr
"Caractere com valor hexadecimal de 16 bits *xxxx*"
#:
../../reference/lexical_analysis.rst:576
msgid
"
\\
(5)"
msgstr
"
\\
(5)"
#:
../../reference/lexical_analysis.rst:579
msgid
"``
\\
Uxxxxxxxx``"
msgstr
"``
\\
Uxxxxxxxx``"
#:
../../reference/lexical_analysis.rst:579
msgid
"Character with 32-bit hex value *xxxxxxxx*"
msgstr
"Caractere com valor hexadecimal de 32 bits *xxxxxxxx*"
#:
../../reference/lexical_analysis.rst:579
msgid
"
\\
(6)"
msgstr
"
\\
(6)"
#:
../../reference/lexical_analysis.rst:583
msgid
"Notes:"
msgstr
"Notas:"
#:
../../reference/lexical_analysis.rst:586
msgid
"As in Standard C, up to three octal digits are accepted."
msgstr
"Como no padrão C, são aceitos até três dígitos octais."
#:
../../reference/lexical_analysis.rst:589
msgid
"Unlike in Standard C, exactly two hex digits are required."
msgstr
""
"Ao contrário do padrão C, são necessários exatamente dois dígitos "
"hexadecimais."
#:
../../reference/lexical_analysis.rst:592
msgid
""
"In a bytes literal, hexadecimal and octal escapes denote the byte with the "
"given value. In a string literal, these escapes denote a Unicode character "
"with the given value."
msgstr
""
#:
../../reference/lexical_analysis.rst:597
msgid
"Support for name aliases [#]_ has been added."
msgstr
"O suporte para apelidos de nome [#]_ foi adicionado."
#:
../../reference/lexical_analysis.rst:601
msgid
"Exactly four hex digits are required."
msgstr
"São necessários quatro dígitos hexadecimais."
#:
../../reference/lexical_analysis.rst:604
msgid
""
"Any Unicode character can be encoded this way. Exactly eight hex digits are "
"required."
msgstr
""
#:
../../reference/lexical_analysis.rst:610
msgid
""
"Unlike Standard C, all unrecognized escape sequences are left in the string "
"unchanged, i.e., *the backslash is left in the result*. (This behavior is "
"useful when debugging: if an escape sequence is mistyped, the resulting "
"output is more easily recognized as broken.) It is also important to note "
"that the escape sequences only recognized in string literals fall into the "
"category of unrecognized escapes for bytes literals."
msgstr
""
#:
../../reference/lexical_analysis.rst:617
msgid
""
"Unrecognized escape sequences produce a :exc:`DeprecationWarning`. In a "
"future Python version they will be a :exc:`SyntaxWarning` and eventually a :"
"exc:`SyntaxError`."
msgstr
""
#:
../../reference/lexical_analysis.rst:622
msgid
""
"Even in a raw literal, quotes can be escaped with a backslash, but the "
"backslash remains in the result; for example, ``r
\"\\\"\"
`` is a valid "
"string literal consisting of two characters: a backslash and a double quote; "
"``r
\"\\\"
`` is not a valid string literal (even a raw string cannot end in "
"an odd number of backslashes). Specifically, *a raw literal cannot end in a "
"single backslash* (since the backslash would escape the following quote "
"character). Note also that a single backslash followed by a newline is "
"interpreted as those two characters as part of the literal, *not* as a line "
"continuation."
msgstr
""
#:
../../reference/lexical_analysis.rst:635
msgid
"String literal concatenation"
msgstr
""
#:
../../reference/lexical_analysis.rst:637
msgid
""
"Multiple adjacent string or bytes literals (delimited by whitespace), "
"possibly using different quoting conventions, are allowed, and their meaning "
"is the same as their concatenation. Thus, ``
\"
hello
\"
'world'`` is "
"equivalent to ``
\"
helloworld
\"
``. This feature can be used to reduce the "
"number of backslashes needed, to split long strings conveniently across long "
"lines, or even to add comments to parts of strings, for example::"
msgstr
""
#:
../../reference/lexical_analysis.rst:648
msgid
""
"Note that this feature is defined at the syntactical level, but implemented "
"at compile time. The '+' operator must be used to concatenate string "
"expressions at run time. Also note that literal concatenation can use "
"different quoting styles for each component (even mixing raw strings and "
"triple quoted strings), and formatted string literals may be concatenated "
"with plain string literals."
msgstr
""
#:
../../reference/lexical_analysis.rst:669
msgid
"Formatted string literals"
msgstr
"Literais de string formatados"
#:
../../reference/lexical_analysis.rst:673
msgid
""
"A :dfn:`formatted string literal` or :dfn:`f-string` is a string literal "
"that is prefixed with ``'f'`` or ``'F'``. These strings may contain "
"replacement fields, which are expressions delimited by curly braces ``{}``. "
"While other string literals always have a constant value, formatted strings "
"are really expressions evaluated at run time."
msgstr
""
#:
../../reference/lexical_analysis.rst:679
msgid
""
"Escape sequences are decoded like in ordinary string literals (except when a "
"literal is also marked as a raw string). After decoding, the grammar for "
"the contents of the string is:"
msgstr
""
#:
../../reference/lexical_analysis.rst:693
msgid
""
"The parts of the string outside curly braces are treated literally, except "
"that any doubled curly braces ``'{{'`` or ``'}}'`` are replaced with the "
"corresponding single curly brace. A single opening curly bracket ``'{'`` "
"marks a replacement field, which starts with a Python expression. To display "
"both the expression text and its value after evaluation, (useful in "
"debugging), an equal sign ``'='`` may be added after the expression. A "
"conversion field, introduced by an exclamation point ``'!'`` may follow. A "
"format specifier may also be appended, introduced by a colon ``':'``. A "
"replacement field ends with a closing curly bracket ``'}'``."
msgstr
""
#:
../../reference/lexical_analysis.rst:703
msgid
""
"Expressions in formatted string literals are treated like regular Python "
"expressions surrounded by parentheses, with a few exceptions. An empty "
"expression is not allowed, and both :keyword:`lambda` and assignment "
"expressions ``:=`` must be surrounded by explicit parentheses. Replacement "
"expressions can contain line breaks (e.g. in triple-quoted strings), but "
"they cannot contain comments. Each expression is evaluated in the context "
"where the formatted string literal appears, in order from left to right."
msgstr
""
#:
../../reference/lexical_analysis.rst:712
msgid
""
"Prior to Python 3.7, an :keyword:`await` expression and comprehensions "
"containing an :keyword:`async for` clause were illegal in the expressions in "
"formatted string literals due to a problem with the implementation."
msgstr
""
#:
../../reference/lexical_analysis.rst:717
msgid
""
"When the equal sign ``'='`` is provided, the output will have the expression "
"text, the ``'='`` and the evaluated value. Spaces after the opening brace "
"``'{'``, within the expression and after the ``'='`` are all retained in the "
"output. By default, the ``'='`` causes the :func:`repr` of the expression to "
"be provided, unless there is a format specified. When a format is specified "
"it defaults to the :func:`str` of the expression unless a conversion ``'!"
"r'`` is declared."
msgstr
""
#:
../../reference/lexical_analysis.rst:725
msgid
"The equal sign ``'='``."
msgstr
""
#:
../../reference/lexical_analysis.rst:728
msgid
""
"If a conversion is specified, the result of evaluating the expression is "
"converted before formatting. Conversion ``'!s'`` calls :func:`str` on the "
"result, ``'!r'`` calls :func:`repr`, and ``'!a'`` calls :func:`ascii`."
msgstr
""
#:
../../reference/lexical_analysis.rst:732
msgid
""
"The result is then formatted using the :func:`format` protocol. The format "
"specifier is passed to the :meth:`__format__` method of the expression or "
"conversion result. An empty string is passed when the format specifier is "
"omitted. The formatted result is then included in the final value of the "
"whole string."
msgstr
""
#:
../../reference/lexical_analysis.rst:738
msgid
""
"Top-level format specifiers may include nested replacement fields. These "
"nested fields may include their own conversion fields and :ref:`format "
"specifiers <formatspec>`, but may not include more deeply-nested replacement "
"fields. The :ref:`format specifier mini-language <formatspec>` is the same "
"as that used by the :meth:`str.format` method."
msgstr
""
#:
../../reference/lexical_analysis.rst:744
msgid
""
"Formatted string literals may be concatenated, but replacement fields cannot "
"be split across literals."
msgstr
""
#:
../../reference/lexical_analysis.rst:747
msgid
"Some examples of formatted string literals::"
msgstr
"Alguns exemplos de literais formatados::"
#:
../../reference/lexical_analysis.rst:779
msgid
""
"A consequence of sharing the same syntax as regular string literals is that "
"characters in the replacement fields must not conflict with the quoting used "
"in the outer formatted string literal::"
msgstr
""
#:
../../reference/lexical_analysis.rst:786
msgid
""
"Backslashes are not allowed in format expressions and will raise an error::"
msgstr
""
"As barras invertidas não são permitidas nas expressões de formatação e "
"levantarão uma exceção::"
#:
../../reference/lexical_analysis.rst:791
msgid
""
"To include a value in which a backslash escape is required, create a "
"temporary variable."
msgstr
""
#:
../../reference/lexical_analysis.rst:798
msgid
""
"Formatted string literals cannot be used as docstrings, even if they do not "
"include expressions."
View remainder of file in raw view
Back
|
FazBrowse Home
|
New Git URL