From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Test: python packages
Date: Thu, 21 Jan 2021 17:27:08 +0100 [thread overview]
Message-ID: <217c637b-4960-8714-befd-7782826866fc@gmail.com> (raw)
In-Reply-To: <DB7PR02MB3996CEB1D34FB21A138E808FE7A10@DB7PR02MB3996.eurprd02.prod.outlook.com>
On 21.01.2021 17:18, Hamish McIntyre-Bhatty via Cygwin wrote:
> On 19/01/2021 21:08, Marco Atzeri via Cygwin-announce via Cygwin wrote:
>> Several python packages have been uploaded as test
Hi Hamish
please trim when replying
> Thanks for packaging pylint Marco, should be very useful.
>
> While things are mostly fine (I tested with 32-bit and 64-bit with
> python36-pylint), I did notice a few things with the pylint packages:
>
> 1: The "pylint" package itself (the test package) doesn't install any of
> the python3x-pylint packages - is this intentional?
>
> 2: There is no "pylint" or "pylint3" command available in the terminal
> after install. Not a deal breaker as one can use "python3.x -m pylint
> ./file.py" but being able to run "pylint(3) ./file.py" is a nice
> convenience feature :)
>
> Hamish
it should pull python38-pylint
$ cygcheck -l python38-pylint | grep bin
/usr/bin/pylint3.8
/usr/bin/epylint3.8
/usr/bin/pyreverse3.8
/usr/bin/symilar3.8
/usr/bin/pylint
/usr/bin/epylint
/usr/bin/pyreverse
/usr/bin/symilar
next prev parent reply other threads:[~2021-01-21 16:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 21:08 Marco Atzeri via Cygwin-announce
2021-01-21 16:18 ` Hamish McIntyre-Bhatty
2021-01-21 16:27 ` Marco Atzeri [this message]
2021-01-21 16:37 ` Hamish McIntyre-Bhatty
2021-01-21 16:52 ` Marco Atzeri
2021-01-21 17:06 ` Hamish McIntyre-Bhatty
2021-01-21 19:06 ` Marco Atzeri
2021-01-22 9:29 ` Hamish McIntyre-Bhatty
-- strict thread matches above, loose matches on Subject: below --
2021-01-13 12:03 Marco Atzeri via Cygwin-announce
2021-01-02 11:48 Marco Atzeri via Cygwin-announce
2020-12-31 7:31 Marco Atzeri via Cygwin-announce
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=217c637b-4960-8714-befd-7782826866fc@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).