Re: pyro 4.27 breaks access to __whatever__ methods

On 8-9-2014 10:14, Irmen de Jong wrote:
> 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


The dev version of Pyro now contains a fix for this problem, please check it out if you
can (directly from github master). See the comment on the linked github issue.

I plan to make this an official release in a week or so.


Irmen


------------------------------------------------------------------------------
Slashdot TV.  Video for Nerds.  Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk