public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: python compilation issue on pylint
Date: Thu, 20 Dec 2018 09:42:00 -0000	[thread overview]
Message-ID: <ecc0222e-ca02-4580-69af-da32eeb6b85a@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]


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


changing in
   RAW_UNICODE = ur'\u0062\n'
or
   RAW_UNICODE = ur"\u0062"

make no difference.

Any clue what can cause it ?
For what I see the code was always there
https://github.com/PyCQA/pylint/commits/master/pylint/test/functional/anomalous_unicode_escape_py2.py

so it seems a cygwin build issue only.

Regards
Marco


---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

[-- Attachment #2: python3-pylint.cygport --]
[-- Type: text/plain, Size: 952 bytes --]

inherit python3-wheel

NAME="python3-pylint"
VERSION=2.2.2
RELEASE=1
CATEGORY="Python"
SUMMARY="Python static code checker"
DESCRIPTION="Analyzes source code for programming errors, helps enforcing a coding
standard and sniffs for some code smells (as defined in Martin
Fowler's Refactoring book). Pylint can be seen as another PyChecker
since nearly all tests you can do with PyChecker can also be done with
Pylint. However, Pylint offers some more features, like checking
length of lines of code, checking if variable names are well-formed
according to your coding standard, or checking if declared interfaces
are truly implemented, and much more."

HOMEPAGE="https://github.com/PyCQA/pylint"
SRC_URI="https://github.com/PyCQA/pylint/archive/pylint-${VERSION}.tar.gz"
SRC_DIR="pylint-pylint-${VERSION}"

# interferes with get_flags_linker_so in numpy.distutils.fcompiler
unset LDFLAGS

python3_pylint_CONTENTS="usr/bin/*3 ${python3_pylint_CONTENTS}"

[-- Attachment #3: Type: text/plain, Size: 219 bytes --]


--
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

             reply	other threads:[~2018-12-20  5:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-20  9:42 Marco Atzeri [this message]
2019-01-02  4:29 ` Yaakov Selkowitz

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=ecc0222e-ca02-4580-69af-da32eeb6b85a@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).