{{ message }}
-
Notifications
You must be signed in to change notification settings - Fork 12
Expand file tree
/
Copy patherrors.po
More file actions
1038 lines (942 loc) · 36.2 KB
/
Copy patherrors.po
File metadata and controls
1038 lines (942 loc) · 36.2 KB
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 Python Software Foundation
# This file is distributed under the same license as the Python package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Ariyan Bolandi, 2025
# khosro azimi, 2025
# Alireza Shabani (Revisto) <theRevisto@gmail.com>, 2025
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Python 3.14\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-07-25 12:59+0330\n"
"PO-Revision-Date: 2021-06-28 01:50+0000\n"
"Last-Translator: Alireza Shabani (Revisto) <theRevisto@gmail.com>, 2025\n"
"Language-Team: Persian (https://app.transifex.com/python-doc/teams/5390/"
"fa/)\n"
"Language: fa\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../tutorial/errors.rst:5
msgid "Errors and Exceptions"
msgstr "خطاها و استثناها"
#: ../../tutorial/errors.rst:7
msgid ""
"Until now error messages haven't been more than mentioned, but if you have "
"tried out the examples you have probably seen some. There are (at least) "
"two distinguishable kinds of errors: *syntax errors* and *exceptions*."
msgstr ""
"تا اینجا پیامهای خطا فقط به صورت کوتاه ذکر شدهاند، اما اگر مثالها را امتحان "
"کرده باشید احتمالاً برخی از آنها را دیدهاید. حداقل دو نوع متمایز از خطا وجود "
"دارد: *خطاهای دستوری* «syntax errors» و *استثناها* «exceptions»."
#: ../../tutorial/errors.rst:15
msgid "Syntax Errors"
msgstr "خطاهای دستوری"
#: ../../tutorial/errors.rst:17
msgid ""
"Syntax errors, also known as parsing errors, are perhaps the most common "
"kind of complaint you get while you are still learning Python::"
msgstr ""
"خطاهای دستوری، که بهعنوان خطاهای تجزیهگر «parsing errors» نیز شناخته میشوند، "
"شاید رایجترین نوع خطاهایی باشند که هنگام یادگیری پایتون با آنها مواجه "
"میشوید::"
#: ../../tutorial/errors.rst:20
msgid ""
">>> while True print('Hello world')\n"
" File \"<stdin>\", line 1\n"
" while True print('Hello world')\n"
" ^^^^^\n"
"SyntaxError: invalid syntax"
msgstr ""
">>> while True print('Hello world')\n"
" File \"<stdin>\", line 1\n"
" while True print('Hello world')\n"
" ^^^^^\n"
"SyntaxError: invalid syntax"
#: ../../tutorial/errors.rst:26
msgid ""
"The parser repeats the offending line and displays little arrows pointing at "
"the place where the error was detected. Note that this is not always the "
"place that needs to be fixed. In the example, the error is detected at the "
"function :func:`print`, since a colon (``':'``) is missing just before it."
msgstr ""
"تجزیهگر «parser» خط مشکلدار را تکرار میکند و فلشهای کوچکی را نشان میدهد که "
"به جایی اشاره دارند که خطا در آن شناسایی شده است.\n"
"توجه داشته باشید که این همیشه همان جایی نیست که باید اصلاح شود.\n"
"در این مثال، خطا در تابع :func:`print` شناسایی شده است، زیرا دو نقطه "
"(``':'``) درست قبل از آن وجود ندارد."
#: ../../tutorial/errors.rst:31
msgid ""
"The file name (``<stdin>`` in our example) and line number are printed so "
"you know where to look in case the input came from a file."
msgstr ""
"نام فایل (در مثال ما ``<stdin>``) و شماره خط چاپ می شوند تا اگر ورودی از یک "
"فایل آمده باشد، بدانید باید کجا را بررسی کنید."
#: ../../tutorial/errors.rst:38
msgid "Exceptions"
msgstr "استثناء ها"
#: ../../tutorial/errors.rst:40
msgid ""
"Even if a statement or expression is syntactically correct, it may cause an "
"error when an attempt is made to execute it. Errors detected during "
"execution are called *exceptions* and are not unconditionally fatal: you "
"will soon learn how to handle them in Python programs. Most exceptions are "
"not handled by programs, however, and result in error messages as shown "
"here::"
msgstr ""
"حتی اگر یک دستور یا عبارت از نظر دستوری «syntactically» درست باشد، ممکن است "
"هنگام اجرای آن خطایی رخ دهد. خطاهایی که هنگام اجرا شناسایی میشوند «استثنا» "
"«*exceptions*» نام دارند و الزاماً باعث توقف برنامه نمیشوند؛ بهزودی خواهید "
"آموخت چگونه آنها را در برنامههای پایتون مدیریت کنید. با این حال، بیشتر "
"استثناها در برنامهها مدیریت نمیشوند و به پیامهای خطا ختم میشوند، مانند چیزی "
"که در اینجا نمایش داده شده است::"
#: ../../tutorial/errors.rst:46
msgid ""
">>> 10 * (1/0)\n"
"Traceback (most recent call last):\n"
" File \"<stdin>\", line 1, in <module>\n"
" 10 * (1/0)\n"
" ~^~\n"
"ZeroDivisionError: division by zero\n"
">>> 4 + spam*3\n"
"Traceback (most recent call last):\n"
" File \"<stdin>\", line 1, in <module>\n"
" 4 + spam*3\n"
" ^^^^\n"
"NameError: name 'spam' is not defined\n"
">>> '2' + 2\n"
"Traceback (most recent call last):\n"
" File \"<stdin>\", line 1, in <module>\n"
" '2' + 2\n"
" ~~~~^~~\n"
"TypeError: can only concatenate str (not \"int\") to str"
msgstr ""
">>> 10 * (1/0)\n"
"Traceback (most recent call last):\n"
" File \"<stdin>\", line 1, in <module>\n"
" 10 * (1/0)\n"
" ~^~\n"
"ZeroDivisionError: division by zero\n"
">>> 4 + spam*3\n"
"Traceback (most recent call last):\n"
" File \"<stdin>\", line 1, in <module>\n"
" 4 + spam*3\n"
" ^^^^\n"
"NameError: name 'spam' is not defined\n"
">>> '2' + 2\n"
"Traceback (most recent call last):\n"
" File \"<stdin>\", line 1, in <module>\n"
" '2' + 2\n"
" ~~~~^~~\n"
"TypeError: can only concatenate str (not \"int\") to str"
#: ../../tutorial/errors.rst:65
msgid ""
"The last line of the error message indicates what happened. Exceptions come "
"in different types, and the type is printed as part of the message: the "
"types in the example are :exc:`ZeroDivisionError`, :exc:`NameError` "
"and :exc:`TypeError`. The string printed as the exception type is the name "
"of the built-in exception that occurred. This is true for all built-in "
"exceptions, but need not be true for user-defined exceptions (although it is "
"a useful convention). Standard exception names are built-in identifiers (not "
"reserved keywords)."
msgstr ""
"آخرین خط از پیام خطا نشان می دهد که چه اتفاقی افتاده است. استثناها دارای "
"انواع مختلفی هستند و نوع آنها به عنوان بخشی از پیام چاپ می شود: انواع موجود "
"در مثال عبارتند از :exc:`ZeroDivisionError`، :exc:`NameError` "
"و :exc:`TypeError`. رشته ای که به عنوان نوع استثنا چاپ می شود، نام استثنای "
"داخلی است که رخ داده است. این موضوع برای تمام استثناهای داخلی صدق می کند، "
"اما برای استثناهای تعریف شده توسط کاربر لزوماً صحیح نیست (گرچه این یک قاعدهٔ "
"مفید محسوب میشود). نام های استثنای استاندارد شناسه های داخلی هستند (نه کلمات "
"کلیدی رزرو شده)."
#: ../../tutorial/errors.rst:73
msgid ""
"The rest of the line provides detail based on the type of exception and what "
"caused it."
msgstr ""
"بخش باقیماندهٔ خط، جزئیاتی را بسته به نوع استثنا «exception» و علت وقوع آن "
"ارائه میدهد."
#: ../../tutorial/errors.rst:76
msgid ""
"The preceding part of the error message shows the context where the "
"exception occurred, in the form of a stack traceback. In general it contains "
"a stack traceback listing source lines; however, it will not display lines "
"read from standard input."
msgstr ""
"بخش قبلی پیام خطا، زمینهای را نشان میدهد که در آن استثنا رخ داده است، بهصورت "
"یک ردگیری پشته «stack traceback». بهطور کلی، این بخش شامل ردگیری پشتهای است "
"که خطوطی از کد منبع را فهرست میکند؛ با این حال، خطوطی که از ورودی استاندارد "
"«standard input» خوانده شدهاند در آن نمایش داده نمیشوند."
#: ../../tutorial/errors.rst:81
msgid ""
":ref:`bltin-exceptions` lists the built-in exceptions and their meanings."
msgstr ""
":ref:`bltin-exceptions` لیستی از استثناهای داخلی و معانی آن ها را ارائه می "
"دهد."
#: ../../tutorial/errors.rst:87
msgid "Handling Exceptions"
msgstr "مدیریت استثناها"
#: ../../tutorial/errors.rst:89
msgid ""
"It is possible to write programs that handle selected exceptions. Look at "
"the following example, which asks the user for input until a valid integer "
"has been entered, but allows the user to interrupt the program "
"(using :kbd:`Control-C` or whatever the operating system supports); note "
"that a user-generated interruption is signalled by raising "
"the :exc:`KeyboardInterrupt` exception. ::"
msgstr ""
"امکان نوشتن برنامههایی وجود دارد که برخی از استثناها را مدیریت میکنند. به "
"مثال زیر نگاه کنید که از کاربر ورودی میخواهد تا زمانی که یک عدد صحیح معتبر "
"وارد شود، اما به کاربر اجازه میدهد برنامه را قطع کند (با فشردن :kbd:`Control-"
"C` یا هر روشی که سیستمعامل پشتیبانی میکند)؛ توجه داشته باشید که قطع برنامه "
"توسط کاربر با ایجاد استثنای :exc:`KeyboardInterrupt` مشخص میشود. ::"
#: ../../tutorial/errors.rst:95
msgid ""
">>> while True:\n"
"... try:\n"
"... x = int(input(\"Please enter a number: \"))\n"
"... break\n"
"... except ValueError:\n"
"... print(\"Oops! That was no valid number. Try again...\")\n"
"..."
msgstr ""
">>> while True:\n"
"... try:\n"
"... x = int(input(\"Please enter a number: \"))\n"
"... break\n"
"... except ValueError:\n"
"... print(\"Oops! That was no valid number. Try again...\")\n"
"..."
#: ../../tutorial/errors.rst:103
msgid "The :keyword:`try` statement works as follows."
msgstr "دستور :keyword:`try` به شکل زیر عمل میکند."
#: ../../tutorial/errors.rst:105
msgid ""
"First, the *try clause* (the statement(s) between the :keyword:`try` "
"and :keyword:`except` keywords) is executed."
msgstr ""
"ابتدا بخش *try clause* (دستوری که بین کلیدواژه های :keyword:`try` "
"و :keyword:`except` قرار دارد) اجرا می شود."
#: ../../tutorial/errors.rst:108
msgid ""
"If no exception occurs, the *except clause* is skipped and execution of "
"the :keyword:`try` statement is finished."
msgstr ""
"اگر هیچ استثنایی رخ ندهد، *بخش except* نادیده گرفته میشود و اجرای "
"دستور :keyword:`try` به پایان میرسد."
#: ../../tutorial/errors.rst:111
msgid ""
"If an exception occurs during execution of the :keyword:`try` clause, the "
"rest of the clause is skipped. Then, if its type matches the exception "
"named after the :keyword:`except` keyword, the *except clause* is executed, "
"and then execution continues after the try/except block."
msgstr ""
"اگر در طول اجرای بخش :keyword:`try` استثنایی رخ دهد، بقیه آن بخش نادیده "
"گرفته میشود. سپس، اگر نوع استثنا با استثنایی که بعد از "
"کلیدواژه :keyword:`except` آمده مطابقت داشته باشد، *بخش except* اجرا میشود و "
"پس از آن اجرای برنامه بعد از بلوک try/except ادامه مییابد."
#: ../../tutorial/errors.rst:116
msgid ""
"If an exception occurs which does not match the exception named in the "
"*except clause*, it is passed on to outer :keyword:`try` statements; if no "
"handler is found, it is an *unhandled exception* and execution stops with an "
"error message."
msgstr ""
#: ../../tutorial/errors.rst:120
msgid ""
"A :keyword:`try` statement may have more than one *except clause*, to "
"specify handlers for different exceptions. At most one handler will be "
"executed. Handlers only handle exceptions that occur in the corresponding "
"*try clause*, not in other handlers of the same :keyword:`!try` statement. "
"An *except clause* may name multiple exceptions, for example::"
msgstr ""
#: ../../tutorial/errors.rst:126
msgid ""
"... except RuntimeError, TypeError, NameError:\n"
"... pass"
msgstr ""
#: ../../tutorial/errors.rst:129
msgid ""
"A class in an :keyword:`except` clause matches exceptions which are "
"instances of the class itself or one of its derived classes (but not the "
"other way around --- an *except clause* listing a derived class does not "
"match instances of its base classes). For example, the following code will "
"print B, C, D in that order::"
msgstr ""
#: ../../tutorial/errors.rst:134
msgid ""
"class B(Exception):\n"
" pass\n"
"\n"
"class C(B):\n"
" pass\n"
"\n"
"class D(C):\n"
" pass\n"
"\n"
"for cls in [B, C, D]:\n"
" try:\n"
" raise cls()\n"
" except D:\n"
" print(\"D\")\n"
" except C:\n"
" print(\"C\")\n"
" except B:\n"
" print(\"B\")"
msgstr ""
#: ../../tutorial/errors.rst:153
msgid ""
"Note that if the *except clauses* were reversed (with ``except B`` first), "
"it would have printed B, B, B --- the first matching *except clause* is "
"triggered."
msgstr ""
#: ../../tutorial/errors.rst:156
msgid ""
"When an exception occurs, it may have associated values, also known as the "
"exception's *arguments*. The presence and types of the arguments depend on "
"the exception type."
msgstr ""
#: ../../tutorial/errors.rst:160
msgid ""
"The *except clause* may specify a variable after the exception name. The "
"variable is bound to the exception instance which typically has an ``args`` "
"attribute that stores the arguments. For convenience, builtin exception "
"types define :meth:`~object.__str__` to print all the arguments without "
"explicitly accessing ``.args``. ::"
msgstr ""
#: ../../tutorial/errors.rst:166
msgid ""
">>> try:\n"
"... raise Exception('spam', 'eggs')\n"
"... except Exception as inst:\n"
"... print(type(inst)) # the exception type\n"
"... print(inst.args) # arguments stored in .args\n"
"... print(inst) # __str__ allows args to be printed directly,\n"
"... # but may be overridden in exception "
"subclasses\n"
"... x, y = inst.args # unpack args\n"
"... print('x =', x)\n"
"... print('y =', y)\n"
"...\n"
"<class 'Exception'>\n"
"('spam', 'eggs')\n"
"('spam', 'eggs')\n"
"x = spam\n"
"y = eggs"
msgstr ""
#: ../../tutorial/errors.rst:183
msgid ""
"The exception's :meth:`~object.__str__` output is printed as the last part "
"('detail') of the message for unhandled exceptions."
msgstr ""
#: ../../tutorial/errors.rst:186
msgid ""
":exc:`BaseException` is the common base class of all exceptions. One of its "
"subclasses, :exc:`Exception`, is the base class of all the non-fatal "
"exceptions. Exceptions which are not subclasses of :exc:`Exception` are not "
"typically handled, because they are used to indicate that the program should "
"terminate. They include :exc:`SystemExit` which is raised "
"by :meth:`sys.exit` and :exc:`KeyboardInterrupt` which is raised when a user "
"wishes to interrupt the program."
msgstr ""
#: ../../tutorial/errors.rst:194
msgid ""
":exc:`Exception` can be used as a wildcard that catches (almost) everything. "
"However, it is good practice to be as specific as possible with the types of "
"exceptions that we intend to handle, and to allow any unexpected exceptions "
"to propagate on."
msgstr ""
#: ../../tutorial/errors.rst:199
msgid ""
"The most common pattern for handling :exc:`Exception` is to print or log the "
"exception and then re-raise it (allowing a caller to handle the exception as "
"well)::"
msgstr ""
#: ../../tutorial/errors.rst:203
msgid ""
"import sys\n"
"\n"
"try:\n"
" f = open('myfile.txt')\n"
" s = f.readline()\n"
" i = int(s.strip())\n"
"except OSError as err:\n"
" print(\"OS error:\", err)\n"
"except ValueError:\n"
" print(\"Could not convert data to an integer.\")\n"
"except Exception as err:\n"
" print(f\"Unexpected {err=}, {type(err)=}\")\n"
" raise"
msgstr ""
#: ../../tutorial/errors.rst:217
msgid ""
"The :keyword:`try` ... :keyword:`except` statement has an optional *else "
"clause*, which, when present, must follow all *except clauses*. It is "
"useful for code that must be executed if the *try clause* does not raise an "
"exception. For example::"
msgstr ""
#: ../../tutorial/errors.rst:222
msgid ""
"for arg in sys.argv[1:]:\n"
" try:\n"
" f = open(arg, 'r')\n"
" except OSError:\n"
" print('cannot open', arg)\n"
" else:\n"
" print(arg, 'has', len(f.readlines()), 'lines')\n"
" f.close()"
msgstr ""
#: ../../tutorial/errors.rst:231
msgid ""
"The use of the :keyword:`!else` clause is better than adding additional code "
"to the :keyword:`try` clause because it avoids accidentally catching an "
"exception that wasn't raised by the code being protected by the :keyword:`!"
"try` ... :keyword:`!except` statement."
msgstr ""
#: ../../tutorial/errors.rst:236
msgid ""
"Exception handlers do not handle only exceptions that occur immediately in "
"the *try clause*, but also those that occur inside functions that are called "
"(even indirectly) in the *try clause*. For example::"
msgstr ""
#: ../../tutorial/errors.rst:240
msgid ""
">>> def this_fails():\n"
"... x = 1/0\n"
"...\n"
">>> try:\n"
"... this_fails()\n"
"... except ZeroDivisionError as err:\n"
"... print('Handling run-time error:', err)\n"
"...\n"
"Handling run-time error: division by zero"
msgstr ""
#: ../../tutorial/errors.rst:254
msgid "Raising Exceptions"
msgstr ""
#: ../../tutorial/errors.rst:256
msgid ""
"The :keyword:`raise` statement allows the programmer to force a specified "
"exception to occur. For example::"
msgstr ""
#: ../../tutorial/errors.rst:259
msgid ""
">>> raise NameError('HiThere')\n"
"Traceback (most recent call last):\n"
" File \"<stdin>\", line 1, in <module>\n"
" raise NameError('HiThere')\n"
"NameError: HiThere"
msgstr ""
#: ../../tutorial/errors.rst:265
msgid ""
"The sole argument to :keyword:`raise` indicates the exception to be raised. "
"This must be either an exception instance or an exception class (a class "
"that derives from :class:`BaseException`, such as :exc:`Exception` or one of "
"its subclasses). If an exception class is passed, it will be implicitly "
"instantiated by calling its constructor with no arguments::"
msgstr ""
#: ../../tutorial/errors.rst:271
msgid "raise ValueError # shorthand for 'raise ValueError()'"
msgstr ""
#: ../../tutorial/errors.rst:273
msgid ""
"If you need to determine whether an exception was raised but don't intend to "
"handle it, a simpler form of the :keyword:`raise` statement allows you to re-"
"raise the exception::"
msgstr ""
#: ../../tutorial/errors.rst:277
msgid ""
">>> try:\n"
"... raise NameError('HiThere')\n"
"... except NameError:\n"
"... print('An exception flew by!')\n"
"... raise\n"
"...\n"
"An exception flew by!\n"
"Traceback (most recent call last):\n"
" File \"<stdin>\", line 2, in <module>\n"
" raise NameError('HiThere')\n"
"NameError: HiThere"
msgstr ""
#: ../../tutorial/errors.rst:293
msgid "Exception Chaining"
msgstr ""
#: ../../tutorial/errors.rst:295
msgid ""
"If an unhandled exception occurs inside an :keyword:`except` section, it "
"will have the exception being handled attached to it and included in the "
"error message::"
msgstr ""
#: ../../tutorial/errors.rst:299
msgid ""
">>> try:\n"
"... open(\"database.sqlite\")\n"
"... except OSError:\n"
"... raise RuntimeError(\"unable to handle error\")\n"
"...\n"
"Traceback (most recent call last):\n"
" File \"<stdin>\", line 2, in <module>\n"
" open(\"database.sqlite\")\n"
" ~~~~^^^^^^^^^^^^^^^^^^^\n"
"FileNotFoundError: [Errno 2] No such file or directory: 'database.sqlite'\n"
"\n"
"During handling of the above exception, another exception occurred:\n"
"\n"
"Traceback (most recent call last):\n"
" File \"<stdin>\", line 4, in <module>\n"
" raise RuntimeError(\"unable to handle error\")\n"
"RuntimeError: unable to handle error"
msgstr ""
#: ../../tutorial/errors.rst:317
msgid ""
"To indicate that an exception is a direct consequence of another, "
"the :keyword:`raise` statement allows an optional :keyword:`from<raise>` "
"clause::"
msgstr ""
#: ../../tutorial/errors.rst:320
msgid ""
"# exc must be exception instance or None.\n"
"raise RuntimeError from exc"
msgstr ""
#: ../../tutorial/errors.rst:323
msgid "This can be useful when you are transforming exceptions. For example::"
msgstr ""
#: ../../tutorial/errors.rst:325
msgid ""
">>> def func():\n"
"... raise ConnectionError\n"
"...\n"
">>> try:\n"
"... func()\n"
"... except ConnectionError as exc:\n"
"... raise RuntimeError('Failed to open database') from exc\n"
"...\n"
"Traceback (most recent call last):\n"
" File \"<stdin>\", line 2, in <module>\n"
" func()\n"
" ~~~~^^\n"
" File \"<stdin>\", line 2, in func\n"
"ConnectionError\n"
"\n"
"The above exception was the direct cause of the following exception:\n"
"\n"
"Traceback (most recent call last):\n"
" File \"<stdin>\", line 4, in <module>\n"
" raise RuntimeError('Failed to open database') from exc\n"
"RuntimeError: Failed to open database"
msgstr ""
#: ../../tutorial/errors.rst:347
msgid ""
"It also allows disabling automatic exception chaining using the ``from "
"None`` idiom::"
msgstr ""
#: ../../tutorial/errors.rst:350
msgid ""
">>> try:\n"
"... open('database.sqlite')\n"
"... except OSError:\n"
"... raise RuntimeError from None\n"
"...\n"
"Traceback (most recent call last):\n"
" File \"<stdin>\", line 4, in <module>\n"
" raise RuntimeError from None\n"
"RuntimeError"
msgstr ""
#: ../../tutorial/errors.rst:360
msgid ""
"For more information about chaining mechanics, see :ref:`bltin-exceptions`."
msgstr ""
#: ../../tutorial/errors.rst:366
msgid "User-defined Exceptions"
msgstr ""
#: ../../tutorial/errors.rst:368
msgid ""
"Programs may name their own exceptions by creating a new exception class "
"(see :ref:`tut-classes` for more about Python classes). Exceptions should "
"typically be derived from the :exc:`Exception` class, either directly or "
"indirectly."
msgstr ""
#: ../../tutorial/errors.rst:372
msgid ""
"Exception classes can be defined which do anything any other class can do, "
"but are usually kept simple, often only offering a number of attributes that "
"allow information about the error to be extracted by handlers for the "
"exception."
msgstr ""
#: ../../tutorial/errors.rst:376
msgid ""
"Most exceptions are defined with names that end in \"Error\", similar to the "
"naming of the standard exceptions."
msgstr ""
#: ../../tutorial/errors.rst:379
msgid ""
"Many standard modules define their own exceptions to report errors that may "
"occur in functions they define."
msgstr ""
#: ../../tutorial/errors.rst:386
msgid "Defining Clean-up Actions"
msgstr ""
#: ../../tutorial/errors.rst:388
msgid ""
"The :keyword:`try` statement has another optional clause which is intended "
"to define clean-up actions that must be executed under all circumstances. "
"For example::"
msgstr ""
#: ../../tutorial/errors.rst:392
msgid ""
">>> try:\n"
"... raise KeyboardInterrupt\n"
"... finally:\n"
"... print('Goodbye, world!')\n"
"...\n"
"Goodbye, world!\n"
"Traceback (most recent call last):\n"
" File \"<stdin>\", line 2, in <module>\n"
" raise KeyboardInterrupt\n"
"KeyboardInterrupt"
msgstr ""
#: ../../tutorial/errors.rst:403
msgid ""
"If a :keyword:`finally` clause is present, the :keyword:`!finally` clause "
"will execute as the last task before the :keyword:`try` statement completes. "
"The :keyword:`!finally` clause runs whether or not the :keyword:`!try` "
"statement produces an exception. The following points discuss more complex "
"cases when an exception occurs:"
msgstr ""
#: ../../tutorial/errors.rst:409
msgid ""
"If an exception occurs during execution of the :keyword:`!try` clause, the "
"exception may be handled by an :keyword:`except` clause. If the exception is "
"not handled by an :keyword:`!except` clause, the exception is re-raised "
"after the :keyword:`!finally` clause has been executed."
msgstr ""
#: ../../tutorial/errors.rst:415
msgid ""
"An exception could occur during execution of an :keyword:`!except` "
"or :keyword:`!else` clause. Again, the exception is re-raised after "
"the :keyword:`!finally` clause has been executed."
msgstr ""
#: ../../tutorial/errors.rst:419
msgid ""
"If the :keyword:`!finally` clause executes "
"a :keyword:`break`, :keyword:`continue` or :keyword:`return` statement, "
"exceptions are not re-raised. This can be confusing and is therefore "
"discouraged. From version 3.14 the compiler emits a :exc:`SyntaxWarning` for "
"it (see :pep:`765`)."
msgstr ""
#: ../../tutorial/errors.rst:425
msgid ""
"If the :keyword:`!try` statement reaches "
"a :keyword:`break`, :keyword:`continue` or :keyword:`return` statement, "
"the :keyword:`!finally` clause will execute just prior to the :keyword:`!"
"break`, :keyword:`!continue` or :keyword:`!return` statement's execution."
msgstr ""
#: ../../tutorial/errors.rst:431
msgid ""
"If a :keyword:`!finally` clause includes a :keyword:`!return` statement, the "
"returned value will be the one from the :keyword:`!finally` "
"clause's :keyword:`!return` statement, not the value from the :keyword:`!"
"try` clause's :keyword:`!return` statement. This can be confusing and is "
"therefore discouraged. From version 3.14 the compiler emits "
"a :exc:`SyntaxWarning` for it (see :pep:`765`)."
msgstr ""
#: ../../tutorial/errors.rst:439
msgid "For example::"
msgstr ""
#: ../../tutorial/errors.rst:441
msgid ""
">>> def bool_return():\n"
"... try:\n"
"... return True\n"
"... finally:\n"
"... return False\n"
"...\n"
">>> bool_return()\n"
"False"
msgstr ""
#: ../../tutorial/errors.rst:450
msgid "A more complicated example::"
msgstr ""
#: ../../tutorial/errors.rst:452
msgid ""
">>> def divide(x, y):\n"
"... try:\n"
"... result = x / y\n"
"... except ZeroDivisionError:\n"
"... print(\"division by zero!\")\n"
"... else:\n"
"... print(\"result is\", result)\n"
"... finally:\n"
"... print(\"executing finally clause\")\n"
"...\n"
">>> divide(2, 1)\n"
"result is 2.0\n"
"executing finally clause\n"
">>> divide(2, 0)\n"
"division by zero!\n"
"executing finally clause\n"
">>> divide(\"2\", \"1\")\n"
"executing finally clause\n"
"Traceback (most recent call last):\n"
" File \"<stdin>\", line 1, in <module>\n"
" divide(\"2\", \"1\")\n"
" ~~~~~~^^^^^^^^^^\n"
" File \"<stdin>\", line 3, in divide\n"
" result = x / y\n"
" ~~^~~\n"
"TypeError: unsupported operand type(s) for /: 'str' and 'str'"
msgstr ""
#: ../../tutorial/errors.rst:479
msgid ""
"As you can see, the :keyword:`finally` clause is executed in any event. "
"The :exc:`TypeError` raised by dividing two strings is not handled by "
"the :keyword:`except` clause and therefore re-raised after the :keyword:`!"
"finally` clause has been executed."
msgstr ""
#: ../../tutorial/errors.rst:484
msgid ""
"In real world applications, the :keyword:`finally` clause is useful for "
"releasing external resources (such as files or network connections), "
"regardless of whether the use of the resource was successful."
msgstr ""
#: ../../tutorial/errors.rst:492
msgid "Predefined Clean-up Actions"
msgstr ""
#: ../../tutorial/errors.rst:494
msgid ""
"Some objects define standard clean-up actions to be undertaken when the "
"object is no longer needed, regardless of whether or not the operation using "
"the object succeeded or failed. Look at the following example, which tries "
"to open a file and print its contents to the screen. ::"
msgstr ""
#: ../../tutorial/errors.rst:499
msgid ""
"for line in open(\"myfile.txt\"):\n"
" print(line, end=\"\")"
msgstr ""
#: ../../tutorial/errors.rst:502
msgid ""
"The problem with this code is that it leaves the file open for an "
"indeterminate amount of time after this part of the code has finished "
"executing. This is not an issue in simple scripts, but can be a problem for "
"larger applications. The :keyword:`with` statement allows objects like files "
"to be used in a way that ensures they are always cleaned up promptly and "
"correctly. ::"
msgstr ""
#: ../../tutorial/errors.rst:508
msgid ""
"with open(\"myfile.txt\") as f:\n"
" for line in f:\n"
" print(line, end=\"\")"
msgstr ""
#: ../../tutorial/errors.rst:512
msgid ""
"After the statement is executed, the file *f* is always closed, even if a "
"problem was encountered while processing the lines. Objects which, like "
"files, provide predefined clean-up actions will indicate this in their "
"documentation."
msgstr ""
#: ../../tutorial/errors.rst:520
msgid "Raising and Handling Multiple Unrelated Exceptions"
msgstr ""
#: ../../tutorial/errors.rst:522
msgid ""
"There are situations where it is necessary to report several exceptions that "
"have occurred. This is often the case in concurrency frameworks, when "
"several tasks may have failed in parallel, but there are also other use "
"cases where it is desirable to continue execution and collect multiple "
"errors rather than raise the first exception."
msgstr ""
#: ../../tutorial/errors.rst:528
msgid ""
"The builtin :exc:`ExceptionGroup` wraps a list of exception instances so "
"that they can be raised together. It is an exception itself, so it can be "
"caught like any other exception. ::"
msgstr ""
#: ../../tutorial/errors.rst:532
msgid ""
">>> def f():\n"
"... excs = [OSError('error 1'), SystemError('error 2')]\n"
"... raise ExceptionGroup('there were problems', excs)\n"
"...\n"
">>> f()\n"
" + Exception Group Traceback (most recent call last):\n"
" | File \"<stdin>\", line 1, in <module>\n"
" | f()\n"
" | ~^^\n"
" | File \"<stdin>\", line 3, in f\n"
" | raise ExceptionGroup('there were problems', excs)\n"
" | ExceptionGroup: there were problems (2 sub-exceptions)\n"
" +-+---------------- 1 ----------------\n"
" | OSError: error 1\n"
" +---------------- 2 ----------------\n"
" | SystemError: error 2\n"
" +------------------------------------\n"
">>> try:\n"
"... f()\n"
"... except Exception as e:\n"
"... print(f'caught {type(e)}: {e}')\n"
"...\n"
"caught <class 'ExceptionGroup'>: there were problems (2 sub-exceptions)\n"
">>>"
msgstr ""
#: ../../tutorial/errors.rst:557
msgid ""
"By using ``except*`` instead of ``except``, we can selectively handle only "
"the exceptions in the group that match a certain type. In the following "
"example, which shows a nested exception group, each ``except*`` clause "
"extracts from the group exceptions of a certain type while letting all other "
"exceptions propagate to other clauses and eventually to be reraised. ::"
msgstr ""
#: ../../tutorial/errors.rst:564
msgid ""
">>> def f():\n"
"... raise ExceptionGroup(\n"
"... \"group1\",\n"
"... [\n"
"... OSError(1),\n"
"... SystemError(2),\n"
"... ExceptionGroup(\n"
"... \"group2\",\n"
"... [\n"
"... OSError(3),\n"
"... RecursionError(4)\n"
"... ]\n"
"... )\n"
"... ]\n"
"... )\n"
"...\n"
">>> try:\n"
"... f()\n"
"... except* OSError as e:\n"
"... print(\"There were OSErrors\")\n"
"... except* SystemError as e:\n"
"... print(\"There were SystemErrors\")\n"
"...\n"
"There were OSErrors\n"
"There were SystemErrors\n"
" + Exception Group Traceback (most recent call last):\n"
" | File \"<stdin>\", line 2, in <module>\n"
" | f()\n"
" | ~^^\n"
" | File \"<stdin>\", line 2, in f\n"
" | raise ExceptionGroup(\n"
" | ...<12 lines>...\n"
" | )\n"
" | ExceptionGroup: group1 (1 sub-exception)\n"
" +-+---------------- 1 ----------------\n"
" | ExceptionGroup: group2 (1 sub-exception)\n"
" +-+---------------- 1 ----------------\n"
" | RecursionError: 4\n"
" +------------------------------------\n"
">>>"
msgstr ""
#: ../../tutorial/errors.rst:605
msgid ""
"Note that the exceptions nested in an exception group must be instances, not "
"types. This is because in practice the exceptions would typically be ones "
"that have already been raised and caught by the program, along the following "
"pattern::"
msgstr ""
#: ../../tutorial/errors.rst:610
msgid ""
">>> excs = []\n"
"... for test in tests:\n"
"... try:\n"
"... test.run()\n"
"... except Exception as e:\n"
"... excs.append(e)\n"
"...\n"
">>> if excs:\n"
"... raise ExceptionGroup(\"Test Failures\", excs)\n"
"..."
msgstr ""
#: ../../tutorial/errors.rst:625
msgid "Enriching Exceptions with Notes"
msgstr ""
#: ../../tutorial/errors.rst:627
msgid ""
"When an exception is created in order to be raised, it is usually "
"initialized with information that describes the error that has occurred. "
"There are cases where it is useful to add information after the exception "
"was caught. For this purpose, exceptions have a method ``add_note(note)`` "
"that accepts a string and adds it to the exception's notes list. The "
"standard traceback rendering includes all notes, in the order they were "
"added, after the exception. ::"
msgstr ""
#: ../../tutorial/errors.rst:634
msgid ""
">>> try:\n"
"... raise TypeError('bad type')\n"
"... except Exception as e:\n"
"... e.add_note('Add some information')\n"
"... e.add_note('Add some more information')\n"
"... raise\n"
"...\n"
"Traceback (most recent call last):\n"
" File \"<stdin>\", line 2, in <module>\n"
" raise TypeError('bad type')\n"
"TypeError: bad type\n"
"Add some information\n"
"Add some more information\n"
">>>"
msgstr ""
#: ../../tutorial/errors.rst:649
msgid ""
"For example, when collecting exceptions into an exception group, we may want "
"to add context information for the individual errors. In the following each "
"exception in the group has a note indicating when this error has occurred. ::"
msgstr ""
#: ../../tutorial/errors.rst:653
msgid ""
">>> def f():\n"
"... raise OSError('operation failed')\n"
"...\n"
">>> excs = []\n"
">>> for i in range(3):\n"
"... try:\n"
"... f()\n"
"... except Exception as e:\n"
You can’t perform that action at this time.