-
Notifications
You must be signed in to change notification settings - Fork 644
ImportError: no such module: socket #299
Comments
From gitter it sounds like this is resolved with: export GOPATH=$PWD/build |
Ah, I see this issue has been updated. Re-opening until socket module is supported. |
Hi, I have add "grumpy" package into Conda2.7 site packages =)
but it didn't helps, so I've backed to README and set PYTHONPATH to grumpi site-packages location
Any thoughts how I can convert code to Go? Or I should wait for request lib to be added to supported list... |
any ETA when the ImportError - no such module: socket will be resolved? |
Heh... The roadmap says "stdlib on July 2017", but I only see it happening if more people put hands on. (What I mean is: please help if you can) |
Yeah, we need more people to work on this project with concrete load map. |
My sense is that a big part of the difficulty in recruiting contributions to this project is because it focuses on legacy Python at a time when zero percent of the Python community innovation is going into Python 2.7. Focusing on transpiling Python 2.7 when everyone else is working towards Python 3.7 is only a setup for a series of efforts to catch up to the current state of the art. |
@cclaus I still need working stuff to keep working, but a working Py27 can be a trampoline for a working Py3X. Would it gain more traction if the roadmap have one more point "Py3k Compliance" over the existing ones? (honest question) |
Just a quick update on socket functionality: I have a rough working socket module here: trotterdylan@a3ead81 Based on that work, BaseHTTPServer works as expected, which is a good sign. There's a bunch of different parts that went into this and I need to break them out into individual PRs, which I'll do over the next week or two. |
@alanjds in answer to your question on May 26th... I say the answer is yes |
@alanjds what about @trotterdylan 's code changes? was the socket library not added? |
@JockDaRock I am not tracking this specifically. I am focused on #223 (print statement misbehaviour), that leads to PRs #302 #303 #304 for now. |
@cclauss Btw, Python 3 support is on the roadmap. Was added some months ago. |
Did anything ever happen with this? |
Also, is there and update on https://github.com/google/grumpy/wiki/Roadmap ? |
@cclaus We are near to stale, in my opinion. In last 10 months 20+ PRs were merged, but just one of it in the last 6 months. Talking for myself, I do think it is hard to contribute because Python modules need Go tests to count for coverage. I was working on this but stopped to wait Go 1.10 and had not got back after. Another thing hindering my progress is the organization of the internal tooling. Is not usable/testable/importable outside of the build folder and environment. I am working on this to have a pip-installable I do think that, after this two got fixed and PEP-3147 got implemented, there could be an speedup on the development because of ease of installing and testing for newcomers. |
I still think is possible to met the "Whole CPython unit test suite runs without errors (goal: Sept 2017)" before Nov 2018 or faster, because of the progress I got on the CLI and PEP-3147 on the last few weeks. For myself, the trick was to set an Android development environment. Now I do had coded about 1:30 hours per day during subway commuting 👍. Weird, but it's how I am rolling it. |
How do I get past this error:
I"m trying to transpile python to Go code on Fedora 25
The text was updated successfully, but these errors were encountered: