Skip to content

Conversation

undingen
Copy link
Contributor

@undingen undingen commented Feb 9, 2016

The socket implementation used to only call close on a socket when all references where gone.
This works fine for cpython which uses reference counting but for pyston (and pypy) this is a problem.
This works around the problem in a similar way as pypy does.
It also uses the same method names so that 3th party libs which already support pypy will automatically work with pyston too.
(e.g. urllib3)

I would prefer if we get ref counting but meanwhile this improves the situation a lot. (While I'm not sure if this does not break other stuff but I would prefer to not spend to much time on this now if it may get replaced soon)

@undingen undingen force-pushed the socket_fixes branch 3 times, most recently from 380d7e7 to c693abf Compare February 10, 2016 16:23
@undingen undingen changed the title [WIP] socket fixes socket fixes Feb 10, 2016
The socket implementation used to only call close on a socket when all references where gone.
This works fine for cpython which uses reference counting but for pyston (and pypy) this is a problem.
This works around the problem in a similar way as pypy does.
It also uses the same method names so that 3th party libs which already support pypy will automatically work with pyston too.
(e.g. urllib3)
kmod added a commit that referenced this pull request Feb 13, 2016
@kmod kmod merged commit 831c8d1 into pyston:master Feb 13, 2016
@kmod
Copy link
Collaborator

kmod commented Feb 13, 2016

Awesome :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants