public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: pylint: ImportError: No module named pkg_resources
Date: Sun, 17 Jan 2021 06:32:44 +0100	[thread overview]
Message-ID: <1f07662a-714a-e1de-3658-04c3e5948dc6@gmail.com> (raw)
In-Reply-To: <vriusg70lbd5.fsf@gavenkoa.example.com>

On 17.01.2021 00:18, Oleksandr Gavenko via Cygwin wrote:
> After installing pylint:
> 
>    setup.exe -p pylint
> 
> I expected I can use the package:
> 
>    pylint /dev/null
> 
>    Traceback (most recent call last):
>      File "/usr/bin/pylint", line 5, in <module>
>        from pkg_resources import load_entry_point
>    ImportError: No module named pkg_resources
> 
> I tried to add package:
> 
>    python-setuptools
> 
> as suggested by:
> 
>    https://stackoverflow.com/questions/7446187/no-module-named-pkg-resources
> 
> and now it works.

Noted. I will look on it as it was anyway built for python2
that is now EOL

So need to be rebuilt to work with python3


> I believe that x86_64/setup.bz2 is broken:
> 
>    depends2: python, python-logilab-astng, python-logilab-common
> 
> It doesn't mention python-setuptools.
> 
> Or it might be that /usr/bin/pylint should be rewritten to avoid dependency to
> setuptools.
> 

This explain the status problem:

  $ grep -e "pylint" -e "logilab" cygwin-pkg-maint
pylint                                       ORPHANED (Jari Aalto)
python-logilab-astng                         ORPHANED (Jari Aalto)
python-logilab-common                        ORPHANED (Jari Aalto)

I guess one is also dead upstream (or was totally re-shaffled)
but I need to look again .

Thanks for the report
Marco

  reply	other threads:[~2021-01-17  5:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-16 23:18 Oleksandr Gavenko
2021-01-17  5:32 ` Marco Atzeri [this message]
2021-01-17 10:23   ` Oleksandr Gavenko
2021-01-17 21:36     ` Marco Atzeri

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=1f07662a-714a-e1de-3658-04c3e5948dc6@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin@cygwin.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).