public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Migrating fireinfo to Python 3
Date: Fri, 07 May 2021 11:16:44 +0000	[thread overview]
Message-ID: <20210507111654.2397-1-michael.tremer@ipfire.org> (raw)
In-Reply-To: <74B08C60-EBDB-4C2E-83E0-A5EB5A0C3C5E@ipfire.org>

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

Hello,

I went ahead and converted fireinfo to Python 3.

This was a little bit more work than usual because it has a little
helper module written in C.

I could mainly use 2to3, but some things needed some manual attention. I
split those into individual commits.

I would now like to invite everyone to manually install this version on
their systems and let me know if it

  a) works

and

  b) does it keep the same ID?

The ID is being generated by a number of factors and if one bit in those
changes, the system would receive a different ID which is something we
would like to avoid.

It worked fine on my system, but I would like to have some larger sample
size to be sure.

Best,
-Michael



  parent reply	other threads:[~2021-05-07 11:16 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-05 14:27 Dropping Python 2 Michael Tremer
2021-05-05 16:49 ` Adolf Belka
2021-05-05 17:12   ` Adolf Belka
2021-05-05 21:46     ` Adolf Belka
2021-05-05 22:30   ` Michael Tremer
2021-05-06 19:40     ` Dropping Python 2 - question about boost Adolf Belka
2021-05-07 11:00       ` Michael Tremer
2021-05-07 11:16 ` Michael Tremer [this message]
2021-05-07 11:16   ` [PATCH 01/10] configure: Link against Python 3 Michael Tremer
2021-05-07 11:16   ` [PATCH 02/10] _fireinfo: Migrate to " Michael Tremer
2021-05-07 11:16   ` [PATCH 03/10] _fireinfo: Refactor some code Michael Tremer
2021-05-07 11:16   ` [PATCH 04/10] Run 2to3 Michael Tremer
2021-05-07 11:21     ` Michael Tremer
2021-05-14 12:10   ` Migrating fireinfo to Python 3 Adolf Belka
2021-05-14 12:13     ` Michael Tremer
2021-05-17 13:59       ` Adolf Belka
2021-05-18 10:29         ` Michael Tremer
2021-05-11 10:37 ` Dropping Python 2 (Problem with ipaddr) Adolf Belka
2021-05-11 10:40   ` Michael Tremer
2021-05-15 11:51     ` Adolf Belka
2021-05-11 12:18 ` Dropping Python 2 (questions about python modules that are in python3 and python2 versions) Adolf Belka
2021-05-12 18:34   ` Jonatan Schlag
2021-05-13 17:36     ` Adolf Belka
2021-05-11 13:24 ` Dropping Python 2 (problems with libxml2 and libxslt) Adolf Belka
2021-05-11 13:25   ` Michael Tremer
2021-05-11 13:31     ` Adolf Belka
2021-05-12 11:07 ` Dropping Python 2 (python-distutils & python-distutils-extra) Adolf Belka
2021-05-12 17:11   ` Michael Tremer
2021-05-12 12:31 ` Dropping Python 2 (python-mechanize + knock on effects) Adolf Belka
2021-05-14 19:28 ` Dropping Python 2 (python-m2crypto) Adolf Belka
2021-05-15 21:03   ` Adolf Belka
2021-05-16 14:16     ` Adolf Belka
2021-05-20 10:15   ` Michael Tremer
2021-05-20 10:30     ` Adolf Belka
2021-05-20 11:21       ` Michael Tremer
2021-05-22 12:25     ` Adolf Belka
2021-05-25 10:03       ` Michael Tremer
2021-05-29 14:31         ` Jonatan Schlag
2021-05-29 16:19           ` Adolf Belka
2021-05-15  8:28 ` Dropping Python 2 (python-optional-src) Adolf Belka
2021-05-15  8:41   ` Adolf Belka

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=20210507111654.2397-1-michael.tremer@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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