QEMU-Devel Archive on lore.kernel.org
 help / color / Atom feed
From: John Snow <jsnow@redhat.com>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] Python3 support for patches
Date: Fri, 13 Sep 2019 17:21:37 -0400
Message-ID: <46399543-4205-93b9-0ec2-7ebb3821eb93@redhat.com> (raw)
In-Reply-To: <12460c01-6960-bd66-501a-46fc31ad7be1@redhat.com>



On 9/13/19 3:32 PM, John Snow wrote:
> Hi,
> 
> I quite like the patches tool; but python2 is notably doomed.
> 
> I tried my hand at polishing it up for python3 and pushed the results
> here: https://github.com/jnsnow/patches/tree/python3
> 
> I didn't faff around with trying to add simultaneous support: this is a
> direct conversion in one big chunk. I used 2to3 and supplemented with
> pylint and flake8 to find problem spots.
> 
> I don't use all of the features of this tool, but maybe if you'd like to
> give this a try you can test this branch and let me know if I missed any
> spots.
> 
> You can install patches 0.3.1 using the standard incantations:
>> python3 setup.py install --user
> 
> If it's too broken, you can uninstall it later with:
>> pip3 uninstall patches
> 
> You may need to check back to the master branch and force a
> reinstallation of the python2 version to get the bin back in your PATH:
> 
>> git checkout master
>> python2 setup.py install --user
> 
> 
> Happy python2 doomsday,
> --js
> 

Ah, this was definitely premature. I had a dream last night that this
was working just fine, but in the harsh, unforgiving sunlight, there are
still a few problems.

Needs a few more minutes in the oven.

--js


  reply index

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-13 19:32 John Snow
2019-09-13 21:21 ` John Snow [this message]
2019-09-17 16:00   ` Stefan Hajnoczi
2019-09-17 17:43     ` John Snow

Reply instructions:

You may reply publically 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=46399543-4205-93b9-0ec2-7ebb3821eb93@redhat.com \
    --to=jsnow@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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

QEMU-Devel Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/qemu-devel/0 qemu-devel/git/0.git
	git clone --mirror https://lore.kernel.org/qemu-devel/1 qemu-devel/git/1.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 qemu-devel qemu-devel/ https://lore.kernel.org/qemu-devel \
		qemu-devel@nongnu.org qemu-devel@archiver.kernel.org
	public-inbox-index qemu-devel


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.nongnu.qemu-devel


AGPL code for this site: git clone https://public-inbox.org/ public-inbox