Skip to content
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

python2legacy - various warnings then no valid dependency graphs #1582

Closed
hottwaj opened this issue Jan 11, 2019 · 3 comments
Closed

python2legacy - various warnings then no valid dependency graphs #1582

hottwaj opened this issue Jan 11, 2019 · 3 comments

Comments

@hottwaj
Copy link
Contributor

hottwaj commented Jan 11, 2019

I have just tried to build my app using the new (post API 26) toolchain. Unfortunately my app still needs to use pygame/sdl on android, so I saw in the docs that I need to use the python2legacy recipe

When I run P4A with the python2recipe selected, I get various warnings like this:

/home/jonathan/prog/src/p4a-2019/pythonforandroid/recipes/pyjnius/__init__.py:3: RuntimeWarning: Parent module 'pythonforandroid.recipes' not found while handling absolute import
  from pythonforandroid.patching import will_build

This happens for all recipes I have included in my build.

Finally, I get:

[ERROR]:   Build failed: Didn't find any valid dependency graphs. This means that some of your requirements pull in conflicting dependencies.

I guess that this is because some recipes depend on python2 (and not python2legacy)?

Thanks!

@homdx
Copy link

homdx commented Jan 14, 2019

Hello.
You not show in issue .p4a file or command line parameters or/and requirements.txt

@AndreMiras
Copy link
Member

Since #1582 was recently merged you could give it a try on master see if the problem is fixed.
e.g. via buildozer android update

@hottwaj
Copy link
Contributor Author

hottwaj commented Jan 14, 2019

Thanks, I will give that a try - and sorry for the lack of p4a cmd line parameters etc, my concern (which I wasn't clear on) was that the python2legacy route was not currently usable because of the recent overhaul

I will close for now and come back with anything specific that I have trouble with.

Cheers!

@hottwaj hottwaj closed this as completed Jan 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants