{"action":"created","issue":{"url":"https://api.github.com/repos/pennersr/django-allauth/issues/968","labels_url":"https://api.github.com/repos/pennersr/django-allauth/issues/968/labels{/name}","comments_url":"https://api.github.com/repos/pennersr/django-allauth/issues/968/comments","events_url":"https://api.github.com/repos/pennersr/django-allauth/issues/968/events","html_url":"https://github.com/pennersr/django-allauth/issues/968","id":84343281,"number":968,"title":"Error: pip install: no such file or directory [during the compiling of provider files]","user":{"login":"Toruitas","id":7018206,"avatar_url":"https://avatars.githubusercontent.com/u/7018206?v=3","gravatar_id":"","url":"https://api.github.com/users/Toruitas","html_url":"https://github.com/Toruitas","followers_url":"https://api.github.com/users/Toruitas/followers","following_url":"https://api.github.com/users/Toruitas/following{/other_user}","gists_url":"https://api.github.com/users/Toruitas/gists{/gist_id}","starred_url":"https://api.github.com/users/Toruitas/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Toruitas/subscriptions","organizations_url":"https://api.github.com/users/Toruitas/orgs","repos_url":"https://api.github.com/users/Toruitas/repos","events_url":"https://api.github.com/users/Toruitas/events{/privacy}","received_events_url":"https://api.github.com/users/Toruitas/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-06-03T03:53:27Z","updated_at":"2016-01-19T18:20:38Z","closed_at":"2015-07-22T22:00:02Z","body":"When installing django-allauth with pip on a win7 x64 and python 3.4.3 also x64, I get this error (from the pip log):\r\n\r\n    byte-compiling C:\\Users\\Stuart\\documents\\github\\python\\practice\\django1\\taskbuster_project\\tb_test\\Lib\\site-packages\\allauth\\socialaccount\\providers\\facebook\\south_migrations\\0002_auto__add_facebookaccesstoken__add_unique_facebookaccesstoken_app_acco.py to 0002_auto__add_facebookaccesstoken__add_unique_facebookaccesstoken_app_acco.cpython-34.pyc\r\n    \r\n    error: [Errno 2] No such file or directory: 'C:\\\\Users\\\\Stuart\\\\documents\\\\github\\\\python\\\\practice\\\\django1\\\\taskbuster_project\\\\tb_test\\\\Lib\\\\site-packages\\\\allauth\\\\socialaccount\\\\providers\\\\facebook\\\\south_migrations\\\\__pycache__\\\\0002_auto__add_facebookaccesstoken__add_unique_facebookaccesstoken_app_acco.cpython-34.pyc.56169120'\r\n\r\n----\r\n    Command \"C:\\Users\\Stuart\\documents\\github\\python\\practice\\django1\\taskbuster_project\\tb_test\\Scripts\\python.exe -c \"import setuptools, tokenize;__file__='C:\\\\Users\\\\Stuart\\\\AppData\\\\Local\\\\Temp\\\\pip-build-2d2ya9l6\\\\django-allauth\\\\setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\\r\\n', '\\n'), __file__, 'exec'))\" install --record C:\\Users\\Stuart\\AppData\\Local\\Temp\\pip-ztgym5qu-record\\install-record.txt --single-version-externally-managed --compile --install-headers C:\\Users\\Stuart\\documents\\github\\python\\practice\\django1\\taskbuster_project\\tb_test\\include\\site\\python3.4\" failed with error code 1 in C:\\Users\\Stuart\\AppData\\Local\\Temp\\pip-build-2d2ya9l6\\django-allauth\r\n    \r\n\r\nI thought it may be a bad tarball, but of course after deleting the pip cache and redownloading the results are the same. \r\n\r\nsite-packages\\allauth\\socialaccount\\providers\\facebook\\south_migrations does contain a similarly named file \r\n0002_auto__add_facebookaccesstoken__add_unique_facebookaccesstoken_app_acco.py , \r\nbut there's nothing compiled in the __pycache__ folder.\r\n\r\nAny ideas why it is trying and failing to compile the .py into a .pyc?"},"comment":{"url":"https://api.github.com/repos/pennersr/django-allauth/issues/comments/172939946","html_url":"https://github.com/pennersr/django-allauth/issues/968#issuecomment-172939946","issue_url":"https://api.github.com/repos/pennersr/django-allauth/issues/968","id":172939946,"user":{"login":"wasabigeek","id":4256705,"avatar_url":"https://avatars.githubusercontent.com/u/4256705?v=3","gravatar_id":"","url":"https://api.github.com/users/wasabigeek","html_url":"https://github.com/wasabigeek","followers_url":"https://api.github.com/users/wasabigeek/followers","following_url":"https://api.github.com/users/wasabigeek/following{/other_user}","gists_url":"https://api.github.com/users/wasabigeek/gists{/gist_id}","starred_url":"https://api.github.com/users/wasabigeek/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wasabigeek/subscriptions","organizations_url":"https://api.github.com/users/wasabigeek/orgs","repos_url":"https://api.github.com/users/wasabigeek/repos","events_url":"https://api.github.com/users/wasabigeek/events{/privacy}","received_events_url":"https://api.github.com/users/wasabigeek/received_events","type":"User","site_admin":false},"created_at":"2016-01-19T18:20:38Z","updated_at":"2016-01-19T18:20:38Z","body":"@Toruitas I had a similar issue while trying to upgrade from 0.18.0 to 0.22.0. What worked for me (not a great solution by any means) was to make a new virtualenv that installed allauth to 0.22.0 directly."}}