Viewing: github-redirect.dependabot.com

Repository navigation

More items

Blame

History

Code
Blame

458 lines (415 loc) 18.6 KB

Raw

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

# SOME DESCRIPTIVE TITLE.

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

# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.

# Translators:

# python-doc bot, 2025

# Takanori Suzuki <takanori@takanory.net>, 2025

#, fuzzy

msgid ""

msgstr ""

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

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

"POT-Creation-Date: 2026-09-23 18:03+0000\n"

"PO-Revision-Date: 2025-09-16 00:02+0000\n"

"Last-Translator: Takanori Suzuki <takanori@takanory.net>, 2025\n"

"Language-Team: Japanese (https://app.transifex.com/python-doc/teams/5390/"

"ja/)\n"

"MIME-Version: 1.0\n"

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

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

"Language: ja\n"

"Plural-Forms: nplurals=1; plural=0;\n"

#: ../../tutorial/venv.rst:6

msgid "Virtual Environments and Packages"

msgstr ""

#: ../../tutorial/venv.rst:9

msgid "Introduction"

msgstr ""

#: ../../tutorial/venv.rst:11

msgid ""

"Python applications will often use packages and modules that don't come as "

"part of the standard library. Applications will sometimes need a specific "

"version of a library, because the application may require that a particular "

"bug has been fixed or the application may be written using an obsolete "

"version of the library's interface."

msgstr ""

"Python "

#: ../../tutorial/venv.rst:17

msgid ""

"This means it may not be possible for one Python installation to meet the "

"requirements of every application. If application A needs version 1.0 of a "

"particular module but application B needs version 2.0, then the requirements "

"are in conflict and installing either version 1.0 or 2.0 will leave one "

"application unable to run."

msgstr ""

"1Python"

"A 1.0 "

"B 2.0 "

"21.0 2.0 "

#: ../../tutorial/venv.rst:23

msgid ""

"The solution for this problem is to create a :term:`virtual environment`, a "

"self-contained directory tree that contains a Python installation for a "

"particular version of Python, plus a number of additional packages."

msgstr ""

" :term:`<virtual environment>` "

" Python Python "

#: ../../tutorial/venv.rst:27

msgid ""

"Different applications can then use different virtual environments. To "

"resolve the earlier example of conflicting requirements, application A can "

"have its own virtual environment with version 1.0 installed while "

"application B has another virtual environment with version 2.0. If "

"application B requires a library be upgraded to version 3.0, this will not "

"affect application A's environment."

msgstr ""

"A"

" 1.0 B"

" 2.0 "

"B 3.0 "

"A"

#: ../../tutorial/venv.rst:36

msgid "Creating Virtual Environments"

msgstr ""

#: ../../tutorial/venv.rst:38

msgid ""

"The module used to create and manage virtual environments is called :mod:"

"`venv`. :mod:`venv` will install the Python version from which the command "

"was run (as reported by the :option:`--version` option). For instance, "

"executing the command with ``python3.12`` will install version 3.12."

msgstr ""

" :mod:`venv` :mod:"

"`venv` Python (:option:`--version` "

") ``python3.12`` "

" 3.12 "

#: ../../tutorial/venv.rst:44

msgid ""

"To create a virtual environment, decide upon a directory where you want to "

"place it, and run the :mod:`venv` module as a script with the directory "

"path::"

msgstr ""

" "

" :mod:`venv` ::"

#: ../../tutorial/venv.rst:47

msgid "python -m venv tutorial-env"

msgstr "python -m venv tutorial-env"

#: ../../tutorial/venv.rst:49

msgid ""

"This will create the ``tutorial-env`` directory if it doesn't exist, and "

"also create directories inside it containing a copy of the Python "

"interpreter and various supporting files."

msgstr ""

" ``tutorial-env`` Python "

#: ../../tutorial/venv.rst:53

msgid ""

"A common directory location for a virtual environment is ``.venv``. This "

"name keeps the directory typically hidden in your shell and thus out of the "

"way while giving it a name that explains why the directory exists. It also "

