Viewing: github-redirect.dependabot.com

Repository navigation

More items

Blame

History

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

# SOME DESCRIPTIVE TITLE.

# This file is distributed under the same license as the Python package.

# Translators:

# tomo, 2017

# <xwhhsprings@gmail.com>, 2015

msgid ""

msgstr ""

"Project-Id-Version: Python 2.7\n"

"Report-Msgid-Bugs-To: \n"

"POT-Creation-Date: 2021-01-01 01:01+0900\n"

"PO-Revision-Date: 2018-12-22 16:43+0000\n"

"Last-Translator: tomo\n"

"Language-Team: Japanese (http://www.transifex.com/python-doc/python-27/"

"language/ja/)\n"

"Language: ja\n"

"MIME-Version: 1.0\n"

"Content-Type: text/plain; charset=UTF-8\n"

"Content-Transfer-Encoding: 8bit\n"

"Plural-Forms: nplurals=1; plural=0;\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 error)* * (exception)* "

#: ../../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 error) Python "

"::"

#: ../../tutorial/errors.rst:26

msgid ""

"The parser repeats the offending line and displays a little 'arrow' pointing "

"at the earliest point in the line where the error was detected. The error "

"is caused by (or at least detected at) the token *preceding* the arrow: in "

"the example, the error is detected at the keyword :keyword:`print`, since a "

"colon (``':'``) is missing before it. File name and line number are printed "

"so you know where to look in case the input came from a script."

msgstr ""

" ** "

" ()"

" :keyword:`print` (``':'``) "

#: ../../tutorial/errors.rst:37

msgid "Exceptions"

msgstr ""

#: ../../tutorial/errors.rst:39

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 ""

" * (exception)* "

"Python "

"::"

#: ../../tutorial/errors.rst:58

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 ""

" "

"(type) "

" :exc:`ZeroDivisionError`, :exc:`NameError`, :exc:`TypeError` "

" ("

") "

" ()"

#: ../../tutorial/errors.rst:66

msgid ""

"The rest of the line provides detail based on the type of exception and what "

"caused it."

msgstr ""

#: ../../tutorial/errors.rst:69

msgid ""

"The preceding part of the error message shows the context where the "

"exception happened, 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 ""

" (context) "

" (stack traceback) "

#: ../../tutorial/errors.rst:74

msgid ""

":ref:`bltin-exceptions` lists the built-in exceptions and their meanings."

msgstr ""

":ref:`bltin-exceptions` "

#: ../../tutorial/errors.rst:80

msgid "Handling Exceptions"

msgstr ""

#: ../../tutorial/errors.rst:82

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:96

msgid "The :keyword:`try` statement works as follows."

msgstr ":keyword:`try` "

#: ../../tutorial/errors.rst:98

msgid ""

"First, the *try clause* (the statement(s) between the :keyword:`try` and :"

"keyword:`except` keywords) is executed."

msgstr ""

" *try (try clause)* ( :keyword:`try` :keyword:`except` "

") "

#: ../../tutorial/errors.rst:101

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:104

msgid ""

"If an exception occurs during execution of the 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 :keyword:`try` statement."

msgstr ""

"try "

" :keyword:`except` "

"except :keyword:`try` "

#: ../../tutorial/errors.rst:109

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 a "

"message as shown above."

msgstr ""

" except :"

"keyword:`try` (handler) "

" * (unhandled exception)* "

#: ../../tutorial/errors.rst:114

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 as a parenthesized tuple, for example::"

msgstr ""

" :keyword:`try` except "

" try :"

"keyword:`try` except "

"::"

#: ../../tutorial/errors.rst:123

msgid ""

"Note that the parentheses around this tuple are required, because ``except "

"ValueError, e:`` was the syntax used for what is normally written as "

"``except ValueError as e:`` in modern Python (described below). The old "

"syntax is still supported for backwards compatibility. This means ``except "

"RuntimeError, TypeError`` is not equivalent to ``except (RuntimeError, "

"TypeError):`` but to ``except RuntimeError as TypeError:`` which is not what "

"you want."

msgstr ""

" ``except ValueError, e:`` "

" Python ``except ValueError as e:`` ()"

" "

"``except RuntimeError, TypeError`` ``except (RuntimeError, TypeError):`` "

" ``except RuntimeError as TypeError:`` "

#: ../../tutorial/errors.rst:131

msgid ""

"The last except clause may omit the exception name(s), to serve as a "

"wildcard. Use this with extreme caution, since it is easy to mask a real "

"programming error in this way! It can also be used to print an error "

"message and then re-raise the exception (allowing a caller to handle the "

"exception as well)::"

msgstr ""

" except (wildcard) "

" except "

" () "

"::"

#: ../../tutorial/errors.rst:150

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 ""

":keyword:`try` ... :keyword:`except` *else (else "

"clause)* :keyword:`else` :"

"keyword:`except` :keyword:`else` "

"try "

"::"

#: ../../tutorial/errors.rst:164

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 ""

" :keyword:`try` :keyword:`else` "

" :keyword:`try` ... :keyword:"

"`except` "

#: ../../tutorial/errors.rst:169

msgid ""

"When an exception occurs, it may have an associated value, also known as the "

"exception's *argument*. The presence and type of the argument depend on the "

"exception type."

msgstr ""

" * (argument)* "

#: ../../tutorial/errors.rst:173

msgid ""

"The except clause may specify a variable after the exception name (or "

"tuple). The variable is bound to an exception instance with the arguments "

