python-docs-id/extending/embedding.po at 3.14 · python/python-docs-id · GitHub

Repository navigation

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

499

500

501

# SOME DESCRIPTIVE TITLE.

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

# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.

#, fuzzy

msgid ""

msgstr ""

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

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

"POT-Creation-Date: 2026-10-03 17:41+0000\n"

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

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

"id/)\n"

"MIME-Version: 1.0\n"

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

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

"Language: id\n"

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

msgid "Embedding Python in Another Application"

msgstr ""

msgid ""

"The previous chapters discussed how to extend Python, that is, how to extend "

"the functionality of Python by attaching a library of C functions to it. It "

"is also possible to do it the other way around: enrich your C/C++ "

"application by embedding Python in it. Embedding provides your application "

"with the ability to implement some of the functionality of your application "

"in Python rather than C or C++. This can be used for many purposes; one "

"example would be to allow users to tailor the application to their needs by "

"writing some scripts in Python. You can also use it yourself if some of the "

"functionality can be written in Python more easily."

msgstr ""

msgid ""

"Embedding Python is similar to extending it, but not quite. The difference "

"is that when you extend Python, the main program of the application is still "

"the Python interpreter, while if you embed Python, the main program may have "

"nothing to do with Python --- instead, some parts of the application "

"occasionally call the Python interpreter to run some Python code."

msgstr ""

msgid ""

"So if you are embedding Python, you are providing your own main program. "

"One of the things this main program has to do is initialize the Python "

"interpreter. At the very least, you have to call the function :c:func:"

"`Py_Initialize`. There are optional calls to pass command line arguments to "

"Python. Then later you can call the interpreter from any part of the "

"application."

msgstr ""

msgid ""

"There are several different ways to call the interpreter: you can pass a "

"string containing Python statements to :c:func:`PyRun_SimpleString`, or you "

"can pass a stdio file pointer and a file name (for identification in error "

"messages only) to :c:func:`PyRun_SimpleFile`. You can also call the lower-"

"level operations described in the previous chapters to construct and use "

"Python objects."

msgstr ""

msgid ":ref:`c-api-index`"

msgstr ""

msgid ""

"The details of Python's C interface are given in this manual. A great deal "

"of necessary information can be found here."

msgstr ""

msgid "Very High Level Embedding"

msgstr ""

msgid ""

"The simplest form of embedding Python is the use of the very high level "

"interface. This interface is intended to execute a Python script without "

"needing to interact with the application directly. This can for example be "

"used to perform some operation on a file. ::"

msgstr ""

msgid ""

"#define PY_SSIZE_T_CLEAN\n"

"#include <Python.h>\n"

"\n"

"int\n"

"main(int argc, char *argv[])\n"

"{\n"

" PyStatus status;\n"

" PyConfig config;\n"

" PyConfig_InitPythonConfig(&config);\n"

"\n"

" /* optional but recommended */\n"

" status = PyConfig_SetBytesString(&config, &config.program_name, "

"argv[0]);\n"

" if (PyStatus_Exception(status)) {\n"

" goto exception;\n"

" }\n"

"\n"

" status = Py_InitializeFromConfig(&config);\n"

" if (PyStatus_Exception(status)) {\n"

" goto exception;\n"

" }\n"

" PyConfig_Clear(&config);\n"

"\n"

" PyRun_SimpleString(\"from time import time,ctime\\n\"\n"

" \"print('Today is', ctime(time()))\\n\");\n"

" if (Py_FinalizeEx() < 0) {\n"

" exit(120);\n"

" }\n"

" return 0;\n"

"\n"

" exception:\n"

" PyConfig_Clear(&config);\n"

" Py_ExitStatusException(status);\n"

"}"

msgstr ""

msgid ""

"``#define PY_SSIZE_T_CLEAN`` was used to indicate that ``Py_ssize_t`` should "

"be used in some APIs instead of ``int``. It is not necessary since Python "

"3.13, but we keep it here for backward compatibility. See :ref:`arg-parsing-"

"string-and-buffers` for a description of this macro."

msgstr ""

msgid ""

"Setting :c:member:`PyConfig.program_name` should be called before :c:func:"

"`Py_InitializeFromConfig` to inform the interpreter about paths to Python "

"run-time libraries. Next, the Python interpreter is initialized with :c:"

"func:`Py_Initialize`, followed by the execution of a hard-coded Python "

