Hi, Dino,
Von: Dino Viehland [mailto:di...@microsoft.com]
> So you want to warn if the file contains a print statement w/o from
> __future__ import print_function? What if it's a call to print such as
> print('foo') which is valid in both 2.x and 3.x?
Considering our user base, I could ignore
The clr.Convert(TransparentProxy, IServerInterface) is failing with same
exception
I will code a C# wrapper but what does it mean? A client side assembly
that will get the transparent proxy and convert it to the Interface type
I need?
Tsahi Muyal
Corporate Platform Group(CPG)
KLA-Tencor Isr
The C# wrapper could be as simple as:
public static class MyWrapper {
public static void IServerInterfaceMethod(object o) {
((IServerInterface)o).IServerInterfaceMethod();
}
}
Used like:
MyWrapper.IServerInterfaceMethod(TransparentP
I tried using typedproxy class
Not sure I am using it the right way
This is what I did
test = typedproxy(TransparentProxy, IServerInterface)
test.IServerInterfaceMethod()
This call is failing with "Expected IServerInterface, got
MarshalByRefObject"
I debugged the code to find o
Hurm, maybe this is a different problem then... Does:
import clr
clr.Convert(TransparentProxy, IServerInterface).IServerInterfaceMethod()
work?
If not then my guess is you might need a C# wrapper :(
From: Muyal,Tsahi [mailto:tsahi.mu...@kla-tencor.com]
Sent: Tuesday, October 11, 2011 2:39 PM
T
I'm not quite certain this is the same issue but you should try using the
wrapper from this thread:
http://lists.ironpython.com/pipermail/users-ironpython.com/2006-September/003549.html
The transparent proxies always succeed when casting them to an interface type
so it's hard for us to work w/
Hi,
I am trying to call our .NET service via remoting using IronPython
I have the transparent proxy object but I don't know how to cast it to
the interfaces (that are implemented by the server side object)
I tried IServerInterface.SomeMethod(transparent-proxy-object) but it is
failing with "
So you want to warn if the file contains a print statement w/o from __future__
import print_function? What if it's a call to print such as print('foo')
which is valid in both 2.x and 3.x?
Either way you should be able to just update ParsePrintStmt in Parser.cs.
But dealing w/ the case of t
I think you'd have to patch the code to add the print check to the -3
warnings. Dino might be able to point out where you would do that.
- Jeff
On Tue, Oct 11, 2011 at 9:13 AM, Markus Schaber
wrote:
> Hi,
>
> What is the easiest way to detect and warn the user when he uses the old
> print synta
Hi,
What is the easiest way to detect and warn the user when he uses the old print
syntax?
It seems that "-3" aka "WarnPy3k" does not warn about it, and a simple check
whether the user does "from __future__ import print_function" gives false
positives if the user does not print at all.
Thanks
Hi ironpython,
Here's your Daily Digest of new issues for project "IronPython".
In today's digest:ISSUES
1. [New comment] Implement _elementtree module
2. [New comment] ValueError: unmarshallable object
3. [New comment] 'x'.replace(u'\uFFFE','') -> ValueError
4. [New comment] print u'\xe4'.encod
11 matches
Mail list logo
