[Buildroot] [PATCH 1/5] python-ipaddress: new package

[Buildroot] [PATCH 1/5] python-ipaddress: new package

[Yegor Yefremov]

Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
---
 package/Config.in                              |  1 +
 package/python-ipaddress/Config.in             |  7 +++++++
 package/python-ipaddress/python-ipaddress.hash |  3 +++
 package/python-ipaddress/python-ipaddress.mk   | 13 +++++++++++++
 4 files changed, 24 insertions(+)
 create mode 100644 package/python-ipaddress/Config.in
 create mode 100644 package/python-ipaddress/python-ipaddress.hash
 create mode 100644 package/python-ipaddress/python-ipaddress.mk

diff --git a/package/Config.in b/package/Config.in
index de0ad5e..e2f387d 100644
--- a/package/Config.in
+++ b/package/Config.in
@@ -639,6 +639,7 @@ menu "External python modules"
 	source "package/python-id3/Config.in"
 	source "package/python-idna/Config.in"
 	source "package/python-ipaddr/Config.in"
+	source "package/python-ipaddress/Config.in"
 	source "package/python-ipy/Config.in"
 	source "package/python-ipython/Config.in"
 	source "package/python-itsdangerous/Config.in"
diff --git a/package/python-ipaddress/Config.in b/package/python-ipaddress/Config.in
new file mode 100644
index 0000000..b2b9f0b
--- /dev/null
+++ b/package/python-ipaddress/Config.in
@@ -0,0 +1,7 @@
+config BR2_PACKAGE_PYTHON_IPADDRESS
+	bool "python-ipaddress"
+	depends on BR2_PACKAGE_PYTHON
+	help
+	  Python 3.3's ipaddress for older Python versions.
+
+	  https://github.com/phihag/ipaddress
diff --git a/package/python-ipaddress/python-ipaddress.hash b/package/python-ipaddress/python-ipaddress.hash
new file mode 100644
index 0000000..21bc373
--- /dev/null
+++ b/package/python-ipaddress/python-ipaddress.hash
@@ -0,0 +1,3 @@
+# md5 from https://pypi.python.org/pypi?:action=show_md5&digest=12915e923b738107e47827478d553ba1, sha256 locally computed
+md5     12915e923b738107e47827478d553ba1  ipaddress-1.0.15.tar.gz
+sha256  af6c85cfc9cdb12b861655e6b9f2f59618bf3088cbde858727b2c0a98e9f6636  ipaddress-1.0.15.tar.gz
diff --git a/package/python-ipaddress/python-ipaddress.mk b/package/python-ipaddress/python-ipaddress.mk
new file mode 100644
index 0000000..8019aa8
--- /dev/null
+++ b/package/python-ipaddress/python-ipaddress.mk
@@ -0,0 +1,13 @@
+################################################################################
+#
+# python-ipaddress
+#
+################################################################################
+
+PYTHON_IPADDRESS_VERSION = 1.0.15
+PYTHON_IPADDRESS_SOURCE = ipaddress-$(PYTHON_IPADDRESS_VERSION).tar.gz
+PYTHON_IPADDRESS_SITE = https://pypi.python.org/packages/source/i/ipaddress
+PYTHON_IPADDRESS_LICENSE = Python software foundation license
+PYTHON_IPADDRESS_SETUP_TYPE = setuptools
+
+$(eval $(python-package))
-- 
2.1.4

[Buildroot] [PATCH 2/5] python-pycparser: new package

[Yegor Yefremov]

Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
---
 package/Config.in                              |  1 +
 package/python-pycparser/Config.in             |  6 ++++++
 package/python-pycparser/python-pycparser.hash |  3 +++
 package/python-pycparser/python-pycparser.mk   | 15 +++++++++++++++
 4 files changed, 25 insertions(+)
 create mode 100644 package/python-pycparser/Config.in
 create mode 100644 package/python-pycparser/python-pycparser.hash
 create mode 100644 package/python-pycparser/python-pycparser.mk

diff --git a/package/Config.in b/package/Config.in
index e2f387d..f767ebc 100644
--- a/package/Config.in
+++ b/package/Config.in
@@ -664,6 +664,7 @@ menu "External python modules"
 	source "package/python-psutil/Config.in"
 	source "package/python-pyasn/Config.in"
 	source "package/python-pycli/Config.in"
