From: Kashyap Chamarthy <kchamart@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: Cleber Rosa <crosa@redhat.com>,
Daniel Berrange <berrange@redhat.com>,
qemu-devel@nongnu.org, Beraldo Leal <bleal@redhat.com>
Subject: Re: [qemu.qmp PATCH 11/12] remove sub-dependency pins from Pipfile
Date: Mon, 25 Apr 2022 15:19:43 +0200 [thread overview]
Message-ID: <Ymaf77sfhrqYVvsA@paraplu> (raw)
In-Reply-To: <20220422184940.1763958-12-jsnow@redhat.com>
On Fri, Apr 22, 2022 at 02:49:39PM -0400, John Snow wrote:
> Now that we've got a Pipfile.lock generated that works, we can remove
> the static pins from the Pipfile to allow various dependencies to be
> added or removed as necessary when updating our direct dependencies in
> the future.
>
> So long as --keep-outdated is always passed to Pipenv, items that aren't
> absolutely necessary to update will not be, which will help keep our
> requirements more at the very oldest possible versions that still work.
>
> Signed-off-by: John Snow <jsnow@redhat.com>
Makes sense.
Reviewed-by: Kashyap Chamarthy <kchamart@redhat.com>
PS: I see that you've also documented a summary version of Pipfile.lock
et al in FILES.txt; thank you.
[...]
--
/kashyap
next prev parent reply other threads:[~2022-04-25 13:22 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 18:49 [qemu.qmp PATCH 00/12] python: fork qemu.qmp python lib into independent repo John Snow
2022-04-22 18:49 ` [qemu.qmp PATCH 01/12] fork qemu.qmp from qemu.git John Snow
2022-04-25 10:37 ` Daniel P. Berrangé
2022-04-25 18:54 ` John Snow
2022-04-22 18:49 ` [qemu.qmp PATCH 02/12] update maintainer metadata John Snow
2022-04-25 10:54 ` Daniel P. Berrangé
2022-04-25 18:15 ` John Snow
2022-04-22 18:49 ` [qemu.qmp PATCH 03/12] update project description John Snow
2022-04-29 13:44 ` Beraldo Leal
2022-04-22 18:49 ` [qemu.qmp PATCH 04/12] update project URLs John Snow
2022-04-25 10:56 ` Daniel P. Berrangé
2022-04-25 18:19 ` John Snow
2022-04-26 7:55 ` Daniel P. Berrangé
2022-04-26 8:16 ` Kashyap Chamarthy
2022-04-26 16:38 ` John Snow
2022-04-29 14:06 ` Beraldo Leal
2022-04-29 15:48 ` John Snow
2022-04-22 18:49 ` [qemu.qmp PATCH 05/12] add a couple new trove classifiers John Snow
2022-04-22 18:49 ` [qemu.qmp PATCH 06/12] move README.rst to FILES.rst and update John Snow
2022-04-25 13:23 ` Kashyap Chamarthy
2022-04-22 18:49 ` [qemu.qmp PATCH 07/12] move PACKAGE.rst to README.rst " John Snow
2022-04-22 18:49 ` [qemu.qmp PATCH 08/12] docs: add versioning policy to README John Snow
2022-04-22 18:49 ` [qemu.qmp PATCH 09/12] add LGPLv2+ and GPLv2 LICENSE files John Snow
2022-04-25 11:00 ` Daniel P. Berrangé
2022-04-22 18:49 ` [qemu.qmp PATCH 10/12] update Pipfile John Snow
2022-04-22 18:49 ` [qemu.qmp PATCH 11/12] remove sub-dependency pins from Pipfile John Snow
2022-04-25 13:19 ` Kashyap Chamarthy [this message]
2022-04-22 18:49 ` [qemu.qmp PATCH 12/12] update VERSION to 0.0.0a1 John Snow
2022-04-29 14:09 ` Beraldo Leal
2022-04-29 17:18 ` [qemu.qmp PATCH 00/12] python: fork qemu.qmp python lib into independent repo John Snow
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=Ymaf77sfhrqYVvsA@paraplu \
--to=kchamart@redhat.com \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=jsnow@redhat.com \
--cc=qemu-devel@nongnu.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.
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 NNTP newsgroup(s).