pyro 4.27 breaks access to __whatever__ methods

Irmen de Jong <[email protected]> Mon, 08 Sep 2014 10:14:55 +0200
Newsgroups gmane.comp.python.pyro
Message-ID <[email protected]>
Hi,

I think I made a mistake in the last Pyro version by considering every method starting
with _ or __ a private method. But Python itself treats "dunder" methods differently
(not private!). This means that in 4.27 it is no longer possible to access remote
methods named "__method__".

Note that the same problem already existed in the previous Pyro version (4.26) if you
enabled DOTTEDNAMES.

This is unintentional and I'm planning to fix this for 4.28. If your code depends on
remote double-underscore method names, please wait with upgrading Pyro until the next
release.  Note that an exception will be made only for the double-underscore methods,
any other method starting with an underscore will still be treated as private and
inaccessible.


https://github.com/irmen/Pyro4/issues/57


Irmen



------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk