3 ms·

> MySQL roll out for our Python software is a complete pain Really? How so?

by lamby 17y ago

Goladus 17y ago
Just taking a guess, but: mysql client must be installed on every machine mysql python bindings must be compiled and deployed on every machine. I imagine it's not uncommon among Python web apps for the mysql library to be the only thing that requires gcc to compile from source. Having a library entirely in python, for which you presumably already have a deployment process, would definitely simplify things.
- thwarted 17y ago
  Does Gentoo really have this level of penetration? How did you get python on the machine in the first place? Any distribution worth using for LAMP already provides everything you need for a base install for this already compiled and packaged. Pure <your favorite language> implementations are useful from a portability, testing/verification, and avoiding vendor lock-in perspective, but the problem of "How do I get the libraries I need on all the machines" has long since been solved. In fact, using a packaging system like dpkg or rpm will make it easy to determine if you're missing anything, since they can list everything that is installed via packages.
  - Goladus 17y ago
    The last time I checked, Solaris blastwave didn't have a mysql database interface package for Python. I don't know what OS ErrantX is using. He claims that the package provided is unreliable.
ErrantX 17y ago
As Goladus says it adds a whole list of pre-requisites and a compile stage when installing software. Windows isnt too bad because there is Windows binaries that do work ok. But on Linux the current offerings of MySQL in Python have always been a bit shaky.
- lamby 17y ago
  What's wrong the versions from your distribution's package manager?
  - ErrantX 17y ago
    50% of the time (at least) it doesn't work right. It's an incredibly fickle set up. For an end point software package it's a little too unreliable for us to, well, rely on :)

> MySQL roll out for our Python software is a complete pain Really? How so?

by lamby 17y ago

> MySQL roll out for our Python software is a complete pain Really? How so?

Just taking a guess, but: mysql client must be installed on every machine mysql python bindings must be compiled and deployed on every machine. I imagine it's not uncommon among Python web apps for the mysql library to be the only thing that requires gcc to compile from source. Having a library entirely in python, for which you presumably already have a deployment process, would definitely simplify things.

thwarted 17y ago
Does Gentoo really have this level of penetration? How did you get python on the machine in the first place? Any distribution worth using for LAMP already provides everything you need for a base install for this already compiled and packaged. Pure <your favorite language> implementations are useful from a portability, testing/verification, and avoiding vendor lock-in perspective, but the problem of "How do I get the libraries I need on all the machines" has long since been solved. In fact, using a packaging system like dpkg or rpm will make it easy to determine if you're missing anything, since they can list everything that is installed via packages.
- Goladus 17y ago
  The last time I checked, Solaris blastwave didn't have a mysql database interface package for Python. I don't know what OS ErrantX is using. He claims that the package provided is unreliable.

ErrantX 17y ago

As Goladus says it adds a whole list of pre-requisites and a compile stage when installing software. Windows isnt too bad because there is Windows binaries that do work ok. But on Linux the current offerings of MySQL in Python have always been a bit shaky.

lamby 17y ago
What's wrong the versions from your distribution's package manager?
- ErrantX 17y ago
  50% of the time (at least) it doesn't work right. It's an incredibly fickle set up. For an end point software package it's a little too unreliable for us to, well, rely on :)