{"action":"created","issue":{"url":"https://api.github.com/repos/torebutlin/cued_datalogger/issues/11","repository_url":"https://api.github.com/repos/torebutlin/cued_datalogger","labels_url":"https://api.github.com/repos/torebutlin/cued_datalogger/issues/11/labels{/name}","comments_url":"https://api.github.com/repos/torebutlin/cued_datalogger/issues/11/comments","events_url":"https://api.github.com/repos/torebutlin/cued_datalogger/issues/11/events","html_url":"https://github.com/torebutlin/cued_datalogger/issues/11","id":261133258,"number":11,"title":"Linux installation issues","user":{"login":"tombsar","id":3090978,"avatar_url":"https://avatars3.githubusercontent.com/u/3090978?v=4","gravatar_id":"","url":"https://api.github.com/users/tombsar","html_url":"https://github.com/tombsar","followers_url":"https://api.github.com/users/tombsar/followers","following_url":"https://api.github.com/users/tombsar/following{/other_user}","gists_url":"https://api.github.com/users/tombsar/gists{/gist_id}","starred_url":"https://api.github.com/users/tombsar/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tombsar/subscriptions","organizations_url":"https://api.github.com/users/tombsar/orgs","repos_url":"https://api.github.com/users/tombsar/repos","events_url":"https://api.github.com/users/tombsar/events{/privacy}","received_events_url":"https://api.github.com/users/tombsar/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2017-09-27T22:07:33Z","updated_at":"2017-09-27T22:37:51Z","closed_at":null,"author_association":"NONE","body":"Creating this issue to keep track of installation issues I encountered when trying to get the datalogger working on Debian Linux.\r\n\r\nFirstly, following the quickstart guide, I ran `pip install cued_datalogger` and got the following error:\r\n\r\n```\r\n~$ pip install cued_datalogger\r\nCollecting cued_datalogger\r\n  Downloading cued_datalogger-0.0.36.tar.gz (73kB)\r\n    100% |████████████████████████████████| 81kB 1.4MB/s \r\n    Complete output from command python setup.py egg_info:\r\n    Traceback (most recent call last):\r\n      File \"<string>\", line 1, in <module>\r\n      File \"/tmp/pip-build-YVtMz_/cued-datalogger/setup.py\", line 5, in <module>\r\n        import urllib.request\r\n    ImportError: No module named request\r\n    \r\n    ----------------------------------------\r\nCommand \"python setup.py egg_info\" failed with error code 1 in /tmp/pip-build-YVtMz_/cued-datalogger/\r\n```\r\n\r\nResearching this issue suggests that the `urllib.request` import is Python 3 specific, and `pip` is trying to run the script with Python 2 (at least on my system).\r\n\r\nIs the datalogger Python 3 only, or should it also work in Python 2? If Python 3 only, the documentation should specify this, and the command should probably use `pip3` rather than `pip` (unless my system is misconfigured somehow).\r\n\r\nNB This StackOverflow answer (https://stackoverflow.com/a/41385820) suggests an alternative that works in Python 2: `from urllib2 import urlopen`."},"comment":{"url":"https://api.github.com/repos/torebutlin/cued_datalogger/issues/comments/332675630","html_url":"https://github.com/torebutlin/cued_datalogger/issues/11#issuecomment-332675630","issue_url":"https://api.github.com/repos/torebutlin/cued_datalogger/issues/11","id":332675630,"user":{"login":"tombsar","id":3090978,"avatar_url":"https://avatars3.githubusercontent.com/u/3090978?v=4","gravatar_id":"","url":"https://api.github.com/users/tombsar","html_url":"https://github.com/tombsar","followers_url":"https://api.github.com/users/tombsar/followers","following_url":"https://api.github.com/users/tombsar/following{/other_user}","gists_url":"https://api.github.com/users/tombsar/gists{/gist_id}","starred_url":"https://api.github.com/users/tombsar/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tombsar/subscriptions","organizations_url":"https://api.github.com/users/tombsar/orgs","repos_url":"https://api.github.com/users/tombsar/repos","events_url":"https://api.github.com/users/tombsar/events{/privacy}","received_events_url":"https://api.github.com/users/tombsar/received_events","type":"User","site_admin":false},"created_at":"2017-09-27T22:37:51Z","updated_at":"2017-09-27T22:37:51Z","author_association":"NONE","body":"Running the install command with elevated privileges (`sudo pip3 install cued_datalogger`) seems to have been successful, although the output contains several error messages, including:\r\n```\r\nerror: invalid command 'bdist_wheel'\r\nRunning setup.py bdist_wheel for pyaudio: finished with status 'error'\r\nFailed building wheel for pyaudio\r\n[...]\r\nrunning clean\r\n'build/lib.linux-x86_64-3.5' does not exist -- can't clean it\r\n'build/bdist.linux-x86_64' does not exist -- can't clean it\r\n'build/scripts-3.5' does not exist -- can't clean it\r\nFailed to build pyaudio\r\n[...]\r\nsrc/_portaudiomodule.c:28:10: fatal error: Python.h: No such file or directory\r\n#include \"Python.h\"\r\n         ^~~~~~~~~~\r\ncompilation terminated.\r\nerror: command 'x86_64-linux-gnu-gcc' failed with exit status 1\r\nRunning setup.py install for pyaudio: finished with status 'error'\r\n```\r\n\r\nThe output finishes with the rather confusing:\r\n```\r\nFailed to build cued-datalogger\r\nInstalling collected packages: cued-datalogger\r\n  Running setup.py install for cued-datalogger ... done\r\nSuccessfully installed cued-datalogger-0.0.36\r\n```"}}
{"actor":{"display_login":"tombsar"}}