[patch] Manipulator-aware admin validators are impossible

[Tom Tobin <korpios@…>]

Since magic-removal was merged, there has been no straightforward way to create a validator with the manipulator available to it (see ​this post on django-users for an example of how it might be done). Furthermore, it has been outright impossible to create such a validator for use in the admin; such validators were possible in pre-MR by prefixing the validator name with manipulator_validate.

The attached patch aims to restore such functionality by means of a simple, backwards-compatible API change: if the validator takes three arguments, rather than the standard two (i.e., field_data and all_data), the manipulator will be passed in as the first argument. The patch uses currying to accomplish this, and accounts for all the various types of callables that might be used (methods, callable class instances, etc.).

[Tom Tobin <korpios@…>]

Implements manipulator-aware validators in post-MR.

[Malcolm Tredinnick]

Decreasing the priority on this one for now. Since the Great Manipulator Redesign project seems to be gathering steam again on the developers' list, this patch should be unnecessary.

[Adrian Holovaty]

Closing this because manipulators have been replaced with the newforms library.