Marco van Tol writes: > I tried this, and everything works fine with the last version of my script, > except for one sort-of minor thing,
Please don't deprecate your requirements. If you need it, and you do: > It would be a minor thing if I hadn't told people this is the way to find > out the number of messages in a list, and also to find the most recent post > to a list. we want to give it to you. Sure, sometimes it is harder than you imagine or in our judgment it's not worth as much as something else we could do, but you needn't be shy about asking for it. I'm also pretty sure it's hardly a unique requirement, at least it won't be for long, between GDPR and other worries about privacy of archived data in many contexts. > [And what's not working right is] the message count if you search > for "*". It won't update to the right message count in the top > middle of the page until I do a "rebuild_index". How much does time does cost to do that? If it's expensive enough that on "monthly cleaning day" you've got some lists that stay unsynced for many minutes or hours, we might need to rearchitect the index to be per list. > I'm afraid "update" index only looks at the messages changed since the last > time update was run, and misses the fact that messages have disappeared > from the beginning. Have you looked at the code to verify this? I agree it's consistent with the Mailman behavior you see. Unfortunately I'm not sure that all the indexers we claim to support would be able to suppose such deletions without a full rebuild. Steve _______________________________________________ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
