Core dump on loading python3.7 when using futures in requirements

[akshayaurora]

Versions

• Python:3.7
• OS:
• Kivy:
• Cython:

Core dump on loading python3.7 when using futures in requirements

I was in the process of moving my app from a old py2 build to the python3 one in p4a master when the app would simply crash with a core dump on android.

buildozer.spec

Just add futures as a requirement with python3

Command: buildozer android debug deploy run logcat

Logs

http://paste.opensuse.org/view//88462490

on some successive failures I used the get the following line at the end of the crash dump

#01 pc 001c8db8  /data/app/org.pydatadelhi.conf2019-3LJ2kxGuga_dks0fo6JWGw==/lib/arm/libpython3.7m.so (offset 0x84000)
07-24 16:10:15.017 13895 13916 E LB      : fail to open file: No such file or directory

Futures is of-course a lib that is in standard library. Main issue is not with future itself but with the fact that we for what ever reason, don't give a informative output, there is just a core dump.

My intuitive reaction to this is that the best solution would be if the people writing the futures library changed it such that it won't crash a py3 interpreter but rather make it spit out an ImportError. (which likely means making a bug on the official python bugtracker about this might be helpful)

Because wouldn't this possibly happen on desktop as well with this crash? It just doesn't seem to me like p4a is a good general place to solve this, as much as this sucks porting python 2 stuff to python 3 stuff

[inclement]

Does this happen the same way on the desktop? I don't understand what's the actual reason for the crash, could it be that we are setting up the pythonpath in such a way that it overrides a builtin or something (whereas it wouldn't normally)?

[akshayaurora]

Just checked on desktop, python3 -m pip install futures does not lead to a error.

There are 2 issues here

1. pip installs futures on python3 ....it shouldn't? Maybe a upstream bug. You have been able to install/upgrade standard modules with pip, so futures is no different?
2. This installed futures lib causes Python3 to crash on p4a. Does not result in a crash on desktops.

• Further investigation needed for this.