python-ipaddress: new package

Host variant is needed to build python-cryptography package.

Signed-off-by Yegor Yefremov <[email protected]>

---
 package/python-cffi/python-cffi.mk | 2 ++
 1 file changed, 2 insertions(+)

package/python-cffi/python-cffi.mk +0 -0

index 70fbe02..a6e4107 100644

package/python-cffi/python-cffi.mk +1 -0

 $(eval $(python-package))
+$(eval $(host-python-package))

Signature · 6 lines

2.1.4

_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

Yegor, All,

On 2015-12-24 22:30 +0100, Yegor Yefremov spake thusly:

Quoted 12 lines

Host variant is needed to build python-cryptography package.

Signed-off-by Yegor Yefremov <[email protected]>

---
 package/python-cffi/python-cffi.mk | 2 ++
 1 file changed, 2 insertions(+)

package/python-cffi/python-cffi.mk +0 -0

index 70fbe02..a6e4107 100644

package/python-cffi/python-cffi.mk PYTHON_CFFI_SETUP_TYPE = setuptools · line 14

Quoted 4 lines

package/python-cffi/python-cffi.mk +1 -0

@@ -11,5 +11,7 @@ PYTHON_CFFI_SETUP_TYPE = setuptools
 PYTHON_CFFI_DEPENDENCIES = host-pkgconf libffi
 PYTHON_CFFI_LICENSE = MIT
 PYTHON_CFFI_LICENSE_FILES = LICENSE
+HOST_PYTHON_CFFI_DEPENDENCIES = host-python-pycparser

So, the host variant needs python-pycparser, but the target variantdoes not?

I would have expect either:

    PYTHON_CFFI_DEPENDENCIES += host-python-pycparser

or:

    PYTHON_CFFI_DEPENDENCIES += python-pycparser

Care to shed some light on this, please?

Target variant doesn't need pycparser. cffi's setup.py seems to distinguish, if we install real package or cross-compiled one:

        install_requires=[
            'pycparser',
        ] if cpython else [],

Quoted 6 lines

Target variant doesn't need pycparser. cffi's setup.py seems to distinguish, if we install real package or cross-compiled one:

        install_requires=[
            'pycparser',
        ] if cpython else [],

I don't understand how this "if cpython" is relevant to make the different between the native (host) variant or the cross-compiled (target) variant. cpython is defined as is:

cpython = ('_cffi_backend' not in sys.builtin_module_names)

Can you give some more details?

Thomas, Yegor, All,

On 2015-12-25 20:00 +0100, Thomas Petazzoni spake thusly:

Quoted 8 lines · Yegor Yefremov

Quoted 6 lines

Target variant doesn't need pycparser. cffi's setup.py seems to distinguish, if we install real package or cross-compiled one:

        install_requires=[
            'pycparser',
        ] if cpython else [],

Quoted 7 lines

I don't understand how this "if cpython" is relevant to make the different between the native (host) variant or the cross-compiled (target) variant. cpython is defined as is:

cpython = ('_cffi_backend' not in sys.builtin_module_names)

Can you give some more details?

Yegor and I briefly discussed this on IRC yesterday, but I'm not really convinced by this reply either. I forgot to reply yesterday...

What I understand, however, is that they want to differentiate between cpython (the 'ofiicial' native Python interpreter), and PyPy (the Python interpreter written in Python).

Of course, I don't see how this all works. It seems in cross-compilation. there differentiation criterai beliveves it is running under PyPy amd thus they do not need pycparser.

But thtat's just incorrect, because we may have a host-python with cffi_backend at one point, and thus the check above will eventually differentiate toward cpython, and we'd nreak again.

So, two things:
- their check is wrong,
- we probably need host-pycparser

At least, that's what I understood...

Quoted 32 lines

On 2015-12-25 20:00 +0100, Thomas Petazzoni spake thusly:

Quoted 8 lines · Yegor Yefremov

Quoted 6 lines

Target variant doesn't need pycparser. cffi's setup.py seems to distinguish, if we install real package or cross-compiled one:

        install_requires=[
            'pycparser',
        ] if cpython else [],