"script that prints the date and time. Afterwards, the :c:func:"

"`Py_FinalizeEx` call shuts the interpreter down, followed by the end of the "

"program. In a real program, you may want to get the Python script from "

"another source, perhaps a text-editor routine, a file, or a database. "

"Getting the Python code from a file can better be done by using the :c:func:"

"`PyRun_SimpleFile` function, which saves you the trouble of allocating "

"memory space and loading the file contents."

msgstr ""

msgid "Beyond Very High Level Embedding: An overview"

msgstr ""

msgid ""

"The high level interface gives you the ability to execute arbitrary pieces "

"of Python code from your application, but exchanging data values is quite "

"cumbersome to say the least. If you want that, you should use lower level "

"calls. At the cost of having to write more C code, you can achieve almost "

"anything."

msgstr ""

msgid ""

"It should be noted that extending Python and embedding Python is quite the "

"same activity, despite the different intent. Most topics discussed in the "

"previous chapters are still valid. To show this, consider what the extension "

"code from Python to C really does:"

msgstr ""

msgid "Convert data values from Python to C,"

msgstr ""

msgid "Perform a function call to a C routine using the converted values, and"

msgstr ""

msgid "Convert the data values from the call from C to Python."

msgstr ""

msgid "When embedding Python, the interface code does:"

msgstr ""

msgid "Convert data values from C to Python,"

msgstr ""

msgid ""

"Perform a function call to a Python interface routine using the converted "

"values, and"

msgstr ""

msgid "Convert the data values from the call from Python to C."

msgstr ""

msgid ""

"As you can see, the data conversion steps are simply swapped to accommodate "

"the different direction of the cross-language transfer. The only difference "

"is the routine that you call between both data conversions. When extending, "

"you call a C routine, when embedding, you call a Python routine."

msgstr ""

msgid ""

"This chapter will not discuss how to convert data from Python to C and vice "

"versa. Also, proper use of references and dealing with errors is assumed to "

"be understood. Since these aspects do not differ from extending the "

"interpreter, you can refer to earlier chapters for the required information."

msgstr ""

msgid "Pure Embedding"

msgstr ""

msgid ""

"The first program aims to execute a function in a Python script. Like in the "

"section about the very high level interface, the Python interpreter does not "

"directly interact with the application (but that will change in the next "

"section)."

msgstr ""

msgid "The code to run a function defined in a Python script is:"

msgstr ""

msgid ""

"#define PY_SSIZE_T_CLEAN\n"

"#include <Python.h>\n"

"\n"

"int\n"

"main(int argc, char *argv[])\n"

"{\n"

" PyObject *pName, *pModule, *pFunc;\n"

" PyObject *pArgs, *pValue;\n"

" int i;\n"

"\n"

" if (argc < 3) {\n"

" fprintf(stderr,\"Usage: call pythonfile funcname [args]\\n\");\n"

" return 1;\n"

" }\n"

"\n"

" Py_Initialize();\n"

" pName = PyUnicode_DecodeFSDefault(argv[1]);\n"

" /* Error checking of pName left out */\n"

"\n"

" pModule = PyImport_Import(pName);\n"

" Py_DECREF(pName);\n"

"\n"

" if (pModule != NULL) {\n"

" pFunc = PyObject_GetAttrString(pModule, argv[2]);\n"

" /* pFunc is a new reference */\n"

"\n"

" if (pFunc && PyCallable_Check(pFunc)) {\n"

" pArgs = PyTuple_New(argc - 3);\n"

" for (i = 0; i < argc - 3; ++i) {\n"

" pValue = PyLong_FromLong(atoi(argv[i + 3]));\n"

" if (!pValue) {\n"

" Py_DECREF(pArgs);\n"

" Py_DECREF(pModule);\n"

" fprintf(stderr, \"Cannot convert argument\\n\");\n"

" return 1;\n"

" }\n"

" /* pValue reference stolen here: */\n"

" PyTuple_SetItem(pArgs, i, pValue);\n"

" }\n"

" pValue = PyObject_CallObject(pFunc, pArgs);\n"

" Py_DECREF(pArgs);\n"

" if (pValue != NULL) {\n"

" printf(\"Result of call: %ld\\n\", PyLong_AsLong(pValue));\n"

" Py_DECREF(pValue);\n"

" }\n"

" else {\n"

