-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pure python requirements does not install (plyer for example) #795
Comments
Hmm, looks like the requirements.txt is incorrectly empty (or maybe otherwise invalid). This vaguely rings a bell but I don't know why. Just to check, presumably you're using an up-to-date p4a? |
I installed it from github about a week ago pip install git+https://github.com/kivy/python-for-android On Sat, Jun 18, 2016 at 7:55 PM, Alexander Taylor notifications@github.com
|
I just checked this, but couldn't reproduce it. You could try with the newest master version in case that fixes it, but other than that I'm not sure how to track it down. |
I just installed fresh version from master and this issue still exists. Complete log: https://gist.github.com/Fak3/e840bcd9bdec63f2d505f353b3c306f1 I created new dist testpygame_new, and the requirements.txt error still looks the same. And plyer is still nowhere to be found in the dist directory. |
Oh, I think i mixed my venv\system python2\3 - it may be the culprit. Checking it now |
Right. On my system pip points to pip3 by default. I think I initialized p4a using python2 from virtualenv (actually, buildozer did that for me). Then I got an error that p4a should not be launched inside virtualenv and installed system-wide p4a with pip3. Running that system-wide p4a results in this bug. |
Hi. I Tried to create a dstro with plyer package included. Build process does not throw any error, distro reports that the plyer requirement is installed, but it is not. Debug logging reveal some issues with pure-python requirements.txt handling:
The text was updated successfully, but these errors were encountered: