From: Tanguy LE CARROUR <tanguy@bioneland.org>
To: 45003-done@debbugs.gnu.org, Marius Bakke <marius@gnu.org>
Subject: [bug#45003] [PATCH] gnu: poetry: Fix a problem with a dependency.
Date: Fri, 04 Dec 2020 08:23:38 +0100 [thread overview]
Message-ID: <1607066408.sa1r45l72s.astroid@melmoth.none> (raw)
In-Reply-To: <87o8jaimtw.fsf@gnu.org>
Hi Marius!
Excerpts from Marius Bakke's message of December 3, 2020 10:47 pm:
> Tanguy Le Carrour <tanguy@bioneland.org> skriver:
>
>> * gnu/packages/python-xyz.scm (poetry)[arguments]: Relax version constraints
>> for python-packaging.
>
> Applied, thanks!
Thanks!
> Note: I tried to do this:
> […]
> But the test suite actually picks the 'python-packaging' that is
> propagated from 'pytest', and promptly fails.
>
> Updating packaging alone is also a staging-level change, so I did not
> dig much further. But there is some room for improvement here. Maybe
> by (setenv "PYTHONPATH" (string-append ".:" (getenv "PYTHONPATH"))) ?
>
> I also wonder whether pytest needs to propagate packaging at all, or if
> wrapping is enough. Do you know how common it is to "import pytest" or
> "from pytest import foo", and whether those code paths would need
> 'packaging'?
>
> Anyway, future problems! Thanks for maintaining Poetry. :-)
I would hardly call it "maintaining"! It's been more like a struggle! ^_^'
Now that the situation has (hopefully) stabilized, I can spend some time
on the "poetry build system".
Thank you again for your precious help and your time!
--
Tanguy
next prev parent reply other threads:[~2020-12-04 7:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 8:33 [bug#45003] [PATCH] gnu: poetry: Fix a problem with a dependency Tanguy Le Carrour
2020-12-03 21:47 ` bug#45003: " Marius Bakke
2020-12-04 7:23 ` Tanguy LE CARROUR [this message]
2020-12-04 7:35 ` [bug#45003] " Tanguy LE CARROUR
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=1607066408.sa1r45l72s.astroid@melmoth.none \
--to=tanguy@bioneland.org \
--cc=45003-done@debbugs.gnu.org \
--cc=marius@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.