" Py_DECREF(pFunc);\n"

" Py_DECREF(pModule);\n"

" PyErr_Print();\n"

" fprintf(stderr,\"Call failed\\n\");\n"

" return 1;\n"

" }\n"

" else {\n"

" if (PyErr_Occurred())\n"

" PyErr_Print();\n"

" fprintf(stderr, \"Cannot find function \\\"%s\\\"\\n\", "

"argv[2]);\n"

" }\n"

" Py_XDECREF(pFunc);\n"

" Py_DECREF(pModule);\n"

" }\n"

" else {\n"

" PyErr_Print();\n"

" fprintf(stderr, \"Failed to load \\\"%s\\\"\\n\", argv[1]);\n"

" return 1;\n"

" }\n"

" if (Py_FinalizeEx() < 0) {\n"

" return 120;\n"

" }\n"

" return 0;\n"

"}\n"

msgstr ""

msgid ""

"This code loads a Python script using ``argv[1]``, and calls the function "

"named in ``argv[2]``. Its integer arguments are the other values of the "

"``argv`` array. If you :ref:`compile and link <compiling>` this program "

"(let's call the finished executable :program:`call`), and use it to execute "

"a Python script, such as:"

msgstr ""

msgid ""

"def multiply(a,b):\n"

" print(\"Will compute\", a, \"times\", b)\n"

" c = 0\n"

" for i in range(0, a):\n"

" c = c + b\n"

" return c"

msgstr ""

msgid "then the result should be:"

msgstr ""

msgid ""

"$ call multiply multiply 3 2\n"

"Will compute 3 times 2\n"

"Result of call: 6"

msgstr ""

msgid ""

"Although the program is quite large for its functionality, most of the code "

"is for data conversion between Python and C, and for error reporting. The "

"interesting part with respect to embedding Python starts with ::"

msgstr ""

msgid ""

"Py_Initialize();\n"

"pName = PyUnicode_DecodeFSDefault(argv[1]);\n"

"/* Error checking of pName left out */\n"

"pModule = PyImport_Import(pName);"

msgstr ""

msgid ""

"After initializing the interpreter, the script is loaded using :c:func:"

"`PyImport_Import`. This routine needs a Python string as its argument, "

"which is constructed using the :c:func:`PyUnicode_DecodeFSDefault` data "

"conversion routine. ::"

msgstr ""

msgid ""

"pFunc = PyObject_GetAttrString(pModule, argv[2]);\n"

"/* pFunc is a new reference */\n"

"\n"

"if (pFunc && PyCallable_Check(pFunc)) {\n"

" ...\n"

"}\n"

"Py_XDECREF(pFunc);"

msgstr ""

msgid ""

"Once the script is loaded, the name we're looking for is retrieved using :c:"

"func:`PyObject_GetAttrString`. If the name exists, and the object returned "

"is callable, you can safely assume that it is a function. The program then "

"proceeds by constructing a tuple of arguments as normal. The call to the "

"Python function is then made with::"

msgstr ""

msgid "pValue = PyObject_CallObject(pFunc, pArgs);"

msgstr ""

msgid ""

"Upon return of the function, ``pValue`` is either ``NULL`` or it contains a "

"reference to the return value of the function. Be sure to release the "

"reference after examining the value."

msgstr ""

msgid "Extending Embedded Python"

msgstr ""

msgid ""

"Until now, the embedded Python interpreter had no access to functionality "

"from the application itself. The Python API allows this by extending the "

"embedded interpreter. That is, the embedded interpreter gets extended with "

"routines provided by the application. While it sounds complex, it is not so "

"bad. Simply forget for a while that the application starts the Python "

"interpreter. Instead, consider the application to be a set of subroutines, "

"and write some glue code that gives Python access to those routines, just "

"like you would write a normal Python extension. For example::"

msgstr ""

msgid ""

"static int numargs=0;\n"

"\n"

"/* Return the number of arguments of the application command line */\n"

"static PyObject*\n"

"emb_numargs(PyObject *self, PyObject *args)\n"

"{\n"

" if(!PyArg_ParseTuple(args, \":numargs\"))\n"

" return NULL;\n"

" return PyLong_FromLong(numargs);\n"

"}\n"

"\n"

"static PyMethodDef emb_module_methods[] = {\n"

" {\"numargs\", emb_numargs, METH_VARARGS,\n"

