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 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 scheme is. Christophe 1. for example python-django-uuidfield
signature.asc
Description: Digital signature
