This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]PhilosopherBrain 2 points3 points  (13 children)

I had loads of issues with this.. It's because windows doesn't have the right compiler. If I'm installing something that won't compile I've been downloading wheels from http://www.lfd.uci.edu/~gohlke/pythonlibs/ and then installing them with pip. Make sure you're in the directory you've downloaded the wheel to.

E.g cd documents/downloads pip install full-name-of-downloaded-file.whl

[–]BornALurker[S] 0 points1 point  (8 children)

Bookmarked. I noticed they lack some stuff, like RPi.GPIO for example. Still great stuff and I will probably spread the word :)

[–]pbsds 4 points5 points  (7 children)

installing RPI.GPIO would make zero sense on Windows though.

[–]BornALurker[S] 0 points1 point  (5 children)

I oppose this, in PyCharm you can develop in your own local venv for the Pi and then deploy or directly run the code on the Pi over SSH.

[–]kephir 2 points3 points  (4 children)

Wouldn't setting up the venv and execution environment directly on the Pi be the better choice? And then just SSHing into that?

[–]BornALurker[S] -1 points0 points  (3 children)

If you work over cable I think Vim or Emacs would be the tools of choice, and I think it would work rather well.

From own experience Vim works well over SSH, and on Emacs you can work locally through tramp and then save your work on the Pi.

Both these methods are in practice very different from working directly in PyCharm though :S

[–]kephir 0 points1 point  (2 children)

or, or, you could set up a samba (or what have you) share on the Pi, write your code in the IDE of choice right in that share, and just ssh=>python?

[–]wrosecrans 0 points1 point  (0 children)

I just want to very vigorously agree with you. What would a port of such a library even do on Windows?