Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 04/20] python3: make it exclusive from	python
Date: Sun, 09 Oct 2016 09:55:40 +0200	[thread overview]
Message-ID: <so9pcdxaht.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: CAGm1_kv=SFf1jZ=O+JAOiqL9e+_WtQ=UpxeTbX2AQayntH8BaQ@mail.gmail.com

Am Sat, 08 Oct 2016 20:23:09 +0200 schrieb Yegor Yefremov:

> isn't mwclient Python 3 compatible? See [1]
> 
> [1] https://github.com/mwclient/mwclient/blob/master/setup.py#L48

Hi Yegor,

using this defconfig

BR2_TOOLCHAIN_BUILDROOT_WCHAR=y
BR2_PACKAGE_PYTHON3=y
BR2_PACKAGE_PYTHON_MWCLIENT=y

this error occurs with plain make:
-------------------------------------------------
>>>   Finalizing target directory
PYTHONPATH="/home/buildroot/br3_couchdb/output/target/usr/lib/python3.5/
sysconfigdata/:/home/buildroot/br3_couchdb/output/target/usr/lib/
python3.5/site-packages/" /home/buildroot/br3_couchdb/output/host/usr/bin/
python3.5 support/scripts/pycompile.py /home/buildroot/br3_couchdb/output/
target/usr/lib/python3.5
Traceback (most recent call last):
  File "/home/buildroot/br3_couchdb/output/host/usr/lib/python3.5/
py_compile.py", line 125, in compile
    _optimize=optimize)
  File "<frozen importlib._bootstrap_external>", line 700, in 
source_to_code
  File "<frozen importlib._bootstrap>", line 222, in 
_call_with_frames_removed
  File "/home/buildroot/br3_couchdb/output/target/usr/lib/python3.5/site-
packages/mwclient/ex.py", line 15
    exec _file in globals(), predata
             ^
SyntaxError: invalid syntax
-------------------------------------------------
This error does not occur with python2.

Regards, Bernd

  reply	other threads:[~2016-10-09  7:55 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18 20:39 [Buildroot] [PATCH v2 00/20] Python 2 and 3 bumps, support for Python 3 external modules Thomas Petazzoni
2014-02-18 20:39 ` [Buildroot] [PATCH v2 01/20] pkg-python: no longer use distutilscross for setuptools Thomas Petazzoni
2014-02-18 21:57   ` Peter Korsgaard
2014-02-18 20:39 ` [Buildroot] [PATCH v2 02/20] python-distutilscross: remove package that is no longer needed Thomas Petazzoni
2014-02-18 21:58   ` Peter Korsgaard
2014-02-18 20:39 ` [Buildroot] [PATCH v2 03/20] python3: removal of *.py/*.pyc is now done globally Thomas Petazzoni
2014-02-18 21:58   ` Peter Korsgaard
2014-02-18 20:39 ` [Buildroot] [PATCH v2 04/20] python3: make it exclusive from python Thomas Petazzoni
2014-02-18 21:58   ` Peter Korsgaard
2016-10-05 18:00   ` Bernd Kuhls
2016-10-05 19:30     ` Thomas Petazzoni
2016-10-08 12:24       ` Yann E. MORIN
2016-10-08 12:51         ` Thomas Petazzoni
2016-10-08 13:51           ` Yann E. MORIN
2016-10-08 14:02             ` Thomas Petazzoni
2016-10-08 15:57               ` Bernd Kuhls
2016-10-08 18:23                 ` Yegor Yefremov
2016-10-09  7:55                   ` Bernd Kuhls [this message]
2016-10-09  9:44                     ` Yegor Yefremov
2016-10-09 11:29                       ` Yegor Yefremov
2016-10-08 16:55               ` Yann E. MORIN
2014-02-18 20:39 ` [Buildroot] [PATCH v2 05/20] python3: add python -> python3 symlink for the host variant Thomas Petazzoni
2014-02-18 21:58   ` Peter Korsgaard
2014-02-18 20:39 ` [Buildroot] [PATCH v2 06/20] python3: add config directory symbolic link Thomas Petazzoni
2014-02-18 21:56   ` Peter Korsgaard
2014-02-18 22:17     ` Thomas Petazzoni
2014-02-18 22:21       ` Peter Korsgaard
2014-02-18 20:40 ` [Buildroot] [PATCH v2 07/20] python3: use proper PYTHON3_VERSION_MAJOR instead of harcoding 3.3 Thomas Petazzoni
2014-02-18 22:22   ` Peter Korsgaard
2014-02-18 20:40 ` [Buildroot] [PATCH v2 08/20] python3: bump to 3.4.0rc1 Thomas Petazzoni
2014-02-18 22:23   ` Peter Korsgaard
2014-02-18 20:40 ` [Buildroot] [PATCH v2 09/20] python3: provide a PYTHON3_PATH Thomas Petazzoni
2014-02-18 22:29   ` Peter Korsgaard
2014-02-18 22:33     ` Thomas Petazzoni
2014-02-18 20:40 ` [Buildroot] [PATCH v2 10/20] package: add python3 support in the package infrastructure Thomas Petazzoni
2014-02-18 20:40 ` [Buildroot] [PATCH v2 11/20] package: allow Python packages with Python3 Thomas Petazzoni
2014-02-18 20:40 ` [Buildroot] [PATCH v2 12/20] python, python3: enable unicodedata for host-python, needed by setuptools Thomas Petazzoni
2014-02-18 20:40 ` [Buildroot] [PATCH v2 13/20] python-setuptools: bump version to 2.1.2 Thomas Petazzoni
2014-02-18 20:40 ` [Buildroot] [PATCH v2 14/20] python, python3: fix to ensure libpython is stripped Thomas Petazzoni
2014-02-18 20:40 ` [Buildroot] [PATCH v2 15/20] python-pyasn: use the real upstream Thomas Petazzoni
2014-02-18 20:40 ` [Buildroot] [PATCH v2 16/20] python-bottle: allow to build with Python 3 Thomas Petazzoni
2014-02-18 20:40 ` [Buildroot] [PATCH v2 17/20] python-serial: " Thomas Petazzoni
2014-02-18 20:40 ` [Buildroot] [PATCH v2 18/20] python-pyasn: " Thomas Petazzoni
2014-02-18 20:40 ` [Buildroot] [PATCH v2 19/20] python-pycrypto: " Thomas Petazzoni
2014-02-18 20:40 ` [Buildroot] [PATCH v2 20/20] python-pysnmp{, -apps, -mibs}: " Thomas Petazzoni
2014-02-19  8:03 ` [Buildroot] [PATCH v2 00/20] Python 2 and 3 bumps, support for Python 3 external modules Peter Korsgaard
2014-02-19  8:23   ` Thomas Petazzoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=so9pcdxaht.ln2@ID-313208.user.individual.net \
    --to=bernd.kuhls@t-online.de \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox