Name Last modified Size Description
cgi-bin 31-Jul-2004 01:18 - img 14-May-2005 20:09 - mivatest 04-Aug-2005 22:29 - listings 07-Mar-2006 20:17 - Merchant 20-Jun-2007 17:52 - _mgxftp 14-Aug-2007 14:59 - _mgxroot 14-Aug-2007 15:00 - phpads 15-Mar-2010 22:36 - __MACOSX 11-Mar-2011 01:33 - newcalendar 25-Feb-2013 08:21 - calendar 26-Feb-2013 08:14 - smartphpcalendar 26-Feb-2013 08:14 - phpwiki 15-Oct-2016 12:10 - test 15-Oct-2016 12:10 - gallery_old 16-Oct-2016 00:41 - wdCalendar 21-Oct-2016 03:42 - baby-rewards.com 01-Jan-2018 21:17 - webtradeproltd.com 01-Jan-2018 21:18 - cm 02-Jan-2018 06:39 - WebCalendar-1.2.5 03-Jan-2018 13:12 - rss.php 31-Jul-2005 18:33 12k test.wmv 18-Aug-2005 18:25 0k linttylog-1.00-0.i386.rpm 20-Dec-2005 19:28 16k BIMPLiteConfig.bat 14-Aug-2007 14:59 4k phpinfo.php 13-Sep-2008 22:54 4k calendar.zip 04-Oct-2011 20:24 392k WebCalendar-1.2.5.tar.gz.1 29-Feb-2012 18:25 1340k WebCalendar-1.2.5.tar.gz 29-Feb-2012 18:25 1340k error_log 21-Feb-2020 05:14 2116k
The setup.py script uses mysql_config to find all compiler and linker options, and should work as is on any POSIX-like platform, so long as mysql_config is in your path.
Depending on which version of MySQL you have, you may have the option of using three different client libraries:
mysqlclient_r is used by default. To use one of the others, set the environment variable mysqlclient to the name of the library you want to use. In a Bourne-style shell, use:
$ export mysqlclient=mysqlclient
Only do this if you don't have the thread-safe library (mysqlclient_r) or you want to use the embedded server (mysqld).
Finally, putting it together:
$ tar xfz MySQL-python-1.1.10.tar.gz $ cd MySQL-python-1.1.10 $ python setup.py build $ su # or use sudo # python setup.py install
NOTE: You must export environment variables for setup.py to see them. Depending on what shell you prefer, you may need to use "export" or "set -x" (bash and other Bourne-like shells) or "setenv" (csh-like shells).
I don't do Windows. However if someone provides me with a package for Windows, I'll make it available. Don't ask me for help with Windows because I can't help you.
Generally, though, running setup.py is similar to above:
C:\...> python setup.py install C:\...> python setup.py bdist_wininst
The latter example should build a Windows installer package, if you have the correct tools. In any event, you must have a C compiler. Additionally, you have to set an environment variable (mysqlroot) which is the path to your MySQL installation. In theory, it would be possible to get this information out of the registry, but like I said, I don't do Windows, but I'll accept a patch that does this.
If you are using a binary package of Zope, you need run setup.py with the python executable that came with Zope. Otherwise, you'll install into the wrong Python tree and Zope (ZMySQLDA) will not be able to find _mysql.
With zope.org's Zope-2.5.1-linux2-x86 binary tarball, you'd do something like this:
$ export ZOPEBIN=".../Zope-2.5.1-linux2-x86/bin" # wherever you unpacked it $ $ZOPEBIN/python setup.py install # builds and installs
I don't plan to make binary packages any more. However, if someone contributes one, I will make it available. Several OS vendors have their own packages available.
If you prefer to install RPMs, you can use the bdist_rpm command with setup.py. This only builds the RPM; it does not install it. You may want to use the --python=XXX option, where XXX is the name of the Python executable, i.e. python, python2, python2.1; the default is python. Using this will incorporate the Python executable name into the package name for the RPM so you have install the package multiple times if you need to support more than one version of Python.
MySQL-python is pre-packaged in Red Hat Linux 7.x and newer. This likely includes Fedora Core and Red Hat Enterprise Linux. You can also build your own RPM packages as described above.
Packaged as mysql-python. Gentoo is also my development platform:
# emerge sync # emerge mysql-python # emerge zmysqlda # if you use Zope
MySQL-python is a ported package in FreeBSD, NetBSD, and OpenBSD, although the name may vary to match OS conventions.