qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Thomas Huth" <thuth@redhat.com>,
	"Vladimir Sementsov-Ogievskiy" <vsementsov@virtuozzo.com>,
	"Daniel Berrange" <berrange@redhat.com>,
	"Eduardo Habkost" <ehabkost@redhat.com>,
	Qemu-block <qemu-block@nongnu.org>,
	"Markus Armbruster" <armbru@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Willian Rampazzo" <willianr@redhat.com>,
	"Hanna Reitz" <hreitz@redhat.com>,
	"Cleber Rosa" <crosa@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PULL 0/5] Python patches
Date: Thu, 18 Nov 2021 10:50:31 -0500	[thread overview]
Message-ID: <CAFn=p-adBsoLYCEX0UM8PyHW0QcGKBQXUPeFBez8yZ-0AHMaDw@mail.gmail.com> (raw)
In-Reply-To: <20211118064534.vbamk7ky2b5hawqm@sirius.home.kraxel.org>

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

On Thu, Nov 18, 2021 at 1:46 AM Gerd Hoffmann <kraxel@redhat.com> wrote:

>   Hi,
>
> > - Split python/qemu/qmp out into its own repository and begin uploading
> it
> > to PyPI, as a test. (Do not delete python/qemu/qmp yet at this phase.)
>
> I think you can do that as two separate steps.
>
> pip can install from vcs too, i.e. when splitted to a separate repo but
> not yet uploaded to pypi you can simply drop something like ...
>
>         git+https://gitlab.com/qemu/qemu-python.git@master
>
> ... into pip-requirements.txt.  That way you can easily test things
> before actually uploading to pypi.
>
>
Indeed - a limitation here however is that pip will not install from this
source unless explicitly asked to, so you couldn't use this package as a
requirement for another one, for example -- but it works as a testing step.
but that's the rough outline of where I am headed and what I think needs to
be done to get there. It's just taking me a while to get everything put in
order exactly the right way to be able to flip the switch. Hopefully soon,
though.

I realized when re-reading my mails last night that I said I wouldn't be
able to do it until "next release" but what I really meant was "until the
next development window".

--js

[-- Attachment #2: Type: text/html, Size: 1811 bytes --]

  reply	other threads:[~2021-11-18 15:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-17  0:33 [PULL 0/5] Python patches John Snow
2021-11-17  0:33 ` [PULL 1/5] python/aqmp: Fix disconnect during capabilities negotiation John Snow
2021-11-17  0:33 ` [PULL 2/5] python/aqmp: fix ConnectError string method John Snow
2021-11-17  0:33 ` [PULL 3/5] scripts/device-crash-test: simplify Exception handling John Snow
2021-11-17  0:33 ` [PULL 4/5] scripts/device-crash-test: don't emit AQMP connection errors to stdout John Snow
2021-11-17  0:33 ` [PULL 5/5] scripts/device-crash-test: hide tracebacks for QMP connect errors John Snow
2021-11-17  8:47 ` [PULL 0/5] Python patches Richard Henderson
2021-11-17  9:41 ` Gerd Hoffmann
2021-11-17 17:56   ` John Snow
2021-11-17 18:20     ` Vladimir Sementsov-Ogievskiy
2021-11-17 19:07       ` John Snow
2021-11-17 19:12         ` Vladimir Sementsov-Ogievskiy
2021-11-18  6:45     ` Gerd Hoffmann
2021-11-18 15:50       ` John Snow [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-04 21:04 John Snow
2023-01-05 18:42 ` Peter Maydell
     [not found] <20230531204338.1656158-1-jsnow@redhat.com>
2023-05-31 23:20 ` Richard Henderson

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='CAFn=p-adBsoLYCEX0UM8PyHW0QcGKBQXUPeFBez8yZ-0AHMaDw@mail.gmail.com' \
    --to=jsnow@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=crosa@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=hreitz@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=vsementsov@virtuozzo.com \
    --cc=wainersm@redhat.com \
    --cc=willianr@redhat.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 NNTP newsgroup(s).