While I'm waiting for a response from mobile-sig, I'm going through
the documentation (and something called "fossies") of importlib. I
hope that it's okay to ask some follow up questions...even though I've
redirected this post to mobile-sig.
If it is, my first question(s) is/are about the import
It's not very helpful, but here it us if you want to look at it. I added the
INFO/ALERT statements in setup.py for troubleshooting purposes.
INFO: removing statically built modules
INFO: Parsing Modules/Setup and Setup.local
INFO: Getting env var to pass to setup.py
INFO: Building remaining exts
selton [mailto:chasel...@gmail.com]
>Sent: Monday, February 02, 2015 3:25 PM
>To: Ryan Gonzalez
>Cc: Python-Dev
>Subject: Re: [Python-Dev] Import Fails in setup.py On Android
>
>No traceback unfortunately...the fakechroot in the environment throws
>the error and setup.py<http:/
The array module is the current culprit.
Are there details about the freeze process at Python.org? That may help me
figure out what and why my build breaks?
I'll try my best to get a traceback...I don't have a working gdb in this env
yet...and if I do get one I'll add it to the email I send to
On Mon, Feb 2, 2015 at 12:36 PM, Cyd Haselton wrote:
> After fixing a segfault issue (many thanks Ryan) I'm back to the same issue
> I was having with Python 2.7.8; the newly built python throws an undefined
> reference to dlopen when running setup.py...specifically when importing
> just-built ext
Gonzalez
Cc: Python-Dev
Subject: Re: [Python-Dev] Import Fails in setup.py On Android
No traceback unfortunately...the fakechroot in the environment throws the error
and setup.py<http://setup.py> fails.
I'll roll back that change...any idea where I could find info about the
original
Unfortunately, I have no idea. You might want to ask someone who's more
familiar with the Python source than I am.
What exactly appears? Does it say anything about the source of the error?
On Mon, Feb 2, 2015 at 3:24 PM, Cyd Haselton wrote:
> No traceback unfortunately...the fakechroot in the e
No traceback unfortunately...the fakechroot in the environment throws the error
and setup.py fails.
I'll roll back that change...any idea where I could find info about the
original method?
On February 2, 2015 3:17:54 PM CST, Ryan Gonzalez wrote:
>In reality, things just got broken even more. I
In reality, things just got broken even more. I don't know when that patch
was created, but it's now very out of date: importlib._bootstrap has no
load function. That's what the error you're getting is telling you. Since
it isn't getting to load anything, the issue seems "solved". Not really.
What
Update: While waiting for replies I made the change referenced here:
https://bugs.python.org/review/5309/diff2/12811:12826/setup.py?context=3&column_width=80
specifically changing
importlib. _bootstrap._SpecMethods(spec).load()
to
importlib._bootstrap.load(spec)
I no longer get a
After fixing a segfault issue (many thanks Ryan) I'm back to the same issue I
was having with Python 2.7.8; the newly built python throws an undefined
reference to dlopen when running setup.py...specifically when importing
just-built extensions
I've managed to narrow the problem down to the fol
11 matches
Mail list logo
