Manual:Pywikibot/Development

How to report a bug
When you report a bug please try to include:


 * Pywikipediabot version in use. It's recommended to test if the bug is still present in latest Git revision available.
 * Python version (python -V) and operating system you use (e.g. Windows, Linux, MacOS...)
 * For above purpose, version.py will be useful.
 * A nice summary
 * Full description of the problem/report
 * How to reproduce bug full information (script, command line, family, and language used)
 * The console output provided by the script (included the Python traceback if you are reporting a crash)

To submit a new bug visit the bug tracker provided by SourceForge.

Development
If you have a function you want to have a bot for that is not yet provided by one of the bots, you can ask one of the programmers to write it for you. Or even better, you can try to work on the bots yourself. Python is a nice language, and not hard to learn. We will welcome you.

Commit access
To request commit access, first email the mailing list and explain what you'd like to work on. Once you've gotten a little community consensus that you should get access, submit a formal commit access request and mention that you'd like pywikipediabot commit access, and point to the mailing list thread where you got an OK from the pywikipediabot community. Example.

Contributing changes
If you changed the bot and want to send a patch to the maintainer,
 * 1) Update to the current version (it will merge your changes with the improvements already committed to the SVN Repository),
 * 2) Resolve any conflicts caused by the update (grep for "=====" ;-) and
 * 3) Type:

Review the diff to ensure it only includes the changes you want to contribute. The lines at the beginning starting with "?" should be removed.

If you are in direct contact with a Pywikipediabot developer, you can send the file svn.diff to him, but preferably attach the patch to a ticket in the Pywikipedia bug tracking system.

Git
See this mailing list post if you would like to try Git instead of Subversion for source control. This github repo mentioned is quite dated, the best part is this git svn command: Note that this will take quite a while.

SVN
All prerequisites are the same as for Git access. Then checkout the code from wikimedia svn server by using your ssh account there: for trunk and for rewrite.

After that you can change the code and afterwards submit those modifications by a simple:

Bot & Proxy
There is probably (not tested!) draft workaround described here.