Hi.
I pulled from git the compat version and I got these errors when trying to
get pages from en, wikisource.
Getting [[Category:Author pages linking to Wikipedia]] list...
Getting 125 pages from wikisource:en...
WARNING: Missing namespace in family file wikisource: namespace['en'][114]
(it is set to 'Translation')
WARNING: Missing namespace in family file wikisource: namespace['en'][115]
(it is set to 'Translation talk')
I guess these namespaces need to be added to wikisource_family.py
BTW, I operate MpaaBot on en:WS based on pywikipediabot. I have some python
knowledge (but I'm not a professional developer) and would be nice to
contribute to this project in my spare time. Any advice on where/how one
could help? If I am welcome, you could list areas where you need help, and
I could pick what is more suitable for my knowledge level and interest.
Bye
Mpaa
Could anyone explain this message please. I tried to push some changes on family files to core but it hanged until I aborted the pushing. I did not found these changes on Gerrit. How to proceed in that matter?
Greetings
xqt
----- Ursprüngliche Nachricht -----
Von: Travis CI
Gesendet: 02.09.2013 19:38
An: info(a)gno.de
Betreff: [Errored] wikimedia/pywikibot-core#114 (master - 5105954)
The build has errored.
Repository
wikimedia/pywikibot-core
Build #114
https://travis-ci.org/wikimedia/pywikibot-core/builds/10902770
Changeset
https://github.com/wikimedia/pywikibot-core/compare/da3542c8738c...5105954b…
Commit
5105954 (master)
Message
update language_by_size from compat
Change-Id: Iffcfb52295a5bedda4c4748bd380ffda3a1343ff
Author
xqt
Duration
10 minutes and 25 seconds
You can configure recipients for build notifications in your configuration file. Further documentation about Travis CI can be found here. For help please join our IRC channel irc.freenode.net#travis.
Want Travis CI for your private repositories?
Powered by
img { margin-right: 16px !important; }
Hi everybody!
I just set this patch: https://gerrit.wikimedia.org/r/83372
It's final resolution of BeautifulSoup problem. Out of some options, I
chose maintaining by hand. Why? let's take a look at the options:
1- using BS4 as an external submodule directly from their version control
system: unfortunately it's not possible because BS is using Bazaar So we
can't make a an exact mirror beside of that the launchpad version is not
stable and they have an stable release once a while
2-using BS4 as an external from git clones: the clones in GitHub are
totally maintaining by hand and are out of date, (really out of date like
updated two years ago)
3-Make people to download and install BS: there is no need to explain why
this is not a good option
4-Copying from the stable release and maintaining by hand: We have to
update this codes once a while but we are maintaining name of namespaces in
Wikipedia projects by hand, so It won't bother me (as a dev) so much and
it's more available and more easier for users
I talked about this problem with some of BS devs:
https://groups.google.com/forum/?fromgroups#!topic/beautifulsoup/AoV_ao9Hrvg
Any suggestion, idea, anything! is welcome!
Best
--
Amir
Hi,
with the recent switch to HTTPS by default [0] I'm wondering if it still
makes sense to keep httplib2 (the upstream version, not the one
maintained at [1]) as a dependency in setup.py?
According to setuptools' documentation [2] the effect of listing
httplib2 (or any other dependency) in install_requires is that
When your project is installed, either by using EasyInstall, setup.py
install, or setup.py develop, all of the dependencies not already
installed will be located (via PyPI), downloaded, built (if necessary),
and installed.
For PWB this means that installing the project via `setup.py install` in
an environment where [1] is not already installed, setuptools will
download httplib2 from PyPI. This is not a good idea because all it will
do is give people an httplib2 that can't verify Wikimedias certificate.
AFAIK the only way to recognize this is during the install step - and
let's be honest - nooes reading *all* of the output ;)
I did try adding depency links as described by [2]:
dependency_links=[
'git+https://git.wikimedia.org/git/pywikibot/externals/httplib2.git#egg=http…'
],
but surprisingly, this only works with pip but not setuptools itself
('git+https' is an unknown url type to setuptools).
So it seems to me that specifying httlib2 as a dependency in setup.py
does more harm than good and it should be removed - [3] already lists
the submodule as a dependency, although it could be made more clear that
the git submodule differs from upstream.
As I'm not really that familiar with the python packaging ecosystem, I'm
not sure if there's a way to make (for example) the dependency links
stuff work or if the dependency is worth keeping for some other reason.
If there are no objections/other ideas to make this work, I'd submit a
patch removing the dependency from setup.py reusing most of this mail as
the commit message.
[0] https://git.wikimedia.org/commit/pywikibot%2Fcore.git/6bb502983afc93b4222d3…
[1] https://git.wikimedia.org/summary/?r=pywikibot/externals/httplib2.git
[2] http://pythonhosted.org/setuptools/setuptools.html#declaring-dependencies
[3] https://www.mediawiki.org/wiki/Manual:Pywikipediabot/Installation#Manual_.2…
--
Wieland
----- Original Nachricht ----
Von: Jeremy Baron <jeremy(a)tuxmachine.com>
An: Pywikipedia discussion list <pywikipedia-l(a)lists.wikimedia.org>
Datum: 05.09.2013 18:57
Betreff: Re: [Pywikipedia-l] Git error message
> On Sep 5, 2013 12:44 PM, <info(a)gno.de> wrote:
> > Jeremy, I did some pushes which where done without any problems. Then I
> sometimes get that messages. I deleted the clones several times and started
> a new try over and over again. But I did not found the point. Really I am
> tired with that stuff. Could we get svn back please.
>
> so then maybe you don't have the hook installed at all. it must be
> reinstalled every time you reclone.
Yes, I always did it after cloning
>
> > git bash doesn't work with refs/for/master review because it seems to
> redirect it to refs/refs/for/master. Obmitting refs/ creates a new
> directory /for/master. I'ts very strange.
>
> Well I don't have Windows here and don't have much free time through the
> end of the weekend but I would love to dig into that more. You should bring
> these issues first to IRC when you encounter them; there's usually someone
> around to help. (I'll be back on Monday and feel free to highlight me then.
> (e.g. say 'jeremyb' in #pywikipediabot on freenode))
>
I played a bit with git and could push some changes after the following try:
$ git pull "origin" master
>From ssh://gerrit.wikimedia.org:29418/pywikibot/compat
* branch master -> FETCH_HEAD
Already up-to-date
$ git pull --rebase
There is no tracking information for the current branch.
Please specify which branch you want to rebase against.
See git-pull(1) for details
git pull <remote> <branch>
If you wish to set tracking information for this branch you do so with:
git branch --set-upstream master origin/<branch>
$ git push
warning: push.default is unset; its implicit value is changing in
Git 2.0 from 'matching' to 'upstream'. To squelch this message
and maintain the current behavior after the default changes, use:
git config --global push.default matching
To squelch this message and adopt the new behavior now, use:
git config --global push.default upstream
See 'git help config' and search for 'push.default' for further information.
Counting objects: 10, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (6/6), done.
Writing objects: 100% (7/7), 878 bytes, done.
Total 7 (delta 3), reused 0 (delta 0)
remote: Resolving deltas: 100% (3/3)
remote: Processing changes: closed: 2, refs: 1, done
To ssh://xqt@gerrit.wikimedia.org:29418/pywikibot/compat
f9f28e8..b1b0531 master -> master
# with this command the last push was merged without any review [1]
# but afterwards I could push a new commit which I tried before without success: [2]
tortoisegit git commit [ammend last commit]
tortoisegit push master -> refs/for/master
Awaiting the next failure.
Best regards
xqt
[1] https://gerrit.wikimedia.org/r/#/c/82256/
[2] https://gerrit.wikimedia.org/r/#/c/83068/
Hi all,
I have just merged a change[1] into core which introduces a breaking change
to reading sources when using an ItemPage. The change now parses
multi-claim sources properly (example[2]). If you are simply adding
sources, this won't affect anything.
If you are reading sources, Claim.sources is a list of dictionaries. Each
dictionary is a "source", and is organized just like claims are currently
stored in an ItemPage.
Thank you to FelixReimann for taking the time to quash this bug and for
some of the other great work he's been doing!
[1] https://gerrit.wikimedia.org/r/#/c/81219
[2] https://test.wikidata.org/wiki/Q7
--Legoktm
FYI, maybe something Pywiki developers should go too?
-------- Origineel bericht --------
Onderwerp: [Wikitech-l] Fwd: Wiki DevRoom at FOSDEM?
Datum: Wed, 04 Sep 2013 15:29:40 -0700
Van: Quim Gil <qgil(a)wikimedia.org>
Antwoord-naar: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
Organisatie: Wikimedia Foundation
Aan: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
I have contacted some wiki projects sending them the email below. If you
know good contacts out there please forward this invitation to them.
The FOSDEM organizers replied back saying that they preferred a
cross-project Wiki devroom. The more and more diverse support we get,
the better chances we will have to get the devroom proposal accepted.
... and if you want to help defining the proposal you are of course
invited too. I'll start drafting tomorrow.
-------- Original Message --------
Subject: Wiki DevRoom at FOSDEM?
Date: Wed, 04 Sep 2013 15:06:28 -0700
From: Quim Gil <qgil(a)wikimedia.org>
Organization: Wikimedia Foundation
To: qgil(a)wikimedia.org
Dear wikicolleague(s),
The Wikimedia/MediaWiki community is planning to propose a DevRoom for
FOSDEM (Brussels, February 1-2, 2014).
https://fosdem.org/2014/news/2013-08-06-call-for-participation/
The FOSDEM organizers promote cross-project devrooms and we think it is
a good idea as well. There is no lack of wiki projects and wiki topics
to present and discuss!
I'm coordinating the elaboration of the proposal from the Wikimedia
side. Deadline: 15 September. I will start drafting it at
https://www.mediawiki.org/wiki/Events/FOSDEM tomorrow, but first I
wanted to contact several projects seeking support and eventually
collaboration.
What we need:
* If you are interested, please give explicit support to this DevRoom on
behalf of your project.
* If you are quite interested, watch and edit the proposal.
* If you are really really interested and you will have the time, step
in to co-coordinate the DevRoom.
There are no more details so far. Following TheWikiWay ;) I decided to
start contacting you before getting too deep into the planning.
Let me know if you are interested!
Best regards,
--
Quim Gil
Technical Contributor Coordinator @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
----- Original Nachricht ----
Von: Jeremy Baron <jeremy(a)tuxmachine.com>
An: Pywikipedia discussion list <pywikipedia-l(a)lists.wikimedia.org>
Datum: 05.09.2013 18:21
Betreff: Re: [Pywikipedia-l] Git error message
> On Sep 5, 2013 11:58 AM, "Chad Horohoe" <chorohoe(a)wikimedia.org> wrote:
> > Offhand, my guess would be that the commit-msg hook isn't platform
> > independent and is giving you problems on Windows. As a workaround,
> > you can amend your latest commit on master (git commit -a --amend)
> > and copy+paste that suggested Change-Id into the message.
>
> or the hook was installed in the wrong place or has the wrong perms?
> (execute bit?)
>
> or maybe it's the environment. try using git bash? or else just ditch
> windows!
>
> -Jeremy
Jeremy, I did some pushes which where done without any problems. Then I sometimes get that messages. I deleted the clones several times and started a new try over and over again. But I did not found the point. Really I am tired with that stuff. Could we get svn back please.
git bash doesn't work with refs/for/master review because it seems to redirect it to refs/refs/for/master. Obmitting refs/ creates a new directory /for/master. I'ts very strange. Ok maybe it's windoof. But it's the only ability for all my other development software. I should ask a wikimedia chapter for some sponsoring. Sorry please, my patience is running out. I should leave that time consuming issue and cook my own soup (would be beautiful ;)
Thanks and greetings
xqt