" \"Return the number of arguments received by the process.\"},\n"

" {NULL, NULL, 0, NULL}\n"

"};\n"

"\n"

"static struct PyModuleDef emb_module = {\n"

" .m_base = PyModuleDef_HEAD_INIT,\n"

" .m_name = \"emb\",\n"

" .m_size = 0,\n"

" .m_methods = emb_module_methods,\n"

"};\n"

"\n"

"static PyObject*\n"

"PyInit_emb(void)\n"

"{\n"

" return PyModuleDef_Init(&emb_module);\n"

"}"

msgstr ""

msgid ""

"Insert the above code just above the :c:func:`main` function. Also, insert "

"the following two statements before the call to :c:func:`Py_Initialize`::"

msgstr ""

msgid ""

"numargs = argc;\n"

"PyImport_AppendInittab(\"emb\", &PyInit_emb);"

msgstr ""

msgid ""

"These two lines initialize the ``numargs`` variable, and make the :func:`!"

"emb.numargs` function accessible to the embedded Python interpreter. With "

"these extensions, the Python script can do things like"

msgstr ""

msgid ""

"import emb\n"

"print(\"Number of arguments\", emb.numargs())"

msgstr ""

msgid ""

"In a real application, the methods will expose an API of the application to "

"Python."

msgstr ""

msgid "Embedding Python in C++"

msgstr ""

msgid ""

"It is also possible to embed Python in a C++ program; precisely how this is "

"done will depend on the details of the C++ system used; in general you will "

"need to write the main program in C++, and use the C++ compiler to compile "

"and link your program. There is no need to recompile Python itself using C+"

"+."

msgstr ""

msgid "Compiling and Linking under Unix-like systems"

msgstr ""

msgid ""

"It is not necessarily trivial to find the right flags to pass to your "

"compiler (and linker) in order to embed the Python interpreter into your "

"application, particularly because Python needs to load library modules "

"implemented as C dynamic extensions (:file:`.so` files) linked against it."

msgstr ""

msgid ""

"To find out the required compiler and linker flags, you can execute the :"

"file:`python{X.Y}-config` script which is generated as part of the "

"installation process (a :file:`python3-config` script may also be "

"available). This script has several options, of which the following will be "

"directly useful to you:"

msgstr ""

msgid ""

"``pythonX.Y-config --cflags`` will give you the recommended flags when "

"compiling:"

msgstr ""

msgid ""

"$ /opt/bin/python3.11-config --cflags\n"

"-I/opt/include/python3.11 -I/opt/include/python3.11 -Wsign-compare -DNDEBUG "

"-g -fwrapv -O3 -Wall"

msgstr ""

msgid ""

"``pythonX.Y-config --ldflags --embed`` will give you the recommended flags "

"when linking:"

msgstr ""

msgid ""

"$ /opt/bin/python3.11-config --ldflags --embed\n"

"-L/opt/lib/python3.11/config-3.11-x86_64-linux-gnu -L/opt/lib -lpython3.11 -"

"lpthread -ldl -lutil -lm"

msgstr ""

msgid ""

"To avoid confusion between several Python installations (and especially "

"between the system Python and your own compiled Python), it is recommended "

"that you use the absolute path to :file:`python{X.Y}-config`, as in the "

"above example."

msgstr ""

msgid ""

"If this procedure doesn't work for you (it is not guaranteed to work for all "

"Unix-like platforms; however, we welcome :ref:`bug reports <reporting-"

"bugs>`) you will have to read your system's documentation about dynamic "

"linking and/or examine Python's :file:`Makefile` (use :func:`sysconfig."

"get_makefile_filename` to find its location) and compilation options. In "

"this case, the :mod:`sysconfig` module is a useful tool to programmatically "

"extract the configuration values that you will want to combine together. "

"For example:"

msgstr ""

msgid ""

">>> import sysconfig\n"

">>> sysconfig.get_config_var('LIBS')\n"

"'-lpthread -ldl -lutil'\n"

">>> sysconfig.get_config_var('LINKFORSHARED')\n"

"'-Xlinker -export-dynamic'"

msgstr ""

python-docs-id/extending/embedding.po at 3.14 · python/python-docs-id · GitHub

Repository navigation

Expand file tree

Breadcrumbs

embedding.po

Latest commit

History

Breadcrumbs

embedding.po

File metadata and controls