<h1>Linux RPMs for Python 2.1.2</h1>

<p>Made available by Sean Reifschneider.

<p><ul><li>Source:

<ul>

<li><a href="/ftp/python/2.1.2/rpms/python2.1-2.1.2-1.src.rpm"> python2.1-2.1.2-1.src.rpm</a>

<li><a href="/ftp/python/2.1/expat-1.1-4tummy.src.rpm"> expat-1.1-4tummy.src.rpm</a> (Needed for building Python SRPM, for systems that don't provide expat-devel)

</ul>

<li>Binary for RedHat-7.1-based systems:

<ul> <li><a href="/ftp/python/2.1.2/rpms/python2.1-2.1.2-1.i386.rpm"> python2.1-2.1.2-1.i386.rpm</a> (RedHat-based 7.1 base RPM)

<li><a href="/ftp/python/2.1.2/rpms/python2.1-tkinter-2.1.2-1.i386.rpm"> python2.1-tkinter-2.1.2-1.i386.rpm</a> (RedHat-based 7.1 tkinter RPM)

<li><a href="/ftp/python/2.1.2/rpms/python2.1-devel-2.1.2-1.i386.rpm"> python2.1-devel-2.1.2-1.i386.rpm</a> (RedHat-based 7.1 development RPM)

<li><a href="/ftp/python/2.1.2/rpms/python2.1-tools-2.1.2-1.i386.rpm"> python2.1-tools-2.1.2-1.i386.rpm</a> (RedHat-based 7.1 Tools RPM, including IDLE) </ul>

</ul>

<p>Shy of RPMs because of library or other dependancy problems with most of the RPMs you pick up? The cure, in my experience is to pick up an SRPM (Source RPM). All you need to do to build a binary package tailored to your system is run

<pre> rpm --rebuild &lt;packagename>.src.rpm</pre>

Note: this does not actually install &lt;packagename&gt;. The end products (.rpm files as indicated by the "Wrote:" stdout lines) must be subsequently installed with rpm -U or the equivalent.