-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01.09.2013 01:56, Mpaa wrote:
Hi.
My 2 cents ... on compat regarding the message about logging
handlers.
When no log is required, log.log(_level, text, extra=context,
**kwargs) in wikipedia.logoutput() actually has no handlers and no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I did not find any crash situation or bug to fix. I just tried to
understand what was the root cause of the missing logger
message, someone was complaining about. Which I described above
(always assuming it is the correct one ...).
Yes that's
2013/8/24 John phoenixoverr...@gmail.com
Another point that is really frustrating is the logging system that
complains about not having a logger defined if you run any custom scripts.
So this is the reason! I didn't understand why I suddenly got those strange
messages.
I have a dream: someday
logging should activated for those scripts listed in config.log list only.
Isn't it?
xqt
- Original Nachricht
Von: Bináris wikipo...@gmail.com
An: Pywikipedia discussion list pywikipedia-l@lists.wikimedia.org
Datum: 31.08.2013 18:08
Betreff: Re: [Pywikipedia-l] Cruft
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Compat/trunk never worked like this... I always (at least 5 years now)
checked out/cloned the current version - tested it a few days with my
bots, commited bug fixes if needed and then ran this code for about 6
months. After that period the same
. Isn't it?
xqt
- Original Nachricht Von: Bináris
wikipo...@gmail.com An: Pywikipedia discussion list
pywikipedia-l@lists.wikimedia.org Datum: 31.08.2013 18:08
Betreff: Re: [Pywikipedia-l] Cruft in compat
2013/8/24 John phoenixoverr...@gmail.com
Another
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I fully agree with Merlijn and Amir!
Though John is pointing us to some things we might have to pay
attention to:
(1) It shoudnt be querying git on every script invocation
Indeed you are right - this might be due to version.py imported in
See this:
http://sourceforge.net/p/pywikipediabot/bugs/1633/
The problem is we can't set all of patches for all of users. So many
people are not interested in running IRC bots or image handling bots,
so They don't need to download almost 100M for that
Best
On 8/24/13, John
I shoudnt have to set wikipedia.setLogfileStatus(True) in all my scripts
just because someone cant be bothered to implement their logging code
correctly.
Moving to pre-configred git sub modules would do the same thing, without
running exicutibles on windows computers. Just because someone
Wouldn't it be possible to implement some kind of plugin-strucutred addons
for those special cases where you have to download more, install more, do
more by yourself?
On Sun, Aug 25, 2013 at 11:34 AM, John phoenixoverr...@gmail.com wrote:
I shoudnt have to set wikipedia.setLogfileStatus(True)
We have done it recently:
you can read more in
http://www.mediawiki.org/wiki/Manual:Pywikipediabot/Installation
On 8/25/13, swuensch swuen...@gmail.com wrote:
Wouldn't it be possible to implement some kind of plugin-strucutred addons
for those special cases where you have to download more,
Hi John,
On 23 August 2013 00:36, John phoenixoverr...@gmail.com wrote:
The final straw was when I just converted to Git and discovered that he is
trying to run executables.
I think most of us agree using patch.exe was not the best decision.
However, creating a way to install dependencies
Another point that is really frustrating is the logging system that
complains about not having a logger defined if you run any custom scripts.
The only way that I have found to shut this up is to enable logging for all
scripts, however I end up with thousands of log files. (each pid creates
its
Ive been slowly getting more and more irritated by drtrigon's additions to
the code. The final straw was when I just converted to Git and discovered
that he is trying to run executables. This is bloatware plain and simple I
have seen the number of externals go from 2 to 17. Most of these are
14 matches
Mail list logo