+	source "package/python-pycparser/Config.in"
 	source "package/python-pycrypto/Config.in"
 	source "package/python-pydal/Config.in"
 	source "package/python-pyftpdlib/Config.in"
diff --git a/package/python-pycparser/Config.in b/package/python-pycparser/Config.in
new file mode 100644
index 0000000..99ab8d1
--- /dev/null
+++ b/package/python-pycparser/Config.in
@@ -0,0 +1,6 @@
+config BR2_PACKAGE_PYTHON_PYCPARSER
+	bool "python-pycparser"
+	help
+	  Complete C99 parser in pure Python.
+
+	  https://github.com/eliben/pycparser/
diff --git a/package/python-pycparser/python-pycparser.hash b/package/python-pycparser/python-pycparser.hash
new file mode 100644
index 0000000..a87bfd4
--- /dev/null
+++ b/package/python-pycparser/python-pycparser.hash
@@ -0,0 +1,3 @@
+# md5 from https://pypi.python.org/pypi?:action=show_md5&digest=a2bc8d28c923b4fe2b2c3b4b51a4f935, sha256 locally computed
+md5     a2bc8d28c923b4fe2b2c3b4b51a4f935  pycparser-2.14.tar.gz
+sha256  7959b4a74abdc27b312fed1c21e6caf9309ce0b29ea86b591fd2e99ecdf27f73  pycparser-2.14.tar.gz
diff --git a/package/python-pycparser/python-pycparser.mk b/package/python-pycparser/python-pycparser.mk
new file mode 100644
index 0000000..a32f1aa
--- /dev/null
+++ b/package/python-pycparser/python-pycparser.mk
@@ -0,0 +1,15 @@
+################################################################################
+#
+# python-pycparser
+#
+################################################################################
+
+PYTHON_PYCPARSER_VERSION = 2.14
+PYTHON_PYCPARSER_SOURCE = pycparser-$(PYTHON_PYCPARSER_VERSION).tar.gz
+PYTHON_PYCPARSER_SITE = https://pypi.python.org/packages/source/p/pycparser
+PYTHON_PYCPARSER_SETUP_TYPE = setuptools
+PYTHON_PYCPARSER_LICENSE = BSD-3c
+PYTHON_PYCPARSER_LICENSE_FILES = LICENSE
+
+$(eval $(python-package))
+$(eval $(host-python-package))
-- 
2.1.4

[Buildroot] [PATCH 3/5] python-cffi: add host variant

[Yegor Yefremov]

Host variant is needed to build python-cryptography package.

Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
---
 package/python-cffi/python-cffi.mk | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/package/python-cffi/python-cffi.mk b/package/python-cffi/python-cffi.mk
index 70fbe02..a6e4107 100644
--- a/package/python-cffi/python-cffi.mk
+++ b/package/python-cffi/python-cffi.mk
@@ -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
 
 $(eval $(python-package))
+$(eval $(host-python-package))
-- 
2.1.4

[Buildroot] [PATCH 4/5] python-cryptography: new package

[Yegor Yefremov]

Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
---
 package/Config.in                                  |  1 +
 package/python-cryptography/Config.in              | 20 +++++++++++++++++++
 .../python-cryptography/python-cryptography.hash   |  3 +++
 package/python-cryptography/python-cryptography.mk | 23 ++++++++++++++++++++++
 4 files changed, 47 insertions(+)
 create mode 100644 package/python-cryptography/Config.in
 create mode 100644 package/python-cryptography/python-cryptography.hash
 create mode 100644 package/python-cryptography/python-cryptography.mk

diff --git a/package/Config.in b/package/Config.in
index f767ebc..4c96454 100644
--- a/package/Config.in
+++ b/package/Config.in
@@ -625,6 +625,7 @@ menu "External python modules"
 	source "package/python-configobj/Config.in"
 	source "package/python-configshell-fb/Config.in"
 	source "package/python-crc16/Config.in"
+	source "package/python-cryptography/Config.in"
 	source "package/python-daemon/Config.in"
 	source "package/python-dialog/Config.in"
 	source "package/python-django/Config.in"
