On 20 June 2014 23:03, Barry Warsaw wrote:
> >python3-django-captcha
>
> +1
>
> can-never-have-enough-python-3-ly y'rs,
>
I woke up and realized that I can't do a python3-django-captcha just yet,
without a python3-django package.
Have made a start here, may try some more tomorrow, if I get time
On Jun 20, 2014, at 12:06 PM, Brian May wrote:
>My latest thought is maybe I should rename to:
>
>python-django-captcha
>
>and create:
>
>python3-django-captcha
+1
can-never-have-enough-python-3-ly y'rs,
-Barry
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject
Le 20 juin 2014 01:23, "Brian May" a écrit
:
>
> Hello,
>
> Just noticed that Olivier Sallou did a new upload of python-captcha
recently, so presumably this means there is some interest in keeping
python-captcha in Debian. Have CCed him in case he can offer any opinions.
Hi
Python-captcha is a dep
On 20 June 2014 11:48, Scott Kitterman wrote:
> This isn't necessarily fatal. See python-dnspython (provides the dns
> module)
> and python-dns (provides the DNS module). Sine python-captcha is already
> used, I'd recommend picking an alternate name for your package. Since
> python
> module na
This isn't necessarily fatal. See python-dnspython (provides the dns module)
and python-dns (provides the DNS module). Sine python-captcha is already
used, I'd recommend picking an alternate name for your package. Since python
module names are case sensitive, this thing can happen and we shou
Hello,
Just noticed that Olivier Sallou did a new upload of python-captcha
recently, so presumably this means there is some interest in keeping
python-captcha in Debian. Have CCed him in case he can offer any opinions.
Thanks.
On 5 May 2014 09:58, Brian May wrote:
> Hello,
>
> Debian has the
On 6 May 2014 03:49, Christophe Siraut wrote:
> In this case we can probably name the source django-simple-captcha even
> if the policy states it should be python-captcha. Note I have seen
> django modules were source and package name are the same [1], it is not
> clear to me what the best naming
On 6 May 2014 03:49, Christophe Siraut wrote:
> In this case we can probably name the source django-simple-captcha even
> if the policy states it should be python-captcha. Note I have seen
> django modules were source and package name are the same [1], it is not
> clear to me what the best naming
Hi,
Brian May wrote:
> Technically speaking, the module names don't conflict, this is only because
> of the case of the first character is different, which IMHO isn't
> sufficient. Also policy would require me to package django-simple-captcha
> as python-captcha, which would clash.
In this case w
9 matches
Mail list logo