Quoted 7 lines

I don't understand how this "if cpython" is relevant to make the different between the native (host) variant or the cross-compiled (target) variant. cpython is defined as is:

cpython = ('_cffi_backend' not in sys.builtin_module_names)

Can you give some more details?

Yegor and I briefly discussed this on IRC yesterday, but I'm not really convinced by this reply either. I forgot to reply yesterday...

What I understand, however, is that they want to differentiate between cpython (the 'ofiicial' native Python interpreter), and PyPy (the Python interpreter written in Python).

Of course, I don't see how this all works. It seems in cross-compilation. there differentiation criterai beliveves it is running under PyPy amd thus they do not need pycparser.

But thtat's just incorrect, because we may have a host-python with cffi_backend at one point, and thus the check above will eventually differentiate toward cpython, and we'd nreak again.

Quoted 5 lines

So, two things:
- their check is wrong,
- we probably need host-pycparser

At least, that's what I understood...

We have host-pycparser: http://patchwork.ozlabs.org/patch/560970/

Yegor, All,

On 2015-12-25 20:58 +0100, Yegor Yefremov spake thusly:

Quoted 39 lines · Yann E. MORIN

Quoted 37 lines

On 2015-12-25 20:00 +0100, Thomas Petazzoni spake thusly:

Quoted 8 lines · Yegor Yefremov

Quoted 6 lines

Target variant doesn't need pycparser. cffi's setup.py seems to distinguish, if we install real package or cross-compiled one:

        install_requires=[
            'pycparser',
        ] if cpython else [],

Quoted 7 lines

I don't understand how this "if cpython" is relevant to make the different between the native (host) variant or the cross-compiled (target) variant. cpython is defined as is:

cpython = ('_cffi_backend' not in sys.builtin_module_names)

Can you give some more details?

Yegor and I briefly discussed this on IRC yesterday, but I'm not really convinced by this reply either. I forgot to reply yesterday...

What I understand, however, is that they want to differentiate between cpython (the 'ofiicial' native Python interpreter), and PyPy (the Python interpreter written in Python).

Of course, I don't see how this all works. It seems in cross-compilation. there differentiation criterai beliveves it is running under PyPy amd thus they do not need pycparser.

But thtat's just incorrect, because we may have a host-python with cffi_backend at one point, and thus the check above will eventually differentiate toward cpython, and we'd nreak again.

So, two things:
- their check is wrong,
- we probably need host-pycparser

At least, that's what I understood...

Quoted 1 line

We have host-pycparser: http://patchwork.ozlabs.org/patch/560970/

Well, I meant that we should need host-pycparser as a dependency of python-cffi.

But anyway, there is more to this: we really need to understand what is going on...

Quoted 4 lines · Yann E. MORIN

Yegor, All,

On 2015-12-25 20:58 +0100, Yegor Yefremov spake thusly:

Quoted 1 line

On Fri, Dec 25, 2015 at 8:12 PM, Yann E. MORIN <[email protected]>

Quoted 13 lines · wrote:

Quoted 13 lines

Quoted 13 lines

On 2015-12-25 20:00 +0100, Thomas Petazzoni spake thusly:

Quoted 12 lines · Yegor Yefremov

Quoted 6 lines

Target variant doesn't need pycparser. cffi's setup.py seems to distinguish, if we install real package or cross-compiled one:

        install_requires=[
            'pycparser',
        ] if cpython else [],

I don't understand how this "if cpython" is relevant to make the different between the native (host) variant or the cross-compiled (target) variant. cpython is defined as is:

Quoted 5 lines

Quoted 5 lines

Quoted 5 lines

Quoted 3 lines

cpython = ('_cffi_backend' not in sys.builtin_module_names)

Can you give some more details?

Yegor and I briefly discussed this on IRC yesterday, but I'm not

really

Quoted 4 lines

Quoted 4 lines

Quoted 4 lines

convinced by this reply either. I forgot to reply yesterday...

