Hi
I use Python frecuently, and today I start working with pywikipediabot, wich is a very good library, by the way.
But I think that the workflow is very out-of-the-python-way. I explain my point:
To make a script that uses this environment, you need to put the code on the main directory of pywikipediabot, or do some links to that directory. But usually, when you use a third-party module on Python, you should have the chance to "install" the module and load it with a simple
import pywikipediabot
or
from pywikipediabot import wikipedia
And doing thins on any directory on your system, without any extra configuration or needed files. I think this could be a nice feature, because it respects the python-way, and gives the chance to distribuite the module much more easier using 'distutils'[1] or even Debian packages
[1] http://docs.python.org/distutils/index.html
Regards, Pablo Recio
Hello,
2010/3/16 Pablo Recio Quijano rikutheronin@gmail.com:
Hi
I use Python frecuently, and today I start working with pywikipediabot, wich is a very good library, by the way.
But I think that the workflow is very out-of-the-python-way. I explain my point:
To make a script that uses this environment, you need to put the code on the main directory of pywikipediabot, or do some links to that directory. But usually, when you use a third-party module on Python, you should have the chance to "install" the module and load it with a simple
import pywikipediabot
or
from pywikipediabot import wikipedia
And doing thins on any directory on your system, without any extra configuration or needed files. I think this could be a nice feature, because it respects the python-way, and gives the chance to distribuite the module much more easier using 'distutils'[1] or even Debian packages
You are right. pywikipedia was at first a collection of user-script, and users started to factor and gather together common procedures. Its current architecture has many, many flaws. A few "crazy" people (Russell, me, some others?) do not use anymore the trunk/ version of pywikipedia, but the rewrite/ branch. The rewrite only uses the MediaWiki API to edit and retrieve data, and is structured as a normal Python module with submodules. It even, oh magic, includes some tests.
The original idea was to abandon trunk/ to use the rewrite, but we lack manpower and (at least for me) time to actually do the conversion work of all existing scripts. But I know for a fact that code is working, and cleaner. Please give it a try :)
Regards,
[1] http://docs.python.org/distutils/index.html
Regards, Pablo Recio
Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l