From: Efraim Flashner <efraim@flashner.co.il>
To: Ben Woodcroft <b.woodcroft@uq.edu.au>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: pytest plugins
Date: Sun, 10 Apr 2016 13:34:42 +0300 [thread overview]
Message-ID: <20160410103442.GA24736@debian-netbook> (raw)
In-Reply-To: <570A0C9A.6030802@uq.edu.au>
[-- Attachment #1: Type: text/plain, Size: 1339 bytes --]
On Sun, Apr 10, 2016 at 06:19:38PM +1000, Ben Woodcroft wrote:
> Hi there,
>
> I'm running into clashes when using pytest plugins e.g.
>
> $ ./pre-inst-env guix environment -C --ad-hoc python-pytest-cov
> [..]
> warning: collision encountered: /gnu/store/cfj96msw5ypxcii4z615l03wbjq5hcs9-python-pytest-cov-2.2.0/bin/py.test
> /gnu/store/4hz0mf56b9mm8q97k5iw5xbb909vsz4p-python-pytest-2.7.3/bin/py.test
> warning: arbitrarily choosing /gnu/store/cfj96msw5ypxcii4z615l03wbjq5hcs9-python-pytest-cov-2.2.0/bin/py.test
> [..]
>
> i.e. the pytest executable is included in `python-pytest' as well
> `python-pytest-cov'.
>
> I'm not sure what the best thing to do is here, because no environment
> variable is honoured during the py.test startup sequence when looking for
> plugins:
>
> http://pytest.org/latest/writing_plugins.html#plugin-discovery-order-at-tool-startup
>
> Do any pythonistas have any ideas on how to get around this?
>
> Thanks,
> ben
>
I'll try to take a look at it soon-ish™. My first guess is it has to do
with the propagated inputs of some of the python-test packages.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-04-10 10:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-10 8:19 pytest plugins Ben Woodcroft
2016-04-10 10:34 ` Efraim Flashner [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=20160410103442.GA24736@debian-netbook \
--to=efraim@flashner.co.il \
--cc=b.woodcroft@uq.edu.au \
--cc=guix-devel@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.