Missing a PasswordField for model and manipulation
|Reported by:||Owned by:||Adrian Holovaty|
|Component:||Database layer (models, ORM)||Version:||0.95|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
i can't seem to find anyone complaining about this, very strange...
maybe i'm getting this not-so-polite behaviour because of a mistake i made, anyway...
Shouldn't there be a PasswordField for models and manipulators? I was trying to register a user with an automatically generated form and i noticed that the passoword field is type=text. Then i noticed that the User model has a simple CharField as password. This calls for a PasswordField which does 2 things:
- translates into a type=password in html and validates accordingly (eg. not blank)
- automatically handles safe password storage (e.g. storing only the md5) instead of specifying separately like in the User model.