Bug#896557: ITP: python-django-nocaptcha-recaptcha -- Google No CAPTCHA reCAPTCHA widget for Django forms
Package: wnpp Severity: wishlist Owner: Alexandros Afentoulis X-Debbugs-Cc: debian-de...@lists.debian.org, debian-python@lists.debian.org * Package name: python-django-nocaptcha-recaptcha Version : 0.0.20 Upstream Author : Imaginary Landscape * URL : https://github.com/ImaginaryLandscape/django-nocaptcha-recaptcha * License : BSD Programming Lang: Python Description : Google No CAPTCHA reCAPTCHA widget for Django forms This python module allows creating Django forms with Google's "No CAPTCHA" reCAPTCHA or reCAPTCHA version 2. This is the only available reCAPTCHA since Google switched off version 1 in March 2018. This package is not a dependency for others, its building dependencies are already satisfied and has no running dependencies to other python modules. I already have a working debian package, tested against oldstable and Django 1.8. I plan on git pushing the repository on salsa as soon as possible. I will need a sponsor to upload that package and I would certainly maintain it within a team if that's more appropriate.
Re: Testing Django Packages, was: Re: [Python-modules-team] Bug#896429: python3-django-tables2: django_tables2 fails to import
On 04/21/2018 11:10 PM, Scott Kitterman wrote: > I believe we could benefit from more documentation and perhaps tools to make > it easier to integrate tests for Django modules. > > Scott K I agree, and it would be nice to have it within within the python-django-common package, so one could use it for tests. Cheers, Thomas Goirand (zigo)
Profile-guided optimisation / link-time optimisation in Buster
I noticed that profile-guided optimisation and link-time optimisation have both been unconditionally disabled in Buster's Python 3.6 and 3.7 packages, though 3.5 in Stretch had them both enabled (on common platforms). Can anyone tell me why this was done? I see nothing about this in debian/changelog and the indentation in debian/rules looks odd, so I'm wondering if it might even have been an unintentional change. It's these extra lines in debian/rules: with_pgo = with_lto = just before the ifeq ($(with_lto),yes) line. -M-
