In 2.3 the handling of elements in OSA classes was 
revamped, so that accessing an element would cause an 
object of the right type (the Python class handling the OSA 
class for the element) was returned, but this wasn't done for 
properties. So at the moment it is possible to say 
"finder.get(finder.window(0).name)", but not 
"finder.get(finder.desktop.url)".

This seriously hampers the usefulness of the OSA stuff in 
some cases.

The docs say that development for the MacPython OSA modules has stopped,
and that a replacement is expected for Python 2.5.

Can this issue now be closed, or at least have its priority downgraded?

The module is stagnant ("Development on this set of modules has
stopped"), but the docs (for 2.6!) still claim " and a replacement is
expected for Python 2.5".

http://www.python.org/doc/2.6/library/macosa.html

I've attached a patch to remove "a replacement is expected for Python 
2.5".

All that is needed is the doc patch to be applied and the issue closed.  Or have I missed something?

Suggest a different wording to reflect that the 3rd-party appscript package has become the de facto standard for AppleScript support, so something like:

-stopped, and a replacement is expected for Python 2.5.
+stopped. For more up-to-date implementation of AppleScript support for Python, see the third-party py-appscript project: http://pypi.python.org/pypi/appscript/

I've applied the documentation patch that Ned suggests in r

I'm furthermore closing this issue as "Won't Fix" because the OSA bindings are no longer developed and we'll therefore not implement the new feature that Jack mentions.

Sent the message too soon... the documentation update is in r85069.