Re: Re: small remark on packaging consistency

2019-12-11 Thread Patrice Duroux


Hi Julien,

For the PKG-INFO file I just found it inside the .tar.gz available here where I
am checking Python module:
https://pypi.org/project/testpath/#files

but may be I am wrong to check such a source. This repository is may be adding
it then.

Otherwise sure the new package is much better and fine to me, it was rather
facts that aroused my curiosity.

Thanks for all,
Patrice




Re: Re: small remark on packaging consistency

2019-12-11 Thread Julien Puydt
Hi,

Le mercredi 11 décembre 2019 à 20:10 +0100, Patrice Duroux a écrit :
> For the PKG-INFO file I just found it inside the .tar.gz available
> here where I
> am checking Python module:
> https://pypi.org/project/testpath/#files
> but may be I am wrong to check such a source. This repository is may
> be adding
> it then.

Well, pypi isn't upstream...

> Otherwise sure the new package is much better and fine to me, it was
> rather
> facts that aroused my curiosity.

No problem : feedback is helpful!

Cheers,

JP



sshuttle / python3.8

2019-12-11 Thread Brian May
Hello,

I have been informed that the sshuttle package, in Debian is most likely
completely broken under Python 3.8

https://github.com/sshuttle/sshuttle/issues/381

To me this looks like a regression in Python 3.8. but at the same time
sshuttle is possibly misusing(?) sockets in ways that were never
intended(?).

Unfortunately, even though I am upstream and Debian maintainer, I don't
have any time to look at this.

Help appreciated.

Thanks
-- 
Brian May 



Re: sshuttle / python3.8

2019-12-11 Thread Emmanuel Arias
Hello I am available to help.

Let me take a look.

Cheers,
Emmanuel

El mié., 11 de dic. de 2019 18:02, Brian May  escribió:

> Hello,
>
> I have been informed that the sshuttle package, in Debian is most likely
> completely broken under Python 3.8
>
> https://github.com/sshuttle/sshuttle/issues/381
>
> To me this looks like a regression in Python 3.8. but at the same time
> sshuttle is possibly misusing(?) sockets in ways that were never
> intended(?).
>
> Unfortunately, even though I am upstream and Debian maintainer, I don't
> have any time to look at this.
>
> Help appreciated.
>
> Thanks
> --
> Brian May 
>
>