Hello,
If I understand correctly, Zooba (on the Python Tools for Visual Studio
team at Microsoft) suggested that IronPython isn't emitting proper
debugging information so that the CLR debugger can find the correct lines
of source code. Please see this thread:
https://pytools.codeplex.com/workitem
Hi Alex,
Yup I can do that. I also have a fix for translate issue 27904
I ran the test_bytes.py just to make sure I notice it was failing. In the
test_zzz_cli_features had this
AreEqual(bytearray(b'abc') == 'abc', False)
had to change to
AreEqual(bytearray(b'abc') == 'abc', True)
test_translat
Can you fork on github and provide a merge request?
On Mon, Aug 18, 2014 at 1:50 PM, Daniel Fernandez <
fernandez_d...@hotmail.com> wrote:
> HI All,
>
> Thanks Alex that was a duh moment for me there.
>
> I see the issue the code use the as the operator trying to convert to
> IList. I simple che
HI All,
Thanks Alex that was a duh moment for me there.
I see the issue the code use the as the operator trying to convert to
IList. I simple check if the type is string then convert it to bytes. It
works now
Here is the snippet
public override bool Equals(object other) {IList bytes
Is there any debugger that allows stepping from IronPython to C# to C++? I
tried just adding "import pdb; pdb.set_trace()" and running with "ipy64
-X:Tracing -X:FullFrames", but attempting to step into a C# function just
stepped right over it.
It seems that the PTVS debugger can't handle this eit
ByteArray.cs the Equals method.
On Mon, Aug 18, 2014 at 11:50 AM, Daniel Fernandez <
fernandez_d...@hotmail.com> wrote:
> Hi All,
>
> I ran into an issue comparing bytearray with a string value. I created an
> issue 35470 on codeplex. The code snippet that can reproduce the issue is
> x = bytear
Hi All,
I ran into an issue comparing bytearray with a string value. I created an issue
35470 on codeplex. The code snippet that can reproduce the issue isx =
bytearray(b'Danny')y = 'Danny'x == y
IronPython 2.7.5b3 this is False and CPython 2.7.8 is True.
My question is where in the IronPython c
I agree, I think we need to determine the best way to implement this so we
match CPython more. I think if we just patch the stdlib though, we may run
into other cases in the future that we would need to fix, but if we
determine how to make it work inside IronPython, it would be better.
On Mon, Au
I personally vote for as close to cpython as possible. This is based on
porting experience with python packages. It is really a lot of effort
effort to find the places where it trips in other packages, get the 'if'
around it and get it accepted upstream.
This appears to fix it:
https://github.com/p
Hi ironpython,
Here's your Daily Digest of new issues for project "IronPython".
In today's digest:ISSUES
1. [New comment] Remove obsolete APIs after IronPython 2.6 ships
2. [New comment] socket.getnameinfo(("127.0.0.1", ...), ) broken on
machines with multiple network connections
3. [New c
10 matches
Mail list logo