<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Python 2.0c1 on Python One</title><link>https://tamnd.github.io/python-one/docs/2.0c1/</link><description>Recent content in Python 2.0c1 on Python One</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://tamnd.github.io/python-one/docs/2.0c1/index.xml" rel="self" type="application/rss+xml"/><item><title>Tutorial</title><link>https://tamnd.github.io/python-one/docs/2.0c1/tutorial/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tamnd.github.io/python-one/docs/2.0c1/tutorial/</guid><description>&lt;h1 id="whetting-your-appetite"&gt;Whetting Your Appetite&lt;a class="anchor" href="#whetting-your-appetite"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;If you ever wrote a large shell script, you probably know this feeling: you’d love to add yet another feature, but it’s already so slow, and so big, and so complicated; or the feature involves a system call or other function that is only accessible from C …Usually the problem at hand isn’t serious enough to warrant rewriting the script in C; perhaps the problem requires variable-length strings or other data types (like sorted lists of file names) that are easy in the shell but lots of work to implement in C, or perhaps you’re not sufficiently familiar with C.&lt;/p&gt;</description></item><item><title>Library Reference</title><link>https://tamnd.github.io/python-one/docs/2.0c1/library/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tamnd.github.io/python-one/docs/2.0c1/library/</guid><description>&lt;h1 id="aifc--read-and-write-aiff-and-aifc-files"&gt;&lt;code&gt;aifc&lt;/code&gt; — Read and write AIFF and AIFC files&lt;a class="anchor" href="#aifc--read-and-write-aiff-and-aifc-files"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;&lt;em&gt;Read and write audio files in AIFF or AIFC format.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;This module provides support for reading and writing AIFF and AIFF-C files. AIFF is Audio Interchange File Format, a format for storing digital audio samples in a file. AIFF-C is a newer version of the format that includes the ability to compress the audio data.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Caveat:&lt;/strong&gt; Some operations may only work under IRIX; these will raise &lt;code&gt;ImportError&lt;/code&gt; when attempting to import the &lt;code&gt;cl&lt;/code&gt; module, which is only available on IRIX.&lt;/p&gt;</description></item><item><title>Language Reference</title><link>https://tamnd.github.io/python-one/docs/2.0c1/reference/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tamnd.github.io/python-one/docs/2.0c1/reference/</guid><description>&lt;h1 id="introduction"&gt;Introduction&lt;a class="anchor" href="#introduction"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;This reference manual describes the Python programming language. It is not intended as a tutorial.&lt;/p&gt;
&lt;p&gt;While I am trying to be as precise as possible, I chose to use English rather than formal specifications for everything except syntax and lexical analysis. This should make the document more understandable to the average reader, but will leave room for ambiguities. Consequently, if you were coming from Mars and tried to re-implement Python from this document alone, you might have to guess things and in fact you would probably end up implementing quite a different language. On the other hand, if you are using Python and wonder what the precise rules about a particular area of the language are, you should definitely be able to find them here. If you would like to see a more formal definition of the language, maybe you could volunteer your time — or invent a cloning machine :-).&lt;/p&gt;</description></item><item><title>Extending and Embedding</title><link>https://tamnd.github.io/python-one/docs/2.0c1/extending/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tamnd.github.io/python-one/docs/2.0c1/extending/</guid><description>&lt;p&gt;&lt;strong&gt;Acknowledgements&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;The following people have contributed sections to this document: Jim Fulton, Konrad Hinsen, Chris Phoenix, and Neil Schemenauer.&lt;/p&gt;
&lt;h1 id="extending-python-with-c-or-c"&gt;Extending Python with C or C++&lt;a class="anchor" href="#extending-python-with-c-or-c"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;It is quite easy to add new built-in modules to Python, if you know how to program in C. Such &lt;em&gt;extension modules&lt;/em&gt; can do two things that can’t be done directly in Python: they can implement new built-in object types, and they can call C library functions and system calls.&lt;/p&gt;</description></item><item><title>Python/C API</title><link>https://tamnd.github.io/python-one/docs/2.0c1/api/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tamnd.github.io/python-one/docs/2.0c1/api/</guid><description>&lt;h1 id="introduction"&gt;Introduction&lt;a class="anchor" href="#introduction"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;The Application Programmer’s Interface to Python gives C and C++ programmers access to the Python interpreter at a variety of levels. The API is equally usable from C++, but for brevity it is generally referred to as the Python/C API. There are two fundamentally different reasons for using the Python/C API. The first reason is to write &lt;em&gt;extension modules&lt;/em&gt; for specific purposes; these are C modules that extend the Python interpreter. This is probably the most common use. The second reason is to use Python as a component in a larger application; this technique is generally referred to as &lt;em&gt;embedding&lt;/em&gt; Python in an application.&lt;/p&gt;</description></item><item><title>Installing Python Modules</title><link>https://tamnd.github.io/python-one/docs/2.0c1/installing/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tamnd.github.io/python-one/docs/2.0c1/installing/</guid><description>&lt;h1 id="introduction"&gt;Introduction&lt;a class="anchor" href="#introduction"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Although Python’s extensive standard library covers many programming needs, there often comes a time when you need to add some new functionality to your Python installation in the form of third-party modules. This might be necessary to support your own programming, or to support an application that you want to use and that happens to be written in Python.&lt;/p&gt;
&lt;p&gt;In the past, there has been little support for adding third-party modules to an existing Python installation. With the introduction of the Python Distribution Utilities (Distutils for short) in Python 2.0, this is starting to change. Not everything will change overnight, though, so while this document concentrates on installing module distributions that use the Distutils, we will also spend some time dealing with the old ways.&lt;/p&gt;</description></item><item><title>Distributing Python Modules</title><link>https://tamnd.github.io/python-one/docs/2.0c1/distributing/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tamnd.github.io/python-one/docs/2.0c1/distributing/</guid><description>&lt;h1 id="introduction"&gt;Introduction&lt;a class="anchor" href="#introduction"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;In the past, Python module developers have not had much infrastructure support for distributing modules, nor have Python users had much support for installing and maintaining third-party modules. With the introduction of the Python Distribution Utilities (Distutils for short) in Python 1.6, this situation should start to improve.&lt;/p&gt;
&lt;p&gt;This document only covers using the Distutils to distribute your Python modules. Using the Distutils does not tie you to Python 1.6, though: the Distutils work just fine with Python 1.5.2, and it is reasonable (and expected to become commonplace) to expect users of Python 1.5.2 to download and install the Distutils separately before they can install your modules. Python 1.6 (or later) users, of course, won’t have to add anything to their Python installation in order to use the Distutils to install third-party modules.&lt;/p&gt;</description></item><item><title>Macintosh Library Modules</title><link>https://tamnd.github.io/python-one/docs/2.0c1/macintosh/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tamnd.github.io/python-one/docs/2.0c1/macintosh/</guid><description>&lt;h1 id="introduction"&gt;Introduction&lt;a class="anchor" href="#introduction"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;The modules in this manual are available on the Apple Macintosh only.&lt;/p&gt;
&lt;p&gt;Aside from the modules described here there are also interfaces to various MacOS toolboxes, which are currently not extensively described. The toolboxes for which modules exist are: &lt;code&gt;AE&lt;/code&gt; (Apple Events), &lt;code&gt;Cm&lt;/code&gt; (Component Manager), &lt;code&gt;Ctl&lt;/code&gt; (Control Manager), &lt;code&gt;Dlg&lt;/code&gt; (Dialog Manager), &lt;code&gt;Evt&lt;/code&gt; (Event Manager), &lt;code&gt;Fm&lt;/code&gt; (Font Manager), &lt;code&gt;List&lt;/code&gt; (List Manager), &lt;code&gt;Menu&lt;/code&gt; (Moenu Manager), &lt;code&gt;Qd&lt;/code&gt; (QuickDraw), &lt;code&gt;Qt&lt;/code&gt; (QuickTime), &lt;code&gt;Res&lt;/code&gt; (Resource Manager and Handles), &lt;code&gt;Scrap&lt;/code&gt; (Scrap Manager), &lt;code&gt;Snd&lt;/code&gt; (Sound Manager), &lt;code&gt;TE&lt;/code&gt; (TextEdit), &lt;code&gt;Waste&lt;/code&gt; (non-Apple &lt;strong&gt;TextEdit&lt;/strong&gt; replacement) and &lt;code&gt;Win&lt;/code&gt; (Window Manager).&lt;/p&gt;</description></item></channel></rss>