"prevents clashing with ``.env`` environment variable definition files that "

"some tooling supports."

msgstr ""

" ``.venv`` "

" ``.env`` "

#: ../../tutorial/venv.rst:59

msgid "Once you've created a virtual environment, you may activate it."

msgstr ""

#: ../../tutorial/venv.rst:61

msgid "On Windows, run::"

msgstr "Windows ::"

#: ../../tutorial/venv.rst:63

msgid "tutorial-env\\Scripts\\activate"

msgstr "tutorial-env\\Scripts\\activate"

#: ../../tutorial/venv.rst:65

msgid "On Unix or MacOS, run::"

msgstr "Unix Mac OS ::"

#: ../../tutorial/venv.rst:67

msgid "source tutorial-env/bin/activate"

msgstr "source tutorial-env/bin/activate"

#: ../../tutorial/venv.rst:69

msgid ""

"(This script is written for the bash shell. If you use the :program:`csh` "

"or :program:`fish` shells, there are alternate ``activate.csh`` and "

"``activate.fish`` scripts you should use instead.)"

msgstr ""

"( bash shell :program:`csh` :program:"

"`fish` ``activate.csh`` ``activate."

"fish`` )"

#: ../../tutorial/venv.rst:74

msgid ""

"Activating the virtual environment will change your shell's prompt to show "

"what virtual environment you're using, and modify the environment so that "

"running ``python`` will get you that particular version and installation of "

"Python. For example:"

msgstr ""

"``python`` Python "

"::"

#: ../../tutorial/venv.rst:79

msgid ""

"$ source ~/envs/tutorial-env/bin/activate\n"

"(tutorial-env) $ python\n"

"Python 3.5.1 (default, May 6 2016, 10:59:36)\n"

" ...\n"

">>> import sys\n"

">>> sys.path\n"

"['', '/usr/local/lib/python35.zip', ...,\n"

"'~/envs/tutorial-env/lib/python3.5/site-packages']\n"

">>>"

msgstr ""

"$ source ~/envs/tutorial-env/bin/activate\n"

"(tutorial-env) $ python\n"

"Python 3.5.1 (default, May 6 2016, 10:59:36)\n"

" ...\n"

">>> import sys\n"

">>> sys.path\n"

"['', '/usr/local/lib/python35.zip', ...,\n"

"'~/envs/tutorial-env/lib/python3.5/site-packages']\n"

">>>"

#: ../../tutorial/venv.rst:91

msgid ""

"Note that the activated virtual environment does not alter the "

"``PYTHONPATH`` variable in any way. This may lead to unexpected results if "

"the path includes references to code which is incompatible with the Python "

"version the virtual environment is using. The best practice is to ``unset "

"PYTHONPATH`` in bash or the equivalent for the shell you are using."

msgstr ""

#: ../../tutorial/venv.rst:96

msgid "To deactivate a virtual environment, type::"

msgstr "::"

#: ../../tutorial/venv.rst:98

msgid "deactivate"

msgstr "deactivate"

#: ../../tutorial/venv.rst:100

msgid "into the terminal."

msgstr ""

#: ../../tutorial/venv.rst:103

msgid "Managing Packages with pip"

msgstr "pip "

#: ../../tutorial/venv.rst:105

msgid ""

"You can install, upgrade, and remove packages using a program called :"

"program:`pip`. By default ``pip`` will install packages from the `Python "

"Package Index <https://pypi.org>`_. You can browse the Python Package Index "

"by going to it in your web browser."

msgstr ""

":program:`pip` "

" ``pip`` `Python Package Index "

"<https://pypi.org>`_ "

"Python Package Index "

#: ../../tutorial/venv.rst:110

msgid ""

"``pip`` has a number of subcommands: \"install\", \"uninstall\", \"freeze\", "

"etc. (Consult the :ref:`installing-index` guide for complete documentation "

"for ``pip``.)"

msgstr ""

"``pip`` \"install\" \"uninstall\" \"freeze\" "

" (``pip`` :ref:`installing-"

"index` )"

