Bug#868665: ITP: python-asgiref -- ASGI in-memory channel layer
Package: wnpp Severity: wishlist Owner: Michael Fladischer -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: python-asgiref Version : 1.1.2 Upstream Author : Django Software Foundation * URL : https://github.com/django/asgiref/ * License : BSD-3-clause Programming Lang: Python Description : ASGI in-memory channel layer Contains various reference ASGI implementations, including: . * A base channel layer, asgiref.base_layer * An in-memory channel layer, asgiref.inmemory * WSGI-to-ASGI and ASGI-to-WSGI adapters, in asgiref.wsgi -BEGIN PGP SIGNATURE- iQFFBAEBCgAvFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAllsovARHGZsYWRpQGRl Ymlhbi5vcmcACgkQ/9PIi5l90WpNHQf7Bizo8KnRdfSO9CId2q6kDi/tGTdwlvDG 9XBPwGh5nhKKT/vjXA6gQOgpzPLXr3nke/ZmDSd1x3PiAchiO30dq9Vl/Ipolyjg xy3uBR53DNX2Uxuw43TqA0AAUWoSsOxbDHpcnIyBFzs49kBj+oQR3XClhKgr7fch aKu/BNhC1DpAp5TtKurMPn+4tDlLgIs9TTGEOKAG7iT1tWf0NyTCnRLEgv212L4p dJ1SQYMJlbDE8jhZk0TwKTE02mIS/DaBf6DArl0B5AtFTmdFHFLrLIETtTdqC8+D bfsR94UT1LzHlvPaHmVyp8YTi6yymh15Pg90PNu65R7wMlBHw6kX8A== =rV+h -END PGP SIGNATURE-
Re: python3 for pysrs
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 upstream is dead. I'll send upsteam also a mail with my propolsoal for pysrs python3, but I think I'll don't get response. But before asking upstream I would like to have somebody looking at my python3 changes if they are going into the right direction. > I think that porting a work to Python 3 is not appropriate for a Debian > patch. 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. Yes I know, that this is not really part of an Debian patch, but because upstream is not doing anything, I started now to push python3 support. And I think at this list there are many people how saw many python3 support patches, to give some hints, where to pay attention. Well if upstream is dead I'll need to fork it. Best Regards, sandro signature.asc Description: This is a digitally signed message part.
Re: python3 for pysrs
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 because upstream has not add any patch for three years, I think >upstream >is dead. I'll send upsteam also a mail with my propolsoal for pysrs >python3, >but I think I'll don't get response. But before asking upstream I would >like >to have somebody looking at my python3 changes if they are going into >the >right direction. > >> I think that porting a work to Python 3 is not appropriate for a >Debian >> patch. 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. > >Yes I know, that this is not really part of an Debian patch, but >because >upstream is not doing anything, I started now to push python3 support. >And I >think at this list there are many people how saw many python3 support >patches, >to give some hints, where to pay attention. >Well if upstream is dead I'll need to fork it. 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. My understanding is he views it as doing what it's supposed to do, so rather than dead, it's merely sleeping. In addition to email, you can usually find him on IRC at #spf on irc.perl.org. Scott K
