Currently, the "Version" field of our bugs can only be set to one of
"compat (1.0)", "core (2.0)" or "unspecified".
Why not to create a new "both" option to explicitly indicate that the
bug is valid for both versions?
So, "unspecified" would only mean that the bug has not been tested on
both versions.
(Ideally, the "version" field should consist of two checkboxes, one for
each version.)
This is not a bug in testing. The test detects a bug for archivebot.py which fails for unsigned threads.
xqt
----- Ursprüngliche Nachricht -----
Von: John Mark Vandenberg
Gesendet: 26.07.2014 18:21
An: Pywikibot discussion list
Betreff: Re: [Pywikipedia-l] The build is broken
On Sat, Jul 26, 2014 at 10:39 PM, Ricordisamoa
<ricordisamoa(a)openmailbox.org> wrote:
>
> The build is still broken, but because of this edit, that breaks the timestamp detection of the ArchiveBot.
> Maybe a fictitious, write-protected talk page should be used?
That is being tracked on
https://bugzilla.wikimedia.org/show_bug.cgi?id=67663
An alternative test page would be a good solution.
Or maybe the unit test could allow unsigned sections to be added to
the talk page.
--
John Vandenberg
_______________________________________________
Pywikipedia-l mailing list
Pywikipedia-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
Are we going to have a 'scripts' repository (see bug 64871
<https://bugzilla.wikimedia.org/show_bug.cgi?id=64871>), really?
Pros:
* the size of the package would decrease dramatically (more than half
of the overall), becoming a cleaner environment for experienced
users who only run their own scripts;
* we could move most scripts to subdirectories without running into
maintainability issues.
Cons:
* Gerrit patches that change both scripts and core files would have to
be split in two;
* less experienced users (who often use the bundled scripts) would
have to fetch dependencies.
I remember that in compat we have a function named "getAll" or something
like that which will retrieve content of pages at once. Although in core we
have parameter "content" in most functions, it is possible that we want to
get content of pages which are irrelevant to each other (and therefore we
can't use existing functions). Should we port this function to core, then?
--
Sorawee Porncharoenwase
How can I request new components for the product "Pywikibot" in Bugzilla?
They would be extremely useful, especially for very used scripts like
textlib.py.
pywikibot/__init__.py contains the following lines:
from pywikibot.textlib import *
from pywikibot.i18n import translate
Are we supposed to always use pywikibot.translate() instead of
i18n.translate()? (actually, I did the opposite
<https://gerrit.wikimedia.org/r/136609>)
Or pywikibot.replaceExcept() instead of textlib.replaceExcept()?
If not, can we recommend to always use from pywikibot import textlib?