mysql appears to use (and report !) int for booleans,
which is visible to users.
(e.g.  db.myclass.get(id, bool_prop))

The layer above should make sure the same types are
reported no matter the backend.

We can't return Boolean type values from the hyperdb without breaking Python 2.1 compatibility.

If there's some user-level problem that might be addressed, please give some specifics.

I'm not suggesting the returned value should have the python boolean type.
Rather, I'm saying that the hyperdb should return the same type, no matter
the backend.

roundup requires python 2.3 since version 0.8b3.  compatibility with python 2.1 is not an issue.

Ahah! I knew I should've checked before I posted that ;)

Stefan: I'm still a little confused as to exactly what you're observing.

Let me quote the person who send me the bug originally:

"The MySQL backend returns "int" values for boolean properties, while the
AnyDBM backend returns "bool" values.  For example:

  db.myclass.get(id, bool_prop)

will have different types depending on the back ends, at least in our
version of Roundup.  That seems undesirable; returning bool values
everywhere would make more sense."

HTH,
     Stefan