Path: csiph.com!feeder.erje.net!2.eu.feeder.erje.net!feed.usenet.farm!feeder3.usenet.farm!eternal-september.org!feeder.eternal-september.org!aioe.org!bofh.it!news.nic.it!robomod
From: Scott Kitterman <debian@kitterman.com>
Newsgroups: linux.debian.maint.python
Subject: Re: python3 for pysrs
Date: Mon, 17 Jul 2017 18:30:03 +0200
Message-ID: <u4h4f-7oe-31@gated-at.bofh.it>
References: <u3WCt-2DO-17@gated-at.bofh.it> <u40wp-545-1@gated-at.bofh.it> <u4dtE-51t-27@gated-at.bofh.it>
Old-Return-Path: <debian@kitterman.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Approved: robomod@news.nic.it
Lines: 50
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:9632



On July 17, 2017 8:27:45 AM EDT, "Sandro Knau=C3=9F" <bugs@sandroknauss=2E=
de> wrote:
>Hey,
>
>> This is work you're doing in collaboration with the =E2=80=98pysrs=E2=
=80=99 upstream
>> developers, right? You are aiming to get users to test this, and get
>it
>> into a release, before doing any of this in Debian=2E Is that correct?
>
>well because upstream has not add any patch for three years, I think
>upstream=20
>is dead=2E I'll send upsteam also a mail with my propolsoal for pysrs
>python3,=20
>but I think I'll don't get response=2E But before asking upstream I would
>like=20
>to have somebody looking at my python3 changes if they are going into
>the=20
>right direction=2E
>
>> I think that porting a work to Python 3 is not appropriate for a
>Debian
>> patch=2E That should be done only in a maintained upstream work; maybe
>a
>> fork, but certainly not just a patch on the released upstream work
>for
>> Python 2 only=2E
>
>Yes I know, that this is not really part of an Debian patch, but
>because=20
>upstream is not doing anything, I started now to push python3 support=2E
>And I=20
>think at this list there are many people how saw many python3 support
>patches,=20
>to give some hints, where to pay attention=2E
>Well if upstream is dead I'll need to fork it=2E

I know the upstream developer=2E  I would recommend that you contact him=
=2E  He's been gradually moving from Sourceforge to GitHub and I expect he'=
d move pysrs if you offered to port it=2E =20

My understanding is he views it as doing what it's supposed to do, so rath=
er than dead, it's merely sleeping=2E

In addition to email, you can usually find him on IRC at #spf on irc=2Eper=
l=2Eorg=2E

Scott K