Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9766] New: support/scripts/pkgutil.py conflicts with the pkgutil.py from setuptools => breaks scanpypi (2017.02)
Date: Mon, 20 Mar 2017 18:26:30 +0000	[thread overview]
Message-ID: <bug-9766-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=9766

            Bug ID: 9766
           Summary: support/scripts/pkgutil.py conflicts with the
                    pkgutil.py from setuptools => breaks scanpypi
                    (2017.02)
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: timo.valimaki at sensoan.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

Asked the following in Stackoverflow:

"I'm trying to run the scanpypi script - support script of the Buildroot
(2017.02) but I'm getting the ImportError: cannot import name get_importer.

Traceback (most recent call last): File "./support/scripts/scanpypi", line 52,
in import setuptools File
"/usr/local/lib/python2.7/dist-packages/setuptools/init.py", line 12, in import
setuptools.version File
"/usr/local/lib/python2.7/dist-packages/setuptools/version.py", line 1, in
import pkg_resources File
"/usr/local/lib/python2.7/dist-packages/pkg_resources/init.py", line 40, in
from pkgutil import get_importer ImportError: cannot import name get_importer

I added the following lines into beginning of the scanpypi script to see
sys.path

    import sys
    print(sys.path)

output:

['/home/timo/bldr_lab/buildroot/support/scripts', '/usr/lib/python2.7',
'/usr/lib/python2.7/plat-x86_64-linux-gnu', '/usr/lib/python2.7/lib-tk',
'/usr/lib/python2.7/lib-old', '/usr/lib/python2.7/lib-dynload',
'/usr/local/lib/python2.7/dist-packages', '/usr/lib/python2.7/dist-packages']

As the pkgutil is in the /usr/lib/python2.7 directory the problem is not path
problem.

I have also uninstalled and re-installed python2.7, pip and setuptools but no
help.

What could be reason for the ImportError?"


Got the response:


This is a bug in Buildroot. It is due to commit
12683184b1969f65680cb7db55b547a620a9860f that introduced the pkgutil.py file in
support/scripts. This conflicts with the pkgutil.py from setuptools.

The solution is to rename the pkgutil.py file to something else, and update the
imports in the other scripts accordingly. If you do this, please post a patch
on the Buildroot mailing list, so everyone can benefit. See the manual for
details how to post patches.


http://stackoverflow.com/questions/42892298/import-error-cannot-import-name-get-importer.

Need to practice script creating ...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2017-03-20 18:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-20 18:26 bugzilla at busybox.net [this message]
2017-03-25 13:46 ` [Buildroot] [Bug 9766] support/scripts/pkgutil.py conflicts with the pkgutil.py from setuptools => breaks scanpypi (2017.02) bugzilla at busybox.net

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=bug-9766-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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