From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: python compilation issue on pylint
Date: Wed, 02 Jan 2019 04:29:00 -0000 [thread overview]
Message-ID: <4d8e0dc0a11f2ba11a946df51f8edeb53f94ad07.camel@cygwin.com> (raw)
In-Reply-To: <ecc0222e-ca02-4580-69af-da32eeb6b85a@gmail.com>
On Thu, 2018-12-20 at 06:19 +0100, Marco Atzeri wrote:
> I am trying to build a recent pylint with the attached cygport
> but the following error is puzzling me
>
> /usr/lib/python3.6/assert_on_tuple.py:11: SyntaxWarning: assertion is
> always true, perhaps remove parentheses?
> *** Error compiling
> '/cygdrive/d/cyg_pub/devel/python-module/python3-pylint-2.2.2-1.x86_64/inst/usr/lib/python3.6/site-packages/pylint/test/functional/anomalous_unicode_escape_py2.py'...
> File "/usr/lib/python3.6/anomalous_unicode_escape_py2.py", line 17
> RAW_UNICODE = ur"\u0062\n"
> ^
> SyntaxError: invalid syntax
This appears to be a(n old?) Py2-specific test, which won't byte-
compile with Py3 because of the language changes in between. However,
as this is simply a testcase, it doesn't really have to be installed at
all. FWIW, Fedora just removes the tests entirely, and I would
recommend the same. Presuming you are using python3-wheel (since
pylint 2.x does not support Py2), try the following:
src_install() {
cd ${B}
python3_wheel_install
find ${D}${PYTHON3_SITELIB}/pylint/test/ -delete
}
--
Yaakov
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2019-01-02 4:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 9:42 Marco Atzeri
2019-01-02 4:29 ` Yaakov Selkowitz [this message]
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=4d8e0dc0a11f2ba11a946df51f8edeb53f94ad07.camel@cygwin.com \
--to=yselkowitz@cygwin.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).