Skip to content
Snippets Groups Projects
Commit 450a64f5 authored by Matthias Klose's avatar Matthias Klose
Browse files

* Remove the FAQ for Python2.

parent 0e15b321
No related branches found
No related tags found
No related merge requests found
Expand all Hide whitespace changes
Inline Side-by-side
Showing
with 1 addition and 13347 deletions
debian/changelog
+ 1
− 0
View file @ 450a64f5
......@@ -5,6 +5,7 @@ python-defaults (2.7.15~rc1-2) UNRELEASED; urgency=medium
it. No changes for the "-all" packages.
* Update Vcs attributes.
* Remove Barry Warsaw as uploader.
* Remove the FAQ for Python2.
-- Matthias Klose <doko@debian.org> Wed, 06 Jun 2018 00:09:55 +0200
......
debian/rules
+ 0
− 42
View file @ 450a64f5
......@@ -89,34 +89,6 @@ endif
&& rm -f debian/control.tmp && exit 0; \
mv debian/control.tmp debian/control
faqs = index general programming library extending windows gui installed
get-faq:
# Note: This rule is broken due to web site reorg at python.org
rm -rf faq
mkdir faq
cd faq && \
wget -nv $(foreach p,$(faqs),http://python.org/doc/faq/$(p).ht)
sed 's,\<\([a-zA-Z0-9]*\.html\)\>,faq/\1,' faq/index.ht \
| awk '/^Translations$$/ {exit} {print}' > faq/FAQ.ht
( \
echo ''; \
echo 'This is a local copy of the online FAQ located at'; \
echo 'http://python.org/doc/faq.'; \
echo "The copy was fetched and generated in `date '+%B %Y'`."; \
) >> faq/FAQ.ht
rm -f faq/index.ht
make-faq:
set -e; \
cd faq && \
for p in *.ht; do \
p=`basename $$p .ht`; \
echo $(rst2html) $$p.ht $$p.html; \
awk 'NR > 2' $$p.ht > $$p.ht2; \
$(rst2html) $$p.ht2 $$p.html; \
rm -f $$p.ht2; \
done
MANPAGES ?= dh_python2.1 pycompile.1 pyclean.1
%.1: %.rst
......@@ -165,23 +137,9 @@ install: build stamp-dh_python stamp-install
stamp-install: stamp-build control-file stamp-control
dh_testdir
dh_testroot
dh_installdirs -ppython2 usr/share/doc/python2/faq
dh_installdirs -ppython usr/share/doc/python
dh_install
set -e; \
cd faq && \
for p in *.ht; do \
p=`basename $$p .ht`; \
cp $$p.html ../debian/python2/usr/share/doc/python2/faq/; \
done
mv debian/python2/usr/share/doc/python2/faq/FAQ.html \
debian/python2/usr/share/doc/python2/
ln -sf ../python2/faq \
debian/python/usr/share/doc/python/faq
ln -sf ../python2/FAQ.html \
debian/python/usr/share/doc/python/FAQ.html
touch stamp-install
stamp-dh_python:
......
faq/FAQ.ht deleted 100644 → 0
+ 0
− 19
View file @ 0e15b321
Title: Python Frequently Asked Question Lists
Content-type: text/x-rst
==========================================
Python Frequently Asked Question Lists
==========================================
* `General Python FAQ <faq/general.html>`_
* `Programming FAQ <faq/programming.html>`_
* `Library and Extension FAQ <faq/library.html>`_
* `Extending/Embedding FAQ <faq/extending.html>`_
* `Windows FAQ <faq/windows.html>`_
* `GUI Programming FAQ <faq/gui.html>`_
* `"Why is Python Installed on my Computer?" FAQ <faq/installed.html>`_
This is a local copy of the online FAQ located at
http://python.org/doc/faq.
The copy was fetched and generated in May 2007.
faq/FAQ.html deleted 100644 → 0
+ 0
− 358
View file @ 0e15b321
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="generator" content="Docutils 0.12: http://docutils.sourceforge.net/" />
<title>Python Frequently Asked Question Lists</title>
<style type="text/css">
/*
:Author: David Goodger (goodger@python.org)
:Id: $Id: html4css1.css 7614 2013-02-21 15:55:51Z milde $
:Copyright: This stylesheet has been placed in the public domain.
Default cascading style sheet for the HTML output of Docutils.
See http://docutils.sf.net/docs/howto/html-stylesheets.html for how to
customize this style sheet.
*/
/* used to remove borders from tables and images */
.borderless, table.borderless td, table.borderless th {
border: 0 }
table.borderless td, table.borderless th {
/* Override padding for "table.docutils td" with "! important".
The right padding separates the table cells. */
padding: 0 0.5em 0 0 ! important }
.first {
/* Override more specific margin styles with "! important". */
margin-top: 0 ! important }
.last, .with-subtitle {
margin-bottom: 0 ! important }
.hidden {
display: none }
a.toc-backref {
text-decoration: none ;
color: black }
blockquote.epigraph {
margin: 2em 5em ; }
dl.docutils dd {
margin-bottom: 0.5em }
object[type="image/svg+xml"], object[type="application/x-shockwave-flash"] {
overflow: hidden;
}
/* Uncomment (and remove this text!) to get bold-faced definition list terms
dl.docutils dt {
font-weight: bold }
*/
div.abstract {
margin: 2em 5em }
div.abstract p.topic-title {
font-weight: bold ;
text-align: center }
div.admonition, div.attention, div.caution, div.danger, div.error,
div.hint, div.important, div.note, div.tip, div.warning {
margin: 2em ;
border: medium outset ;
padding: 1em }
div.admonition p.admonition-title, div.hint p.admonition-title,
div.important p.admonition-title, div.note p.admonition-title,
div.tip p.admonition-title {
font-weight: bold ;
font-family: sans-serif }
div.attention p.admonition-title, div.caution p.admonition-title,
div.danger p.admonition-title, div.error p.admonition-title,
div.warning p.admonition-title, .code .error {
color: red ;
font-weight: bold ;
font-family: sans-serif }
/* Uncomment (and remove this text!) to get reduced vertical space in
compound paragraphs.
div.compound .compound-first, div.compound .compound-middle {
margin-bottom: 0.5em }
div.compound .compound-last, div.compound .compound-middle {
margin-top: 0.5em }
*/
div.dedication {
margin: 2em 5em ;
text-align: center ;
font-style: italic }
div.dedication p.topic-title {
font-weight: bold ;
font-style: normal }
div.figure {
margin-left: 2em ;
margin-right: 2em }
div.footer, div.header {
clear: both;
font-size: smaller }
div.line-block {
display: block ;
margin-top: 1em ;
margin-bottom: 1em }
div.line-block div.line-block {
margin-top: 0 ;
margin-bottom: 0 ;
margin-left: 1.5em }
div.sidebar {
margin: 0 0 0.5em 1em ;
border: medium outset ;
padding: 1em ;
background-color: #ffffee ;
width: 40% ;
float: right ;
clear: right }
div.sidebar p.rubric {
font-family: sans-serif ;
font-size: medium }
div.system-messages {
margin: 5em }
div.system-messages h1 {
color: red }
div.system-message {
border: medium outset ;
padding: 1em }
div.system-message p.system-message-title {
color: red ;
font-weight: bold }
div.topic {
margin: 2em }
h1.section-subtitle, h2.section-subtitle, h3.section-subtitle,
h4.section-subtitle, h5.section-subtitle, h6.section-subtitle {
margin-top: 0.4em }
h1.title {
text-align: center }
h2.subtitle {
text-align: center }
hr.docutils {
width: 75% }
img.align-left, .figure.align-left, object.align-left {
clear: left ;
float: left ;
margin-right: 1em }
img.align-right, .figure.align-right, object.align-right {
clear: right ;
float: right ;
margin-left: 1em }
img.align-center, .figure.align-center, object.align-center {
display: block;
margin-left: auto;
margin-right: auto;
}
.align-left {
text-align: left }
.align-center {
clear: both ;
text-align: center }
.align-right {
text-align: right }
/* reset inner alignment in figures */
div.align-right {
text-align: inherit }
/* div.align-center * { */
/* text-align: left } */
ol.simple, ul.simple {
margin-bottom: 1em }
ol.arabic {
list-style: decimal }
ol.loweralpha {
list-style: lower-alpha }
ol.upperalpha {
list-style: upper-alpha }
ol.lowerroman {
list-style: lower-roman }
ol.upperroman {
list-style: upper-roman }
p.attribution {
text-align: right ;
margin-left: 50% }
p.caption {
font-style: italic }
p.credits {
font-style: italic ;
font-size: smaller }
p.label {
white-space: nowrap }
p.rubric {
font-weight: bold ;
font-size: larger ;
color: maroon ;
text-align: center }
p.sidebar-title {
font-family: sans-serif ;
font-weight: bold ;
font-size: larger }
p.sidebar-subtitle {
font-family: sans-serif ;
font-weight: bold }
p.topic-title {
font-weight: bold }
pre.address {
margin-bottom: 0 ;
margin-top: 0 ;
font: inherit }
pre.literal-block, pre.doctest-block, pre.math, pre.code {
margin-left: 2em ;
margin-right: 2em }
pre.code .ln { color: grey; } /* line numbers */
pre.code, code { background-color: #eeeeee }
pre.code .comment, code .comment { color: #5C6576 }
pre.code .keyword, code .keyword { color: #3B0D06; font-weight: bold }
pre.code .literal.string, code .literal.string { color: #0C5404 }
pre.code .name.builtin, code .name.builtin { color: #352B84 }
pre.code .deleted, code .deleted { background-color: #DEB0A1}
pre.code .inserted, code .inserted { background-color: #A3D289}
span.classifier {
font-family: sans-serif ;
font-style: oblique }
span.classifier-delimiter {
font-family: sans-serif ;
font-weight: bold }
span.interpreted {
font-family: sans-serif }
span.option {
white-space: nowrap }
span.pre {
white-space: pre }
span.problematic {
color: red }
span.section-subtitle {
/* font-size relative to parent (h1..h6 element) */
font-size: 80% }
table.citation {
border-left: solid 1px gray;
margin-left: 1px }
table.docinfo {
margin: 2em 4em }
table.docutils {
margin-top: 0.5em ;
margin-bottom: 0.5em }
table.footnote {
border-left: solid 1px black;
margin-left: 1px }
table.docutils td, table.docutils th,
table.docinfo td, table.docinfo th {
padding-left: 0.5em ;
padding-right: 0.5em ;
vertical-align: top }
table.docutils th.field-name, table.docinfo th.docinfo-name {
font-weight: bold ;
text-align: left ;
white-space: nowrap ;
padding-left: 0 }
/* "booktabs" style (no vertical lines) */
table.docutils.booktabs {
border: 0px;
border-top: 2px solid;
border-bottom: 2px solid;
border-collapse: collapse;
}
table.docutils.booktabs * {
border: 0px;
}
table.docutils.booktabs th {
border-bottom: thin solid;
text-align: left;
}
h1 tt.docutils, h2 tt.docutils, h3 tt.docutils,
h4 tt.docutils, h5 tt.docutils, h6 tt.docutils {
font-size: 100% }
ul.auto-toc {
list-style-type: none }
</style>
</head>
<body>
<div class="document" id="python-frequently-asked-question-lists">
<h1 class="title">Python Frequently Asked Question Lists</h1>
<ul class="simple">
<li><a class="reference external" href="faq/general.html">General Python FAQ</a></li>
<li><a class="reference external" href="faq/programming.html">Programming FAQ</a></li>
<li><a class="reference external" href="faq/library.html">Library and Extension FAQ</a></li>
<li><a class="reference external" href="faq/extending.html">Extending/Embedding FAQ</a></li>
<li><a class="reference external" href="faq/windows.html">Windows FAQ</a></li>
<li><a class="reference external" href="faq/gui.html">GUI Programming FAQ</a></li>
<li><a class="reference external" href="faq/installed.html">&quot;Why is Python Installed on my Computer?&quot; FAQ</a></li>
</ul>
<p>This is a local copy of the online FAQ located at
<a class="reference external" href="http://python.org/doc/faq">http://python.org/doc/faq</a>.
The copy was fetched and generated in May 2007.</p>
</div>
</body>
</html>
faq/extending.ht deleted 100644 → 0
+ 0
− 467
View file @ 0e15b321
Title: Python Extending/Embedding FAQ
Content-type: text/x-rst
====================================
Extending/Embedding FAQ
====================================
:Date: $Date: 2004-04-08 09:05:47 -0600 (Thu, 08 Apr 2004) $
:Version: $Revision: 7294 $
:Web site: http://www.python.org/
.. contents::
.. sectnum::
Can I create my own functions in C?
------------------------------------------
Yes, you can create built-in modules containing functions,
variables, exceptions and even new types in C. This is explained in
the document "Extending and Embedding the Python Interpreter" (http://docs.python.org/ext/ext.html).
Most intermediate or advanced Python books will also
cover this topic.
Can I create my own functions in C++?
--------------------------------------------
Yes, using the C compatibility features found in C++.
Place ``extern "C" { ... }`` around the Python include files and put
``extern "C"`` before each function that is going to be called by the
Python interpreter. Global or static C++ objects with constructors
are probably not a good idea.
Writing C is hard; are there any alternatives?
---------------------------------------------------
There are a number of alternatives to writing your own C extensions,
depending on what you're trying to do.
If you need more speed, `Psyco <http://psyco.sourceforge.net/>`_ generates x86 assembly code
from Python bytecode. You can use Psyco to compile the most
time-critical functions in your code, and gain a significant
improvement with very little effort, as long as you're running on a
machine with an x86-compatible processor.
`Pyrex <http://www.cosc.canterbury.ac.nz/~greg/python/Pyrex/>`_ is a compiler that accepts a slightly modified form of Python
and generates the corresponding C code. Pyrex makes it possible to write
an extension without having to learn Python's C API.
If you need to interface to some C library for which no Python
extension currently exists, you can try wrapping the library's data
types and functions with a tool such as `SWIG <http://www.swig.org>`_.
For C++ libraries, you can look at `SIP <http://www.riverbankcomputing.co.uk/sip/>`_, `CXX <http://cxx.sourceforge.net/>`_, `Boost
<http://www.boost.org/libs/python/doc/index.html>`_, or `Weave <http://www.scipy.org/site_content/weave>`_.
How can I execute arbitrary Python statements from C?
------------------------------------------------------------
The highest-level function to do this is ``PyRun_SimpleString()`` which takes
a single string argument to be executed in the context of the module
``__main__`` and returns 0 for success and -1 when an exception occurred
(including ``SyntaxError``). If you want more control, use ``PyRun_String()``;
see the source for ``PyRun_SimpleString()`` in Python/pythonrun.c.
How can I evaluate an arbitrary Python expression from C?
----------------------------------------------------------------
Call the function ``PyRun_String()`` from the previous question with the
start symbol ``Py_eval_input``; it
parses an expression, evaluates it and returns its value.
How do I extract C values from a Python object?
------------------------------------------------------
That depends on the object's type. If it's a tuple,
``PyTupleSize(o)`` returns its length and ``PyTuple_GetItem(o, i)``
returns its i'th item. Lists have similar functions, ``PyListSize(o)``
and ``PyList_GetItem(o, i)``.
For strings, ``PyString_Size(o)`` returns
its length and ``PyString_AsString(o)`` a pointer to its value.
Note that Python strings may contain null bytes so C's ``strlen()``
should not be used.
To test the type of an object, first make sure
it isn't NULL, and then use ``PyString_Check(o)``, ``PyTuple_Check(o)``,
``PyList_Check(o)``, etc.
There is also a high-level API to Python objects which is
provided by the so-called 'abstract' interface -- read
``Include/abstract.h`` for further details. It allows
interfacing with any kind of Python sequence
using calls like ``PySequence_Length()``, ``PySequence_GetItem()``, etc.)
as well as many other useful protocols.
How do I use Py_BuildValue() to create a tuple of arbitrary length?
--------------------------------------------------------------------------
You can't. Use ``t = PyTuple_New(n)`` instead, and fill it with
objects using ``PyTuple_SetItem(t, i, o)`` -- note that this "eats" a
reference count of ``o``, so you have to ``Py_INCREF`` it.
Lists have similar functions ``PyList_New(n)`` and
``PyList_SetItem(l, i, o)``. Note that you *must* set all the tuple items to
some value before you pass the tuple to Python code --
``PyTuple_New(n)`` initializes them to NULL, which isn't a valid Python
value.
How do I call an object's method from C?
-----------------------------------------------
The ``PyObject_CallMethod()`` function can be used to call an arbitrary
method of an object. The parameters are the object, the name of the
method to call, a format string like that used with ``Py_BuildValue()``, and the argument values::
PyObject *
PyObject_CallMethod(PyObject *object, char *method_name,
char *arg_format, ...);
This works for any object that has methods -- whether built-in or
user-defined. You are responsible for eventually ``Py_DECREF``'ing the
return value.
To call, e.g., a file object's "seek" method with arguments 10, 0
(assuming the file object pointer is "f")::
res = PyObject_CallMethod(f, "seek", "(ii)", 10, 0);
if (res == NULL) {
... an exception occurred ...
}
else {
Py_DECREF(res);
}
Note that since ``PyObject_CallObject()`` *always* wants a tuple for the
argument list, to call a function without arguments, pass "()" for the
format, and to call a function with one argument, surround the argument
in parentheses, e.g. "(i)".
How do I catch the output from PyErr_Print() (or anything that prints to stdout/stderr)?
-----------------------------------------------------------------------------------------------
In Python code, define an object that supports the ``write()`` method.
Assign this object to ``sys.stdout`` and ``sys.stderr``.
Call print_error, or just allow the standard traceback mechanism to
work. Then, the output will go wherever your ``write()`` method sends it.
The easiest way to do this is to use the StringIO class in the standard
library.
Sample code and use for catching stdout::
>>> class StdoutCatcher:
... def __init__(self):
... self.data = ''
... def write(self, stuff):
... self.data = self.data + stuff
...
>>> import sys
>>> sys.stdout = StdoutCatcher()
>>> print 'foo'
>>> print 'hello world!'
>>> sys.stderr.write(sys.stdout.data)
foo
hello world!
How do I access a module written in Python from C?
---------------------------------------------------------
You can get a pointer to the module object as follows::
module = PyImport_ImportModule("<modulename>");
If the module hasn't been imported yet (i.e. it is not yet present in
``sys.modules``), this initializes the module; otherwise it simply returns
the value of ``sys.modules["<modulename>"]``. Note that it doesn't enter
the module into any namespace -- it only ensures it has been
initialized and is stored in ``sys.modules``.
You can then access the module's attributes (i.e. any name defined in
the module) as follows::
attr = PyObject_GetAttrString(module, "<attrname>");
Calling ``PyObject_SetAttrString()`` to assign to variables in the module also works.
How do I interface to C++ objects from Python?
------------------------------------------------------
Depending on your requirements, there are many approaches. To do
this manually, begin by reading `the "Extending and Embedding" document <http://docs.python.org/ext/ext.html>`_. Realize
that for the Python run-time system, there isn't a whole lot of
difference between C and C++ -- so the strategy of building a new Python
type around a C structure (pointer) type will also work for C++
objects.
For C++ libraries, you can look at `SIP <http://www.riverbankcomputing.co.uk/sip/>`_, `CXX <http://cxx.sourceforge.net/>`_, `Boost
<http://www.boost.org/libs/python/doc/index.html>`_, or `Weave <http://www.scipy.org/site_content/weave>`_.
`SWIG <http://www.swig.org>`_ is a similar automated tool that only supports C libraries.
I added a module using the Setup file and the make fails; why?
----------------------------------------------------------------------
Setup must end in a newline, if there is no newline there, the build
process fails. (Fixing this requires some ugly shell script hackery,
and this bug is so minor that it doesn't seem worth the effort.)
How do I debug an extension?
------------------------------------
When using GDB with dynamically loaded extensions, you can't set a
breakpoint in your extension until your extension is loaded.
In your ``.gdbinit`` file (or interactively), add the command::
br _PyImport_LoadDynamicModule
Then, when you run GDB::
$ gdb /local/bin/python
gdb) run myscript.py
gdb) continue # repeat until your extension is loaded
gdb) finish # so that your extension is loaded
gdb) br myfunction.c:50
gdb) continue
I want to compile a Python module on my Linux system, but some files are missing. Why?
-------------------------------------------------------------------------------------------------
Most packaged versions of Python don't include the
/usr/lib/python2.x/config/ directory, which contains various files required
for compiling Python extensions.
For Red Hat, install the python-devel RPM to get the necessary files.
For Debian, run ``apt-get install python-dev``.
What does "SystemError: _PyImport_FixupExtension: module yourmodule not loaded" mean?
-------------------------------------------------------------------------------------------------------
This means that you have created an extension module named "yourmodule", but your module init function does not initialize with that name.
Every module init function will have a line similar to::
module = Py_InitModule("yourmodule", yourmodule_functions);
If the string passed to this function is not the same name as your
extenion module, the ``SystemError`` exception will be raised.
How do I tell "incomplete input" from "invalid input"?
--------------------------------------------------------------------------------
Sometimes you want to emulate the Python interactive interpreter's
behavior, where it gives you a continuation prompt when the input
is incomplete (e.g. you typed the start of an "if" statement
or you didn't close your parentheses or triple string quotes),
but it gives you a syntax error message immediately when the input
is invalid.
In Python you can use the ``codeop`` module, which approximates the
parser's behavior sufficiently. IDLE uses this, for example.
The easiest way to do it in C is to call ``PyRun_InteractiveLoop()``
(perhaps in a separate thread) and let the Python interpreter handle
the input for you. You can also set the ``PyOS_ReadlineFunctionPointer``
to point at your custom input function. See ``Modules/readline.c`` and
``Parser/myreadline.c`` for more hints.
However sometimes you have to run the embedded Python interpreter in
the same thread as your rest application and you can't allow the
``PyRun_InteractiveLoop()`` to stop while waiting for user input. The
one solution then is to call ``PyParser_ParseString()`` and test for
``e.error`` equal to ``E_EOF``, which means the input is incomplete).
Here's a sample code fragment, untested, inspired by code from Alex Farber::
#include <Python.h>
#include <node.h>
#include <errcode.h>
#include <grammar.h>
#include <parsetok.h>
#include <compile.h>
int testcomplete(char *code)
/* code should end in \n */
/* return -1 for error, 0 for incomplete, 1 for complete */
{
node *n;
perrdetail e;
n = PyParser_ParseString(code, &_PyParser_Grammar,
Py_file_input, &e);
if (n == NULL) {
if (e.error == E_EOF)
return 0;
return -1;
}
PyNode_Free(n);
return 1;
}
Another solution is trying to compile the received string with
``Py_CompileString()``. If it compiles without errors, try to execute the returned
code object by calling ``PyEval_EvalCode()``. Otherwise save the input for
later. If the compilation fails, find out if it's an error or just
more input is required - by extracting the message string from the
exception tuple and comparing it to the string "unexpected EOF while parsing".
Here is a complete example using the GNU readline library (you may
want to ignore SIGINT while calling readline())::
#include <stdio.h>
#include <readline.h>
#include <Python.h>
#include <object.h>
#include <compile.h>
#include <eval.h>
int main (int argc, char* argv[])
{
int i, j, done = 0; /* lengths of line, code */
char ps1[] = ">>> ";
char ps2[] = "... ";
char *prompt = ps1;
char *msg, *line, *code = NULL;
PyObject *src, *glb, *loc;
PyObject *exc, *val, *trb, *obj, *dum;
Py_Initialize ();
loc = PyDict_New ();
glb = PyDict_New ();
PyDict_SetItemString (glb, "__builtins__", PyEval_GetBuiltins ());
while (!done)
{
line = readline (prompt);
if (NULL == line) /* CTRL-D pressed */
{
done = 1;
}
else
{
i = strlen (line);
if (i > 0)
add_history (line); /* save non-empty lines */
if (NULL == code) /* nothing in code yet */
j = 0;
else
j = strlen (code);
code = realloc (code, i + j + 2);
if (NULL == code) /* out of memory */
exit (1);
if (0 == j) /* code was empty, so */
code[0] = '\0'; /* keep strncat happy */
strncat (code, line, i); /* append line to code */
code[i + j] = '\n'; /* append '\n' to code */
code[i + j + 1] = '\0';
src = Py_CompileString (code, "<stdin>", Py_single_input);
if (NULL != src) /* compiled just fine - */
{
if (ps1 == prompt || /* ">>> " or */
'\n' == code[i + j - 1]) /* "... " and double '\n' */
{ /* so execute it */
dum = PyEval_EvalCode ((PyCodeObject *)src, glb, loc);
Py_XDECREF (dum);
Py_XDECREF (src);
free (code);
code = NULL;
if (PyErr_Occurred ())
PyErr_Print ();
prompt = ps1;
}
} /* syntax error or E_EOF? */
else if (PyErr_ExceptionMatches (PyExc_SyntaxError))
{
PyErr_Fetch (&exc, &val, &trb); /* clears exception! */
if (PyArg_ParseTuple (val, "sO", &msg, &obj) &&
!strcmp (msg, "unexpected EOF while parsing")) /* E_EOF */
{
Py_XDECREF (exc);
Py_XDECREF (val);
Py_XDECREF (trb);
prompt = ps2;
}
else /* some other syntax error */
{
PyErr_Restore (exc, val, trb);
PyErr_Print ();
free (code);
code = NULL;
prompt = ps1;
}
}
else /* some non-syntax error */
{
PyErr_Print ();
free (code);
code = NULL;
prompt = ps1;
}
free (line);
}
}
Py_XDECREF(glb);
Py_XDECREF(loc);
Py_Finalize();
exit(0);
}
How do I find undefined g++ symbols __builtin_new or __pure_virtual?
-----------------------------------------------------------------------------------
To dynamically load g++ extension modules, you must recompile Python, relink it using g++ (change LINKCC in the python Modules Makefile), and link your extension module using g++ (e.g., "g++ -shared -o mymodule.so mymodule.o").
Can I create an object class with some methods implemented in C and others in Python (e.g. through inheritance)?
-----------------------------------------------------------------------------------------------------------------------------------------------------
In Python 2.2, you can inherit from builtin classes such as int, list, dict, etc.
The Boost Python Library (BPL, http://www.boost.org/libs/python/doc/index.html)
provides a way of doing this from C++ (i.e. you can inherit from an
extension class written in C++ using the BPL).
When importing module X, why do I get "undefined symbol: PyUnicodeUCS2*"?
--------------------------------------------------------------------------------------------------
You are using a version of Python that uses a 4-byte representation
for Unicode characters, but some C extension module you are importing
was compiled using a Python that uses a 2-byte representation for
Unicode characters (the default).
If instead the name of the undefined symbol starts with
``PyUnicodeUCS4``, the problem is the reverse: Python was built using
2-byte Unicode characters, and the extension module was compiled using
a Python with 4-byte Unicode characters.
This can easily occur when using pre-built extension packages. RedHat
Linux 7.x, in particular, provided a "python2" binary that is compiled
with 4-byte Unicode. This only causes the link failure if the extension
uses any of the ``PyUnicode_*()`` functions. It is also a problem if an
extension uses any of the Unicode-related format specifiers for
``Py_BuildValue`` (or similar) or parameter specifications for
``PyArg_ParseTuple()``.
You can check the size of the Unicode character a Python interpreter is
using by checking the value of sys.maxunicode::
>>> import sys
>>> if sys.maxunicode > 65535:
... print 'UCS4 build'
... else:
... print 'UCS2 build'
The only way to solve this problem is to use extension modules compiled
with a Python binary built using the same size for Unicode characters.
faq/extending.html deleted 100644 → 0
+ 0
− 793
View file @ 0e15b321
This diff is collapsed.
faq/general.ht deleted 100644 → 0
+ 0
− 1460
View file @ 0e15b321
This diff is collapsed.
faq/general.html deleted 100644 → 0
+ 0
− 1675
View file @ 0e15b321
This diff is collapsed.
faq/gui.ht deleted 100644 → 0
+ 0
− 173
View file @ 0e15b321
This diff is collapsed.
faq/gui.html deleted 100644 → 0
+ 0
− 516
View file @ 0e15b321
This diff is collapsed.
faq/installed.ht deleted 100644 → 0
+ 0
− 61
View file @ 0e15b321
Title: "Why is Python Installed on my Computer?" FAQ
Content-type: text/x-rst
=====================================================
"Why is Python Installed on my Computer?" FAQ
=====================================================
What is Python?
----------------------
Python is a programming language. It's used for many different
applications. It's used in some high schools and colleges as an
introductory programming language because Python is easy to learn, but
it's also used by professional software developers at places such as Google,
NASA, and Industrial Light & Magic.
If you're curious about finding out more about Python, start with the
`Beginner's Guide to Python <http://www.python.org/moin/BeginnersGuide>`_.
Why is Python installed on my machine?
--------------------------------------------------
If you find Python installed on your system but don't remember
installing it, there are several possible ways it could have gotten
there.
* Perhaps another user on the computer wanted to learn programming
and installed it; you'll have to figure out who's been using the machine
and might have installed it.
* A third-party application installed on the machine might have been written
in Python and included a Python installation. For a home computer,
the most common such application is
`PySol <http://www.oberhumer.com/opensource/pysol/>`_,
a solitaire game that includes over 200 different games and variations.
* Some Windows machines also have Python installed. At this writing we're
aware of computers from Hewlett-Packard and Compaq that include Python.
Apparently some of HP/Compaq's administrative tools are written in Python.
* All Apple computers running Mac OS X have Python installed; it's included
in the base installation.
Can I delete Python?
----------------------------
That depends on where Python came from.
If someone installed it deliberately, you can remove it without
hurting anything. On Windows, use the Add/Remove Programs icon in the
Control Panel.
If Python was installed by a third-party application, you can also
remove it, but that application will no longer work. You should probably
use that application's uninstaller rather than removing Python directly.
If Python came with your operating system, removing it is not
recommended. If you remove it, whatever tools were written in Python
will no longer run, and some of them might be important to you.
Reinstalling the whole system would then be required to fix things
again.
faq/installed.html deleted 100644 → 0
+ 0
− 392
View file @ 0e15b321
This diff is collapsed.
faq/library.ht deleted 100644 → 0
+ 0
− 913
View file @ 0e15b321
This diff is collapsed.
faq/library.html deleted 100644 → 0
+ 0
− 1193
View file @ 0e15b321
This diff is collapsed.
faq/programming.ht deleted 100644 → 0
+ 0
− 1756
View file @ 0e15b321
This diff is collapsed.
faq/programming.html deleted 100644 → 0
+ 0
− 2025
View file @ 0e15b321
This diff is collapsed.
faq/windows.ht deleted 100644 → 0
+ 0
− 592
View file @ 0e15b321
This diff is collapsed.
faq/windows.html deleted 100644 → 0
+ 0
− 912
View file @ 0e15b321
This diff is collapsed.
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment
Apertis Website Terms of Use Privacy Policy