m [mailto:users-
boun...@lists.ironpython.com] On Behalf Of Zachary Gramana
Sent: Tuesday, May 17, 2011 3:38 PM
To: Discussion of IronPython
Subject: Re: [IronPython] socket, _socket, and socket.py
I noticed this, with a little disappointment. I also noticed that they
implemented a sort of ersatz/pl
s.ironpython.com [mailto:
> users-boun...@lists.ironpython.com] *On Behalf Of *Curt Hagenlocher
> *Sent:* Tuesday, May 17, 2011 2:59 PM
> *To:* Discussion of IronPython
> *Subject:* Re: [IronPython] socket, _socket, and socket.py
>
>
>
> Originally, we weren't allowed to redi
17, 2011 3:38 PM
> To: Discussion of IronPython
> Subject: Re: [IronPython] socket, _socket, and socket.py
>
> I noticed this, with a little disappointment. I also noticed that they
> implemented a sort of ersatz/platform agnostic reference tracking system in
> ssl.py. Seei
I noticed this, with a little disappointment. I also noticed that they
implemented a sort of ersatz/platform agnostic reference tracking system
in ssl.py. Seeing the _makefile_refs system got me thinking about the
whole ssl.py/_ssl.pyd paradigm and sockets.cs, since I remembered you
tackled th
Thanks Curt. That's encouraging news to hear.
I've noticed that some Python projects have a dependency on being able
to standard library methods and types. For example, Mercurial replaces
buffer() with their own fakebuffer(), but ipy socket reads still return
the original buffer. I ended up
looks like Jython also has a custom
socket.py.
From: users-boun...@lists.ironpython.com
[mailto:users-boun...@lists.ironpython.com] On Behalf Of Curt Hagenlocher
Sent: Tuesday, May 17, 2011 2:59 PM
To: Discussion of IronPython
Subject: Re: [IronPython] socket, _socket, and socket.py
Originally,
Originally, we weren't allowed to redistribute the Python standard library
with IronPython. So it made sense to implement the socket module directly.
When IronPython started shipping the standard lib, it could have been
changed, but never was. I think it makes sense to follow the CPython
pattern.
Hi:
I've been working on adapting Mercurial to run on IronPython 2.7, and
ran into http://ironpython.codeplex.com/workitem/26852 which has stopped
me from getting `hg clone` working over SSL.
I noticed that for the ssl module, the IPY team mirrored the CPython
pattern of placing the platform