-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello all!
Pywikibot finished GIT migration. Now a question has anybody ever
tryed to clone and use the e.g. the pywikibot/compat repo on the TS?
If I do, I get and .git folder of about 200MB which nearly fills my
home quota. (this is the plain clone - nothing done to/with it yet!!)
Yes I could do 'git gc' I could also switch to using SVN from github
(but needs to handle all externals manually)...
So... what was acutally the reason for switching to GIT? Despite the
fact that I have to enter about 1 million different commands now (in
SVN I needed 5 ... maybe 10 - 1 command per action, in GIT I need
about 5-10 command PER action) I am dealing 75% of my time with GIT
issues (that SVN did not have)...
In fact I am not able to to USE or further develop the GIT repo since
the migration - and I am SERIOUSLY thinking about setting up an own
copy on sf.net again and work there... (then we would also have the
bug-tracker back in the same place) At the moment I see just 2 drawbacks:
1.) not hosted by mediawiki (really a drawback?)
2.) no review (this is the one and only advantage of git till now, and
in fact it's git-review which causes issues too)
The list of advantages on the other side, is that long that I will not
even start making one, think of it yourself and please give me some
feedback!
At least I do not see if there will ever be a point in time when GIT
will start to work as well as SVN did in the past. I do also not see
why I have to enter 5 commands just to make a simple commit. And that
will never change...
Thanks for your thoughts and Greetings
DrTrigon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlIGBzQACgkQAXWvBxzBrDC40gCeNt8b7KoBLV9BDNDojjM01Upp
ZsEAoIQIJ7W1FGMNysOE7LIp4qi25pyW
=mvrX
-----END PGP SIGNATURE-----
----- Original Nachricht ----
Von: Merlijn van Deen <valhallasw(a)arctus.nl>
An: Pywikipedia discussion list <pywikipedia-l(a)lists.wikimedia.org>
Datum: 11.08.2013 12:51
Betreff: Re: [Pywikipedia-l] Code review in gerrit
> On 11 August 2013 12:48, Merlijn van Deen <valhallasw(a)arctus.nl> wrote:
>
> > I'm not really sure though how you can do this under windows easily, as
> > tortoisegit doesn't seem to have any git-review capabilities...
> >
> > http://wiki.typo3.org/Contribution_Walkthrough_with_TortoiseGit seems to
> be a guide that explains how to do gerrit with TortoiseGit.
>
Thanks a lot for this hint, Merlijn. I had really given up to contribute any patches to the new repository. Now can I use tortoisegit for windows and I do not need to have git-review installed which fails while missing distutils package and some other problems occured while trying to connect gerrit.
Anyway I will write a small HOWTO.
Best
xqt
----- Original Nachricht ----
Von: Merlijn van Deen <valhallasw(a)arctus.nl>
An: Pywikipedia discussion list <pywikipedia-l(a)lists.wikimedia.org>
Datum: 10.08.2013 16:13
Betreff: Re: [Pywikipedia-l] Code review in gerrit
> On 2 August 2013 08:52, <info(a)gno.de> wrote:
>
> > Ok (or to bad). I am just for a tool stuff reminder for "this part of
> code
> > has still remaining bugs" (fixme) and when it is solved mark it as
> solved.
> > I assume we must use the bug tracker for that which is not very
> comfortable
> > (at least of the last changes at sf ihmo).
> >
>
> I think the basic workflow would be to fix those bugs before merging the
> code. Of course, it could be possible one would want to merge code that is
> not perfect yet, but keeping that in a bug I think would be better. In my
> experience the best part about the post-commit code review was getting
> comments on your work, which you then could fix - but now we can do this
> before even merging the code! :-)
>
> Merlijn
>
Yes I aggree with pre-commit code review. But there also could be remaining bugs after the code was pushed and identified to that code. Anyway I've additional questions to that gerrit workflow:
1st: Is there any way to download these patches for review purposes and merge it to the working copy. It is very uncomfortable do do that by hand and in some cases it is necessary to test the code snippets and not only read it.
2nd: What is the meaning of the scorings "verified" vs. "Code-Review"
Thanks
xqt
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello Merlijn
I heard something about your experiments with a SVN2GIT tool or
solution? May I ask what the status there? What about that?
Thanks and Greetings
DrTrigon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlIGHwgACgkQAXWvBxzBrDCwigCfVi9zsUA2mrexLK8hnMs0jRmC
YuwAn3dXkYJttCNn3R1loGvnZRbs+dHs
=esVt
-----END PGP SIGNATURE-----
Hi folks,
is there any posibility reviewing code _after_ it has been merged as it was before we went to git/gerrit like the mw cr special page. Or us the bug tracker the only remaining way to do it?
Greetings
xqt
I have written the following script:
# -*- coding: utf-8 -*-
import pywikibot
site = pywikibot.Site("gl", "wiktionary")
page = pywikibot.Page(site, u"𐌰𐌽𐌳𐌰𐌿𐍂𐌰")
print page.get()
It fails with the following output:
[gallaecio@afonso fontes]$ python2 test.py
Traceback (most recent call last):
File "test.py", line 7, in <module>
print page.get()
File "/usr/lib/python2.7/site-packages/pywikibot/__init__.py", line 249, in wrapper
return method(*__args, **__kw)
File "/usr/lib/python2.7/site-packages/pywikibot/__init__.py", line 249, in wrapper
return method(*__args, **__kw)
File "/usr/lib/python2.7/site-packages/pywikibot/page.py", line 278, in get
self._getInternals(sysop)
File "/usr/lib/python2.7/site-packages/pywikibot/page.py", line 302, in _getInternals
self.site.loadrevisions(self, getText=True, sysop=sysop)
File "/usr/lib/python2.7/site-packages/pywikibot/page.py", line 96, in site
return self._link.site
File "/usr/lib/python2.7/site-packages/pywikibot/page.py", line 3080, in site
self.parse()
File "/usr/lib/python2.7/site-packages/pywikibot/page.py", line 3037, in parse
u"contains illegal char(s) '%s'" % m.group(0))
pywikibot.exceptions.InvalidTitle: contains illegal char(s) '𐌰'
Hi,
I saw the existence of this script, and I would like have some informations about the parameters to use it. Does someone know it?
I saw for instance the parameter allrevisions, but is there a parameter to choose the page where we put the reults the page than
match the content)? Parameter for the regexp?
Thanks by advance for your answer
Hi,
\b in a regex treats letter "é" (which is a correct Hungarian letter) as a
word boundary.
Can I prevent this behaviour with some kind of settings?
--
Bináris
I would like to know two things:
• I want to implement a script to rename pages. Do you agree that implementing this feature within replace.py as an option would the the right approach, or should I create a separated script?
• What is the current procedure to provide patches (for the rewrite branch)? Reading http://www.mediawiki.org/wiki/Manual:Pywikipediabot/Development didn’t solve this doubt of mine. I see there is a Patches section in SourceForge, is that the right place?
Hi,
I've found yesterday, that there are some wrongly defined instances of
coordinate datatype in wikidata. For reference check [1].
I guess PWB works properly, but we should be more tolerant right now. For
me I've found some workaround:
diff --git a/pywikibot/__init__.py b/pywikibot/__init__.py
index 12bf9ec..b2044c9 100644
--- a/pywikibot/__init__.py
+++ b/pywikibot/__init__.py
@@ -163,10 +163,8 @@ class Coordinate(object):
globes = {}
for k in site.globes():
globes[site.globes()[k]] = k
-
- globekey = data['globe']
- if globekey:
- # FIXME: Should probably use get() with some error handling
when it
+ globes[k] = k
+ if 'globe' in data:
globe = globes[data['globe']]
else:
# Default to earth or should we use None here?
cheers!
[1]
https://www.wikidata.org/wiki/Wikidata:Project_chat#Coordinate_Datatype_mis…
--
Tomasz Magulski