0700 was changed previously to 0600 in rPWBC049cd8a7 due to T206385.

Um

Don't know what the right word would be. You cannot edit it like a wiki but you have to change the code repository where the documentation resides.

T118724 must be solved first to implement this kind of sorting

This patch solves this task in most cases except there are threads added on top or in the middle of a talk page.

In T314560#8132550, @whym wrote:

Is this the same as T312773?

No, although the two may achieve similar results. The method described here will preserve whatever the original order was, while the other task's case the bot will rearrange threads by first posts in threads. (Thank you for working on it, by the way!)

@whym: Is this the same as T312773?

In T312992#8118540, @KBach wrote:

@Xqt thanks! I have it on my list. I'll be looking into these pages this week.

Please take into account that most of the documentation is autogenerated and Xsan be found at https://doc.wikimedia.org/pywikibot/master/

There is a remaining upstream issue:
https://github.com/PyCQA/flake8/issues/1629

There is a similar problem when maxarchivesize = 0T
https://test.wikipedia.org/w/index.php?title=User_talk:Ignocrates&action=history

Stable release 7.5.2 is published, I updated the table above. Use pwb.py version to verify the release. It should be either 7.6.0.dev2 or 7.5.2.

In T313785#8105420, @MarcoAurelio wrote:

Hello @Xqt. By reading the above I see it's safe to continue to run the script, right?

This depends on whether you are using the stable or master release.
Just run pwb.py version. For me it gives:

In T313785#8105161, @PotsdamLamb wrote:

Ok, so what will be the impact going forward? Will the stable version change the variable on wiki when released, or will it leave it as %d? I just need the solid answer as our BC wants to know before I can do more trials as it changed everyone's from d to s.

Yes, it will change all "d" to "s" on-wiki in the future due to.........

No, it will not change the "d" to "s" on the wiki, so there will be no issues, including backward compatibility.

Thanks.

See the table above.

• Running the current master (7.6) will do no changed from %d to %s when find a %d field except for the new fields
• Running the current stable (7.5.1) will change from %d to %s when find a %d field
• Running older release 7.5 will always fail when find a %d field
• Running older release 7.4 and below will always fail on several wikis when find a %d field
• Running any release will never fail and no template changes are made when find a %s field
• %s fields are backward compatible and upward compatible
• new local fields are not backward compatible
• The current master will become stable in August I guess

You can also run the master branch on toolforge. There is no impact to convert fields from %d to %s. The master branch is the development fork. It is merged to the stable branch roughly every month.

It should leave it as %d or it breaks backwards compatibility.

Having %s instead of %d does not break anything because %s can work with any python types whereas %d accepts real numbers only.

master is rPWB517de0a and stable is 7.5.1 on toolforge.

Seems you are using the preinstalled stable release somehow. This should change in few hours to 7.5.1. I am afk and cannot check it now.