Go to file
2003-10-28 00:22:15 +00:00
docs Updated the class names for the table rows 2003-10-20 17:13:40 +00:00
examples Removed, since they're practically useless. No one's going to write their own conf files by hand. 2003-10-05 20:43:10 +00:00
others Made sure the snarfer doesn't respond if there's no license key. 2003-10-22 17:43:04 +00:00
plugins Fix a silly line-continuation error 2003-10-28 00:20:23 +00:00
sandbox Moved to sandbox. 2003-10-21 05:47:01 +00:00
scripts Geezle peats, still didn't get the channel thing right. 2003-10-24 13:35:35 +00:00
src Changed the whole handling of nonCommands and ambiguousCommands and whatnot. Now plugins can define an 'invalidCommand' method to be called on invalid commands. 2003-10-28 00:22:15 +00:00
test Changed the whole handling of nonCommands and ambiguousCommands and whatnot. Now plugins can define an 'invalidCommand' method to be called on invalid commands. 2003-10-28 00:22:15 +00:00
tools Updated the class names for the table rows 2003-10-20 17:13:40 +00:00
__init__.py Initial checkin of the distutils stuff. 2003-09-24 07:19:54 +00:00
.cvsignore Initial revision 2003-03-12 06:26:59 +00:00
ACKS Updated. 2003-10-13 05:35:40 +00:00
BUGS Added link to SF.net page 2003-03-25 23:21:42 +00:00
ChangeLog Add new bugzilla module 2003-10-20 19:56:17 +00:00
LICENSE Removed the Python-commented version of the LICENSE. 2003-10-23 07:18:42 +00:00
README Updated to reflect the change in name of the wizards. 2003-10-23 07:32:19 +00:00
setup.py Removed the .py for eventual packaging in Debian. 2003-10-21 06:13:40 +00:00
TODO Updated. 2003-09-24 06:00:36 +00:00

EVERYONE:
---------
Read LICENSE.  It's a 2-clause BSD license, but you should read it anyway.


USERS:
------
First, you gotta have Python 2.3 for this.  That's alright, though,
because Python 2.3 rocks, and you should have it anyway :)

Assuming "python" is in your path and points to Python 2.3 or newer,
then you need to run this:

python setup.py install

from the untarred directory to install the source files.  Then just
run supybot-wizard (it's been installed in your path somewhere) to
create a script that will run your bot as you answered the questions
in the wizard.

If you have any trouble, feel free to swing by #supybot on
irc.freenode.net or irc.oftc.net (we have a supybot there relaying, so
either network works) and ask questions.  We'll be happy to help
wherever we can.  And by all means, if you find anything hard to
understand or think you know of a better way to do something, *please*
post it on Sourceforge.net so we can improve the bot!


WINDOWS USERS:
--------------
The wizards (supybot-wizard, supybot-newplugin, and
supybot-adduser) are all installed to your Python directory's
\Scripts.  What that *probably* means is that you'll run them like
this: C:\Python23\python C:\Python23\Scripts\supybot-wizard


DEVELOPERS:
-----------
Read OVERVIEW to see what the modules are used for.  Read EXAMPLE to see some
examples of callbacks and command written for the bot.  Read STYLE if you ever
wish to contribute.

Use PyLint.  It's even better than PyChecker.  A sample .pylintrc file
is included as tools/pylintrc.  Copy this to ~/.pylintrc and you'll be
able to check your code with the same stringent guidelines I've found
useful to check my code. (deja vu? :))

If you run the tests on Windows (or on a modem connection), be sure to 
exclude (test\test.py -e) test\test_Debian.py.