What I understand, however, is that they want to differentiate between cpython (the 'ofiicial' native Python interpreter), and PyPy (the

Python

Quoted 16 lines

Quoted 16 lines

Quoted 15 lines

interpreter written in Python).

Of course, I don't see how this all works. It seems in cross-compilation. there differentiation criterai beliveves it is running under PyPy amd thus they do not need pycparser.

But thtat's just incorrect, because we may have a host-python with cffi_backend at one point, and thus the check above will eventually differentiate toward cpython, and we'd nreak again.

So, two things:
- their check is wrong,
- we probably need host-pycparser

At least, that's what I understood...

Quoted 7 lines

Quoted 1 line

We have host-pycparser: http://patchwork.ozlabs.org/patch/560970/

Well, I meant that we should need host-pycparser as a dependency of python-cffi.

But anyway, there is more to this: we really need to understand what is going on...

I still don't really understand the difference between host and target cffi requirements, but at least I can now shed some light on cpython definition. Below is sys.builtin_module_names() description:

"A tuple of strings giving the names of all modules that are compiled into this Python interpreter."

So our host-python version won't show '_cffi_backend' even if it is installed on the system, because it is not built-in. But PyPy
(http://pypy.org/) comes with this backend out of the box.

Will debug further.

@Oli: what are you using cffi for?

Yegor

Quoted 68 lines · Yegor Yefremov

Quoted 46 lines · Yann E. MORIN

Yegor, All,

On 2015-12-25 20:58 +0100, Yegor Yefremov spake thusly:

Quoted 43 lines

Quoted 40 lines · Yann E. MORIN

On 2015-12-25 20:00 +0100, Thomas Petazzoni spake thusly:

Quoted 8 lines · Yegor Yefremov

Quoted 6 lines

Target variant doesn't need pycparser. cffi's setup.py seems to distinguish, if we install real package or cross-compiled one:

        install_requires=[
            'pycparser',
        ] if cpython else [],

Quoted 7 lines

I don't understand how this "if cpython" is relevant to make the different between the native (host) variant or the cross-compiled (target) variant. cpython is defined as is:

cpython = ('_cffi_backend' not in sys.builtin_module_names)

Can you give some more details?

Yegor and I briefly discussed this on IRC yesterday, but I'm not really
convinced by this reply either. I forgot to reply yesterday...

What I understand, however, is that they want to differentiate between
cpython (the 'ofiicial' native Python interpreter), and PyPy (the Python
interpreter written in Python).

Of course, I don't see how this all works. It seems in cross-compilation. there differentiation criterai beliveves it is running under PyPy amd thus they do not need pycparser.

But thtat's just incorrect, because we may have a host-python with cffi_backend at one point, and thus the check above will eventually differentiate toward cpython, and we'd nreak again.

So, two things:
- their check is wrong,
- we probably need host-pycparser

At least, that's what I understood...

Quoted 7 lines

Quoted 1 line

We have host-pycparser: http://patchwork.ozlabs.org/patch/560970/

Well, I meant that we should need host-pycparser as a dependency of python-cffi.

But anyway, there is more to this: we really need to understand what is going on...

I still don't really understand the difference between host and target cffi requirements, but at least I can now shed some light on cpython definition. Below is sys.builtin_module_names() description:

"A tuple of strings giving the names of all modules that are compiled into this Python interpreter."

So our host-python version won't show '_cffi_backend' even if it is installed on the system, because it is not built-in. But PyPy
(http://pypy.org/) comes with this backend out of the box.

Quoted 5 lines

Will debug further.

@Oli: what are you using cffi for?

Yegor

Hello Yegor, All

It's been some time since I worked with buildroot. At the time I was trying
to include smbus-cffi <https://pypi.python.org/pypi/smbus-cffi> into buildroot's python modules and this needs cffi. I wanted to try an alternative module to pysmbus which did not integrate right away.
Meanwhile the module pysmbus <https://pypi.python.org/pypi/pysmbus/0.1> has
been included in buildroot, thank you.