#: ../../tutorial/venv.rst:114

msgid ""

"You can install the latest version of a package by specifying a package's "

"name:"

msgstr ""

"::"

#: ../../tutorial/venv.rst:116

msgid ""

"(tutorial-env) $ python -m pip install novas\n"

"Collecting novas\n"

" Downloading novas-3.1.1.3.tar.gz (136kB)\n"

"Installing collected packages: novas\n"

" Running setup.py install for novas\n"

"Successfully installed novas-3.1.1.3"

msgstr ""

"(tutorial-env) $ python -m pip install novas\n"

"Collecting novas\n"

" Downloading novas-3.1.1.3.tar.gz (136kB)\n"

"Installing collected packages: novas\n"

" Running setup.py install for novas\n"

"Successfully installed novas-3.1.1.3"

#: ../../tutorial/venv.rst:125

msgid ""

"You can also install a specific version of a package by giving the package "

"name followed by ``==`` and the version number:"

msgstr ""

" ``==`` "

"::"

#: ../../tutorial/venv.rst:128

msgid ""

"(tutorial-env) $ python -m pip install requests==2.6.0\n"

"Collecting requests==2.6.0\n"

" Using cached requests-2.6.0-py2.py3-none-any.whl\n"

"Installing collected packages: requests\n"

"Successfully installed requests-2.6.0"

msgstr ""

"(tutorial-env) $ python -m pip install requests==2.6.0\n"

"Collecting requests==2.6.0\n"

" Using cached requests-2.6.0-py2.py3-none-any.whl\n"

"Installing collected packages: requests\n"

"Successfully installed requests-2.6.0"

#: ../../tutorial/venv.rst:136

msgid ""

"If you re-run this command, ``pip`` will notice that the requested version "

"is already installed and do nothing. You can supply a different version "

"number to get that version, or you can run ``python -m pip install --"

"upgrade`` to upgrade the package to the latest version:"

msgstr ""

"``pip`` "

"``python -m pip install --upgrade`` "

"::"

#: ../../tutorial/venv.rst:141

msgid ""

"(tutorial-env) $ python -m pip install --upgrade requests\n"

"Collecting requests\n"

"Installing collected packages: requests\n"

" Found existing installation: requests 2.6.0\n"

" Uninstalling requests-2.6.0:\n"

" Successfully uninstalled requests-2.6.0\n"

"Successfully installed requests-2.7.0"

msgstr ""

"(tutorial-env) $ python -m pip install --upgrade requests\n"

"Collecting requests\n"

"Installing collected packages: requests\n"

" Found existing installation: requests 2.6.0\n"

" Uninstalling requests-2.6.0:\n"

" Successfully uninstalled requests-2.6.0\n"

"Successfully installed requests-2.7.0"

#: ../../tutorial/venv.rst:151

msgid ""

"``python -m pip uninstall`` followed by one or more package names will "

"remove the packages from the virtual environment."

msgstr ""

"``python -m pip uninstall`` 1"

#: ../../tutorial/venv.rst:154

msgid ""

"``python -m pip show`` will display information about a particular package:"

msgstr "``python -m pip show`` ::"

#: ../../tutorial/venv.rst:156

msgid ""

"(tutorial-env) $ python -m pip show requests\n"

"---\n"

"Metadata-Version: 2.0\n"

"Name: requests\n"

"Version: 2.7.0\n"

"Summary: Python HTTP for Humans.\n"

"Home-page: http://python-requests.org\n"

"Author: Kenneth Reitz\n"

"Author-email: me@kennethreitz.com\n"

"License: Apache 2.0\n"

"Location: /Users/akuchling/envs/tutorial-env/lib/python3.4/site-packages\n"

"Requires:"

msgstr ""

"(tutorial-env) $ python -m pip show requests\n"

"---\n"

"Metadata-Version: 2.0\n"

"Name: requests\n"

"Version: 2.7.0\n"

"Summary: Python HTTP for Humans.\n"

"Home-page: http://python-requests.org\n"

"Author: Kenneth Reitz\n"

"Author-email: me@kennethreitz.com\n"

