On Monday, July 24, 2017 03:49:39 PM Sandro Knauß wrote:
> Hey,
>
> > I know the upstream developer. I would recommend that you contact him.
> > He's been gradually moving from Sourceforge to GitHub and I expect he'd
> > move pysrs if you offered to port it.
>
> Okay done - mail sent, than we se
Hey,
> I know the upstream developer. I would recommend that you contact him.
> He's been gradually moving from Sourceforge to GitHub and I expect he'd
> move pysrs if you offered to port it.
Okay done - mail sent, than we see what happens :)
Sandro
signature.asc
Description: This is a digita
On July 17, 2017 8:27:45 AM EDT, "Sandro Knauß" wrote:
>Hey,
>
>> This is work you're doing in collaboration with the ‘pysrs’ 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. Is that correct?
>
>well becau
Hey,
> This is work you're doing in collaboration with the ‘pysrs’ 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. Is that correct?
well because upstream has not add any patch for three years, I think upstrea
Sandro Knauß writes:
> I'm currently porting pysrs to python3 and sofar I got all tests
> running for python2 and python3 *yeah*.
Congratulations!
> But the porting was mostly adding encode()/ decode() to many parts of
> the module. And I'm unsure, if the API is now in a good shape, or if
> it
Hey,
I'm currently porting pysrs to python3 and sofar I got all tests running for
python2 and python3 *yeah*. But the porting was mostly adding encode()/
decode() to many parts of the module. And I'm unsure, if the API is now in a
good shape, or if it is mostly unusable for users, because I mixe
6 matches
Mail list logo