diff --git a/package/python-cryptography/Config.in b/package/python-cryptography/Config.in
new file mode 100644
index 0000000..c6d183f
--- /dev/null
+++ b/package/python-cryptography/Config.in
@@ -0,0 +1,20 @@
+config BR2_PACKAGE_PYTHON_CRYPTOGRAPHY
+	bool "python-cryptography"
+	depends on BR2_INSTALL_LIBSTDCPP # python-pyasn
+	select BR2_PACKAGE_OPENSSL
+	select BR2_PACKAGE_PYTHON_CFFI
+	select BR2_PACKAGE_PYTHON_SETUPTOOLS
+	select BR2_PACKAGE_PYTHON_IDNA
+	select BR2_PACKAGE_PYTHON_PYASN
+	select BR2_PACKAGE_PYTHON_PYEXPAT if BR2_PACKAGE_PYTHON
+	select BR2_PACKAGE_PYTHON3_PYEXPAT if BR2_PACKAGE_PYTHON3
+	select BR2_PACKAGE_PYTHON_ENUM34 if BR2_PACKAGE_PYTHON
+	select BR2_PACKAGE_PYTHON_IPADDRESS if BR2_PACKAGE_PYTHON
+	help
+	  cryptography is a package designed to expose cryptographic
+	  primitives and recipes to Python developers.
+
+	  https://cryptography.io
+
+comment "python-cryptography needs a toolchain w/ C++"
+	depends on !BR2_INSTALL_LIBSTDCPP
diff --git a/package/python-cryptography/python-cryptography.hash b/package/python-cryptography/python-cryptography.hash
new file mode 100644
index 0000000..0358624
--- /dev/null
+++ b/package/python-cryptography/python-cryptography.hash
@@ -0,0 +1,3 @@
+# md5 from https://pypi.python.org/pypi?:action=show_md5&digest=15eeba9e31f852bac21155baa3dfbc61, sha256 locally computed
+md5     15eeba9e31f852bac21155baa3dfbc61  cryptography-1.1.2.tar.gz
+sha256  7f51459f84d670444275e615839f4542c93547a12e938a0a4906dafe5f7de153  cryptography-1.1.2.tar.gz
diff --git a/package/python-cryptography/python-cryptography.mk b/package/python-cryptography/python-cryptography.mk
new file mode 100644
index 0000000..fbd0caf
--- /dev/null
+++ b/package/python-cryptography/python-cryptography.mk
@@ -0,0 +1,23 @@
+################################################################################
+#
+# python-cryptography
+#
+################################################################################
+
+PYTHON_CRYPTOGRAPHY_VERSION = 1.1.2
+PYTHON_CRYPTOGRAPHY_SOURCE = cryptography-$(PYTHON_CRYPTOGRAPHY_VERSION).tar.gz
+PYTHON_CRYPTOGRAPHY_SITE = https://pypi.python.org/packages/source/c/cryptography
+PYTHON_CRYPTOGRAPHY_SETUP_TYPE = setuptools
+PYTHON_CRYPTOGRAPHY_LICENSE = Apache
+PYTHON_CRYPTOGRAPHY_LICENSE_FILES = LICENSE
+PYTHON_CRYPTOGRAPHY_DEPENDENCIES = python-six \
+				   python-idna \
+				   python-pyasn \
+				   host-python-cffi \
+				   openssl
+
+ifeq ($(BR2_PACKAGE_PYTHON),y)
+PYTHON_CRYPTOGRAPHY_DEPENDENCIES += python-enum34
+endif
+
+$(eval $(python-package))
-- 
2.1.4

[Buildroot] [PATCH 5/5] python-pyopenssl: new package

[Yegor Yefremov]

Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
---
 package/Config.in                              |  1 +
 package/python-pyopenssl/Config.in             | 12 ++++++++++++
 package/python-pyopenssl/python-pyopenssl.hash |  3 +++
 package/python-pyopenssl/python-pyopenssl.mk   | 14 ++++++++++++++
 4 files changed, 30 insertions(+)
 create mode 100644 package/python-pyopenssl/Config.in
 create mode 100644 package/python-pyopenssl/python-pyopenssl.hash
 create mode 100644 package/python-pyopenssl/python-pyopenssl.mk

diff --git a/package/Config.in b/package/Config.in
index 4c96454..1d8496d 100644
--- a/package/Config.in
+++ b/package/Config.in
@@ -671,6 +671,7 @@ menu "External python modules"
 	source "package/python-pyftpdlib/Config.in"
 	source "package/python-pygame/Config.in"
 	source "package/python-pyinotify/Config.in"
+	source "package/python-pyopenssl/Config.in"
 	source "package/python-pyparsing/Config.in"
 	source "package/python-pypcap/Config.in"
 	source "package/python-pyqt/Config.in"
