On May 18, 2013, at 5:15 AM, Aymeric Augustin
wrote:
> Apologies for answering so late. I see the change discussed here was already
> committed. The change itself is fine — essentially because it's limited to
> the bcrypt password hasher — but I'd like to
Apologies for answering so late. I see the change discussed here was already
committed. The change itself is fine — essentially because it's limited to the
bcrypt password hasher — but I'd like to bring some perspective to parts of
this discussion.
Overall, I strongly advocate consistency in
On May 11, 2013, at 4:10 AM, Claude Paroz wrote:
> Le samedi 11 mai 2013 07:59:18 UTC+2, Donald Stufft a écrit :
> I went looking for BCrypt + Django + Python3 today and this is what I found:
>
> The current recommended solution to bcrypt + Django is using py-bcrypt which
I went looking for BCrypt + Django + Python3 today and this is what I found:
The current recommended solution to bcrypt + Django is using py-bcrypt which is
not compatible with Python3.
Someone else has taken py-bcrypt and created py3k-bcrypt however they made the
decision to enforce having