"stored in ``instance.args``. For convenience, the exception instance "

"defines :meth:`__str__` so the arguments can be printed directly without "

"having to reference ``.args``."

msgstr ""

"except () "

" ``instance.args`` "

" :meth:`__str__` "

" ``.args`` "

#: ../../tutorial/errors.rst:179

msgid ""

"One may also instantiate an exception first before raising it and add any "

"attributes to it as desired. ::"

msgstr ""

#: ../../tutorial/errors.rst:198

msgid ""

"If an exception has an argument, it is printed as the last part ('detail') "

"of the message for unhandled exceptions."

msgstr ""

" "

"() "

#: ../../tutorial/errors.rst:201

msgid ""

"Exception handlers don't just handle exceptions if they occur immediately in "

"the try clause, but also if they occur inside functions that are called "

"(even indirectly) in the try clause. For example::"

msgstr ""

"try "

"try () "

"::"

#: ../../tutorial/errors.rst:219

msgid "Raising Exceptions"

msgstr ""

#: ../../tutorial/errors.rst:221

msgid ""

"The :keyword:`raise` statement allows the programmer to force a specified "

"exception to occur. For example::"

msgstr ""

":keyword:`raise` ::"

#: ../../tutorial/errors.rst:229

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:`Exception`)."

msgstr ""

":keyword:`raise` (:"

"class:`Exception` )"

#: ../../tutorial/errors.rst:233

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 ""

" :keyword:`raise` "

"::"

#: ../../tutorial/errors.rst:252

msgid "User-defined Exceptions"

msgstr ""

#: ../../tutorial/errors.rst:254

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. For example::"

msgstr ""

" (Python :ref:`tut-classes` )"

" :exc:`Exception` "

"::"

#: ../../tutorial/errors.rst:276

msgid ""

"In this example, the default :meth:`__init__` of :class:`Exception` has been "

"overridden. The new behavior simply creates the *value* attribute. This "

"replaces the default behavior of creating the *args* attribute."

msgstr ""

" :class:`Exception` :meth:`__init__` "

" *value* "

" *args* "

#: ../../tutorial/errors.rst:280

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. When creating a module that can raise several distinct errors, a "

"common practice is to create a base class for exceptions defined by that "

"module, and subclass that to create specific exception classes for different "

"error conditions::"

msgstr ""

"::"

#: ../../tutorial/errors.rst:318

msgid ""

"Most exceptions are defined with names that end in \"Error\", similar to the "

"naming of the standard exceptions."

msgstr ""

"\"Error\" "

#: ../../tutorial/errors.rst:321

msgid ""

"Many standard modules define their own exceptions to report errors that may "

"occur in functions they define. More information on classes is presented in "

"chapter :ref:`tut-classes`."

msgstr ""

" :ref:`tut-classes` "

#: ../../tutorial/errors.rst:329

msgid "Defining Clean-up Actions"

msgstr ""

#: ../../tutorial/errors.rst:331

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 ""

":keyword:`try` "

"::"

#: ../../tutorial/errors.rst:345

msgid ""

"A *finally clause* is always executed before leaving the :keyword:`try` "

"statement, whether an exception has occurred or not. When an exception has "

"occurred in the :keyword:`try` clause and has not been handled by an :"

"keyword:`except` clause (or it has occurred in an :keyword:`except` or :"

"keyword:`else` clause), it is re-raised after the :keyword:`finally` clause "

"has been executed. The :keyword:`finally` clause is also executed \"on the "

"way out\" when any other clause of the :keyword:`try` statement is left via "

"a :keyword:`break`, :keyword:`continue` or :keyword:`return` statement. A "

"more complicated example (having :keyword:`except` and :keyword:`finally` "

"clauses in the same :keyword:`try` statement works as of Python 2.5)::"

msgstr ""

"*finally (finally clause)* :"

"keyword:`try` :keyword:`try` "

" :keyword:`except` :keyword:"

"`except` :keyword:`else` :keyword:`finally` "

" :keyword:`finally` :"

"keyword:`try` :keyword:`break` :keyword:`continue` :keyword:"

"`return` \"\" "

" (:keyword:`except` :keyword:`finally` :keyword:`try` "

" Python 2.5 )"

#: ../../tutorial/errors.rst:379

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 ""

" :keyword:`finally` "

" :exc:`TypeError` :keyword:`except` "

" :keyword:`finally` "

#: ../../tutorial/errors.rst:384

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 ""

" :keyword:`finally` ("

")"

#: ../../tutorial/errors.rst:392

msgid "Predefined Clean-up Actions"

msgstr ""

#: ../../tutorial/errors.rst:394

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:402

msgid ""

"The problem with this code is that it leaves the file open for an "

"indeterminate amount of time after 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 ""

" :keyword:`with` "

" ::"

#: ../../tutorial/errors.rst:412

msgid ""

"After the statement is executed, the file *f* is always closed, even if a "

"problem was encountered while processing the lines. Other objects which "

"provide predefined clean-up actions will indicate this in their "

"documentation."

msgstr ""

" "

"*f* close "

Terms
Privacy
Security
Status
Community
Docs
Contact
Manage cookies
Do not share my personal information

Navigation Menu

Repository navigation

Files

errors.po

errors.po

Navigation Menu

Repository navigation

FilesExpand file tree

Breadcrumbs

errors.po

Latest commit

History

Breadcrumbs

errors.po

File metadata and controls

Footer

Footer navigation

Files