diff --git a/package/python-pyopenssl/Config.in b/package/python-pyopenssl/Config.in
new file mode 100644
index 0000000..cb59e8b
--- /dev/null
+++ b/package/python-pyopenssl/Config.in
@@ -0,0 +1,12 @@
+config BR2_PACKAGE_PYTHON_PYOPENSSL
+	bool "python-pyopenssl"
+	depends on BR2_INSTALL_LIBSTDCPP # python-cryptography
+	select BR2_PACKAGE_PYTHON_SIX
+	select BR2_PACKAGE_PYTHON_CRYPTOGRAPHY
+	help
+	  Python wrapper module around the OpenSSL library.
+
+	  https://github.com/pyca/pyopenssl
+
+comment "python-pyopenssl needs a toolchain w/ C++"
+	depends on !BR2_INSTALL_LIBSTDCPP
diff --git a/package/python-pyopenssl/python-pyopenssl.hash b/package/python-pyopenssl/python-pyopenssl.hash
new file mode 100644
index 0000000..0c6e25a
--- /dev/null
+++ b/package/python-pyopenssl/python-pyopenssl.hash
@@ -0,0 +1,3 @@
+# md5 from https://pypi.python.org/pypi?:action=show_md5&digest=f447644afcbd5f0a1f47350fec63a4c6, sha256 locally computed
+md5     f447644afcbd5f0a1f47350fec63a4c6  pyOpenSSL-0.15.1.tar.gz
+sha256  f0a26070d6db0881de8bcc7846934b7c3c930d8f9c79d45883ee48984bc0d672  pyOpenSSL-0.15.1.tar.gz
diff --git a/package/python-pyopenssl/python-pyopenssl.mk b/package/python-pyopenssl/python-pyopenssl.mk
new file mode 100644
index 0000000..239fd98
--- /dev/null
+++ b/package/python-pyopenssl/python-pyopenssl.mk
@@ -0,0 +1,14 @@
+################################################################################
+#
+# python-pyopenssl
+#
+################################################################################
+
+PYTHON_PYOPENSSL_VERSION = 0.15.1
+PYTHON_PYOPENSSL_SOURCE = pyOpenSSL-$(PYTHON_PYOPENSSL_VERSION).tar.gz
+PYTHON_PYOPENSSL_SITE = https://pypi.python.org/packages/source/p/pyOpenSSL
+PYTHON_PYOPENSSL_LICENSE = Apache-2.0
+PYTHON_PYOPENSSL_LICENSE_FILES = LICENSE
+PYTHON_PYOPENSSL_SETUP_TYPE = setuptools
+
+$(eval $(python-package))
-- 
2.1.4

[Buildroot] [PATCH 3/5] python-cffi: add host variant

[Yann E. MORIN]

Yegor, All,

On 2015-12-24 22:30 +0100, Yegor Yefremov spake thusly:
> Host variant is needed to build python-cryptography package.
> 
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
> ---
>  package/python-cffi/python-cffi.mk | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/package/python-cffi/python-cffi.mk b/package/python-cffi/python-cffi.mk
> index 70fbe02..a6e4107 100644
> --- a/package/python-cffi/python-cffi.mk
> +++ b/package/python-cffi/python-cffi.mk
> @@ -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?

Regards,
Yann E. MORIN.

>  $(eval $(python-package))
> +$(eval $(host-python-package))
> -- 
> 2.1.4
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

[Buildroot] [PATCH 3/5] python-cffi: add host variant

[Yegor Yefremov]

On Thu, Dec 24, 2015 at 10:46 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> Yegor, All,
>
> On 2015-12-24 22:30 +0100, Yegor Yefremov spake thusly:
>> Host variant is needed to build python-cryptography package.
>>
>> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
>> ---
>>  package/python-cffi/python-cffi.mk | 2 ++
>>  1 file changed, 2 insertions(+)
>>
>> diff --git a/package/python-cffi/python-cffi.mk b/package/python-cffi/python-cffi.mk
>> index 70fbe02..a6e4107 100644
>> --- a/package/python-cffi/python-cffi.mk
>> +++ b/package/python-cffi/python-cffi.mk
>> @@ -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 [],

https://bitbucket.org/cffi/cffi/src/f52d1e25624c8fcdd70088b53db91a3e27bc8f23/setup.py?at=default&fileviewer=file-view-default#setup.py-171

Yegor

