Bug introduced at changeset 4500

[Rudolph]

Hi,

I think I found a bug introduced in changeset 4500 (http://
code.djangoproject.com/changeset/4500). When a min_num_in_admin is
specified without a num_in_admin, the "add" view in the admin
interface gives an exception (and possibly the change view as wel, I
didn't test that). Does anyone else experience this since changeset
4500?

Rudolph

[Malcolm Tredinnick]

I did some testing before committing that change, but I may have missed
this case. I'll have a look at it when I get a chance this morning and
fix it if I can track down the problem.

Thanks for the heads-up and apologies for costing you some time.

Regards,
Malcolm

[Rudolph]

On Feb 15, 10:53 pm, Malcolm Tredinnick <malc...@pointy-stick.com>
wrote:

No apologies needed, it's the trunk version after all. Thanks in
advance for your time to correct it.

Rudolph

[Malcolm Tredinnick]

On Thu, 2007-02-15 at 06:02 -0800, Rudolph wrote:

After a fair bit of head scratching and chasing code paths, I think I
managed to fix this in the correct way. The update is in revision r4542.
The problem hadn't ever shown up before because we weren't correctly
handling min_num_in_admin > num_in_admin cases prior to r4500.

Regards,
Malcolm

[Rudolph]

On Feb 19, 5:20 am, Malcolm Tredinnick <malc...@pointy-stick.com>
wrote:

> After a fair bit of head scratching and chasing code paths, I think I
> managed to fix this in the correct way. The update is in revision r4542.
> The problem hadn't ever shown up before because we weren't correctly
> handling min_num_in_admin > num_in_admin cases prior to r4500.
>
> Regards,
> Malcolm

Thanks, I'll test my problem and let you know the result.

Regards,

Rudolph