From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: python2 vs python3 module build
Date: Thu, 20 Dec 2018 04:42:00 -0000 [thread overview]
Message-ID: <a4ac8cd0-1c0f-669d-13f2-5d271ad1c58d@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]
I was thinking to adopt and update some orphaned package
as I need pytest for python3.
Currenty there is also a collision in the python2 area
$ cygcheck -f /usr/bin/pytest
pylint-1.3.1-1
python-logilab-common-0.62.0-1
However it seems I need to build two different
versions for python 2 and python3
--------------------------------------------
$ cygport pylint.cygport install
>>> Installing pylint-2.2.2-1.x86_64
Processing ./dist/pylint-2.2.2-py2-none-any.whl
pylint requires Python '>=3.4.*' but the running Python is 2.7.14
You are using pip version 9.0.1, however version 18.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
*** ERROR: pip2 install failed
--------------------------------------------
Cygport Question:
there is a way to build only one of the two version as
"inherit python-wheel" build both ?
attached tentative cygport file.
Regards
Marco
---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
[-- Attachment #2: pylint.cygport --]
[-- Type: text/plain, Size: 1007 bytes --]
inherit python-wheel
NAME="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
python2_pylint_CONTENTS="usr/bin/*2 ${python2_pylint_CONTENTS}"
python3_pylint_CONTENTS="usr/bin/*3 ${python3_pylint_CONTENTS}"
next reply other threads:[~2018-12-20 4:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 4:42 Marco Atzeri [this message]
2018-12-20 4:49 ` 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=a4ac8cd0-1c0f-669d-13f2-5d271ad1c58d@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin-apps@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).