clarify examples/*py with explicit imports

[jek]

"trw: It would make the examples a lot easier for me (a complete newbie) to read if you would not use "import *", but instead listed out the functions you are importing. For example, looking at http://www.sqlalchemy.org/trac/browser/sqlalchemy/trunk/examples/sharding/attribute_shard.py , I can't easily tell where to find "mapper". I can find it by searching through http://www.sqlalchemy.org/docs/04/docstrings.html , but I wish I could just find its full"

This would help solidify the seperation of concerns in the sql / orm layers too. Also, if this gets done, run pyflakes on all of these to check for cruft.

[Former user]

Import, save(), clear() updates

[Former user]

Here's a patch. There are still some examples that don't run on 0.5/trunk. -Adam Lowry

[Former user]

Failures on: examples/pickle/custom_pickler.py examples/polymorph/polymorph.py examples/polymorph/single.py examples/vertical/dictlike-polymorphic

And a SADeprecationWarning ono examples/elementree/pickle.py

[Former user]

Updated patch with updates to examples/polymorph

[Michael Trier]

Corrected in 6010afb28f95c7050ca48ddd2e6f65ca6cbae5a1. Thanks Adam Lowry!!

[Mike Bayer]

Removing milestone: 0.5.4 (automated comment)