Re: pylint3 reverse dependencies.
> Yes this is a known issue and we are currently waiting for an upload > of dh-python to avoid automatic replacement of pylint by pylint3 when > on python3 before pushing those changes further. http://ftp.debian.org/debian/dists/unstable/main/Contents-amd64.gz still contains pylint3 so I'm waiting with an dh-python upload for now -- GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
Re: [Python-apps-team] pylint3 reverse dependencies.
Piotr, please do not hold onto the upload - the reason is still there it's because it's a cruft package, which will be removed once we fix dh-python and make pylint conflict with pylint3 (instead of just provide it), which we currently cant do due to dh-python still producing the pylint3 dependency. On Fri, Oct 4, 2019 at 5:42 AM Piotr Ożarowski wrote: > > > Yes this is a known issue and we are currently waiting for an upload > > of dh-python to avoid automatic replacement of pylint by pylint3 when > > on python3 before pushing those changes further. > > http://ftp.debian.org/debian/dists/unstable/main/Contents-amd64.gz > still contains pylint3 so I'm waiting with an dh-python upload for now > -- > GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 > > ___ > Python-apps-team mailing list > python-apps-t...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-apps-team -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
Packaging a new Python library
Hi, I would like to package this Python library that is not yet in Debian: https://github.com/peterbe/premailer as a new version of the cppreference-doc package that I maintain has it as a build dependency. What would be the best organizational approach to do that? I could maintain the premailer package myself, but given the fact that many packages are maintained as part of the Python modules team, should I join the team and create the package under the team's umbrella? Regards, Povilas
Re: Packaging a new Python library
El vie., 4 de oct. de 2019 a la(s) 18:00, Povilas Kanapickas (povi...@radix.lt) escribió: > > Hi, > > I would like to package this Python library that is not yet in Debian: > https://github.com/peterbe/premailer as a new version of the > cppreference-doc package that I maintain has it as a build dependency. > > What would be the best organizational approach to do that? I could > maintain the premailer package myself, but given the fact that many > packages are maintained as part of the Python modules team, should I > join the team and create the package under the team's umbrella? Hello, Yeah from my point of view I think would be great create the package under team's umbrella. Will be easy get help and feedback from the team :-) Cheers > > Regards, > Povilas >