"License: Apache 2.0\n"

"Location: /Users/akuchling/envs/tutorial-env/lib/python3.4/site-packages\n"

"Requires:"

#: ../../tutorial/venv.rst:171

msgid ""

"``python -m pip list`` will display all of the packages installed in the "

"virtual environment:"

msgstr ""

"``python -m pip list`` "

"::"

#: ../../tutorial/venv.rst:174

msgid ""

"(tutorial-env) $ python -m pip list\n"

"novas (3.1.1.3)\n"

"numpy (1.9.2)\n"

"pip (7.0.3)\n"

"requests (2.7.0)\n"

"setuptools (16.0)"

msgstr ""

"(tutorial-env) $ python -m pip list\n"

"novas (3.1.1.3)\n"

"numpy (1.9.2)\n"

"pip (7.0.3)\n"

"requests (2.7.0)\n"

"setuptools (16.0)"

#: ../../tutorial/venv.rst:183

msgid ""

"``python -m pip freeze`` will produce a similar list of the installed "

"packages, but the output uses the format that ``python -m pip install`` "

"expects. A common convention is to put this list in a ``requirements.txt`` "

"file:"

msgstr ""

"``python -m pip freeze`` ``python -m "

"pip install`` "

" ``requirements.txt`` :"

#: ../../tutorial/venv.rst:187

msgid ""

"(tutorial-env) $ python -m pip freeze > requirements.txt\n"

"(tutorial-env) $ cat requirements.txt\n"

"novas==3.1.1.3\n"

"numpy==1.9.2\n"

"requests==2.7.0"

msgstr ""

"(tutorial-env) $ python -m pip freeze > requirements.txt\n"

"(tutorial-env) $ cat requirements.txt\n"

"novas==3.1.1.3\n"

"numpy==1.9.2\n"

"requests==2.7.0"

#: ../../tutorial/venv.rst:195

msgid ""

"The ``requirements.txt`` can then be committed to version control and "

"shipped as part of an application. Users can then install all the necessary "

"packages with ``install -r``:"

msgstr ""

"``requirements.txt`` "

" ``install -"

"r`` ::"

#: ../../tutorial/venv.rst:199

msgid ""

"(tutorial-env) $ python -m pip install -r requirements.txt\n"

"Collecting novas==3.1.1.3 (from -r requirements.txt (line 1))\n"

" ...\n"

"Collecting numpy==1.9.2 (from -r requirements.txt (line 2))\n"

" ...\n"

"Collecting requests==2.7.0 (from -r requirements.txt (line 3))\n"

" ...\n"

"Installing collected packages: novas, numpy, requests\n"

" Running setup.py install for novas\n"

"Successfully installed novas-3.1.1.3 numpy-1.9.2 requests-2.7.0"

msgstr ""

"(tutorial-env) $ python -m pip install -r requirements.txt\n"

"Collecting novas==3.1.1.3 (from -r requirements.txt (line 1))\n"

" ...\n"

"Collecting numpy==1.9.2 (from -r requirements.txt (line 2))\n"

" ...\n"

"Collecting requests==2.7.0 (from -r requirements.txt (line 3))\n"

" ...\n"

"Installing collected packages: novas, numpy, requests\n"

" Running setup.py install for novas\n"

"Successfully installed novas-3.1.1.3 numpy-1.9.2 requests-2.7.0"

#: ../../tutorial/venv.rst:212

msgid ""

"``pip`` has many more options. Consult the :ref:`installing-index` guide "

"for complete documentation for ``pip``. When you've written a package and "

"want to make it available on the Python Package Index, consult the `Python "

"packaging user guide`_."

msgstr ""

"``pip`` ``pip`` :"

"ref:`installing-index` Python "

"Package Index `Python packaging user guide`_ "

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

Navigation Menu

Repository navigation

Files

Navigation Menu

Repository navigation

FilesExpand file tree

Breadcrumbs

venv.po

Latest commit

History

Breadcrumbs

venv.po

File metadata and controls

Footer

Footer navigation

Files