issues to address before 2.0 final

Greetings, beloved PyDO minority --

There are a couple of things I wish PyDO 2.0 did that they don't, and
could use some input from intrepid persons, preferably ones smarter
than me.

  1. Oracle introspection.  There is a patch for this which probably
     needs a little work on the berlios tracker.

  2. Better pickle support for dynamically created classes
     (projections, classes created by autoschema).  They should
     (un)pickle fine if they are module attributes *and* if their own
     __module__ attribute matches the module; that isn't the case
     right now.  If I added an optional "module" parameter to both
     project and autoschema, I could populate the module
     correspondingly and fix the __module__ attribute; but perhaps
     someone has a better idea for how to address the problem?
     Thoughts appreciated!

Cheers,

js

-- 
Jacob Smullyan

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDakN7uqamFyFXXLIRAn6BAKCXeU4x4w22eEErgwTlEulvvzu2MQCeK2n8
jcvuDGNC/64Z+f0Kt/LvATE=
=6o+e
-----END PGP SIGNATURE-----