[Buildroot] [PATCH 3/5] python-cffi: add host variant

[Thomas Petazzoni]

Dear Yegor Yefremov,

On Thu, 24 Dec 2015 23:12:49 +0100, Yegor Yefremov wrote:

> 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?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] [PATCH 3/5] python-cffi: add host variant

[Yann E. MORIN]

Thomas, Yegor, All,

On 2015-12-25 20:00 +0100, Thomas Petazzoni spake thusly:
> On Thu, 24 Dec 2015 23:12:49 +0100, Yegor Yefremov wrote:
> > 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?

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...

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

[Buildroot] [PATCH 3/5] python-cffi: add host variant

[Yegor Yefremov]

On Fri, Dec 25, 2015 at 8:12 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> Thomas, Yegor, All,
>
> On 2015-12-25 20:00 +0100, Thomas Petazzoni spake thusly:
>> On Thu, 24 Dec 2015 23:12:49 +0100, Yegor Yefremov wrote:
>> > 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?
>
> 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...

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

Yegor

[Buildroot] [PATCH 3/5] python-cffi: add host variant

[Yann E. MORIN]

Yegor, All,

On 2015-12-25 20:58 +0100, Yegor Yefremov spake thusly:
> On Fri, Dec 25, 2015 at 8:12 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > On 2015-12-25 20:00 +0100, Thomas Petazzoni spake thusly:
> >> On Thu, 24 Dec 2015 23:12:49 +0100, Yegor Yefremov wrote:
> >> > 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?
> >
> > 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...
> 
> 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...

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

[Buildroot] [PATCH 3/5] python-cffi: add host variant

[Yegor Yefremov]

On Fri, Dec 25, 2015 at 10:44 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> Yegor, All,
>
> On 2015-12-25 20:58 +0100, Yegor Yefremov spake thusly:
>> On Fri, Dec 25, 2015 at 8:12 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
>> > On 2015-12-25 20:00 +0100, Thomas Petazzoni spake thusly:
>> >> On Thu, 24 Dec 2015 23:12:49 +0100, Yegor Yefremov wrote:
>> >> > 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?
>> >
>> > 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...
>>
>> 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

[Buildroot] [PATCH 3/5] python-cffi: add host variant

[Oli Vogt]

On 27 December 2015 at 11:54, Yegor Yefremov <yegorslists@googlemail.com>
wrote:

> On Fri, Dec 25, 2015 at 10:44 PM, Yann E. MORIN <yann.morin.1998@free.fr>
> wrote:
> > Yegor, All,
> >
> > On 2015-12-25 20:58 +0100, Yegor Yefremov spake thusly:
> >> On Fri, Dec 25, 2015 at 8:12 PM, Yann E. MORIN <yann.morin.1998@free.fr>
> wrote:
> >> > On 2015-12-25 20:00 +0100, Thomas Petazzoni spake thusly:
> >> >> On Thu, 24 Dec 2015 23:12:49 +0100, Yegor Yefremov wrote:
> >> >> > 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?
> >> >
> >> > 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...
> >>
> >> 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
>
?
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.

Happy New Year, oli

?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20151231/7e018050/attachment.html>

[Buildroot] [PATCH 3/5] python-cffi: add host variant

[Yegor Yefremov]

Hello Oli,

On Thu, Dec 31, 2015 at 8:20 AM, Oli Vogt <oli.vogt.pub01@gmail.com> wrote:
>
> On 27 December 2015 at 11:54, Yegor Yefremov <yegorslists@googlemail.com>
> wrote:
>>
>> On Fri, Dec 25, 2015 at 10:44 PM, Yann E. MORIN <yann.morin.1998@free.fr>
>> wrote:
>> > Yegor, All,
>> >
>> > On 2015-12-25 20:58 +0100, Yegor Yefremov spake thusly:
>> >> On Fri, Dec 25, 2015 at 8:12 PM, Yann E. MORIN
>> >> <yann.morin.1998@free.fr> wrote:
>> >> > On 2015-12-25 20:00 +0100, Thomas Petazzoni spake thusly:
>> >> >> On Thu, 24 Dec 2015 23:12:49 +0100, Yegor Yefremov wrote:
>> >> >> > 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?
>> >> >
>> >> > 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...
>> >>
>> >> 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
>
> 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.

Thanks for clarification. I'll take a look at smbus-cffi.

Happy New Year to all Buildrooters!

Yegor