> presumably, some Mailman upgrade removed the modification to HyperArch.py.
Is there some sort of best practice on how to avoid this situation? That
is, how to avoid modification of HyperArch.py through some Mailman upgrade?
best,
Peter
On Fri, Aug 21, 2015 at 4:59 PM, Mark Sapiro wrote:
> On
okay, sorry for the spam, but I already wrapped my head around how to
change the date format.
just use python's functionality to parse it into a different string.
for instance: 'date': datetime.datetime.strptime(article.datestr, "%a, %d
%b %Y %H:%M:%S %z").strftime("%d %b %Y %H:%M:%S"),
best,
Pet
okay, my admin forgot to restart the service. the dates are now working
again!
one more question: how/where can I format the string?
right now it looks like this: "Mon, 24 Aug 2015 14:18:21 +0200"
I would like the following: "24 Aug 2015 14:18:21"
Thanks and best,
Peter
On Fri, Aug 21, 2015 at 4
thanks for the help.
what do I have to do after editing Mailman/Archiver/HyperArch.py as
suggested by you? Or: How can I test, if the changes actually changed
something?
Because right now, I added your changes and sent a testmail to the list.
The mail gets added to the archive, however, the date s
On 08/21/2015 02:29 AM, Peter Wetz wrote:
> On the archive page of my mailman list the dates are not showing up
> properly. It looks like this: http://i.imgur.com/IrmWnie.png
>
> As you can see, instead of the date a string "%(date)s" is shown. It is
> also worth noting, that it already worked pro
On the archive page of my mailman list the dates are not showing up
properly. It looks like this: http://i.imgur.com/IrmWnie.png
As you can see, instead of the date a string "%(date)s" is shown. It is
also worth noting, that it already worked properly. However, suddenly (at
least I cannot state wh
