Go to file
2004-08-18 14:57:34 +00:00
debian Added a build-depends on python-dev, which is required for distutils. 2004-04-11 23:48:34 +00:00
docs Blech. Totally not literary. 2004-08-13 03:31:45 +00:00
examples Updated. 2004-07-26 01:19:41 +00:00
others Implement some of the hints from Bug #1007571 and fix Bug #1002363 while I'm 2004-08-12 15:04:52 +00:00
plugins ly 2004-08-17 21:00:55 +00:00
sandbox Removed, our plugins version works a bit better. 2004-07-31 00:37:04 +00:00
scripts Added profiling information as well as the threads command. 2004-08-17 20:28:00 +00:00
src Changed supplyDefault to _supplyDefault and added %s handling for supybot.nick.alternates. 2004-08-17 20:43:25 +00:00
test Added profiling information as well as the threads command. 2004-08-17 20:28:00 +00:00
tools Fixing the "I know there was something I didn't finish, but I don't remember 2004-08-18 14:57:34 +00:00
__init__.py Eh, those things didn't need to be where they were. 2004-02-02 17:19:38 +00:00
.cvsignore Initial revision 2003-03-12 06:26:59 +00:00
ACKS Updated. 2004-04-09 17:13:49 +00:00
BUGS Updated. 2004-07-28 19:03:13 +00:00
ChangeLog Add conf.supybot.plugins.Quotes.requireRegistration and fix a bug with 2004-08-17 03:45:30 +00:00
DEVS kmj is right. Writing in third person is balls. :) 2004-04-16 08:56:55 +00:00
LICENSE Updated. 2004-04-09 17:13:49 +00:00
README Typo fix. 2004-08-11 04:59:44 +00:00
RELNOTES Updated to allow multiple servers. 2004-07-30 06:52:21 +00:00
setup.py Handle stupid distributions. 2004-08-03 06:23:50 +00:00
TODO Updated. 2004-07-29 11:17:16 +00:00

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


USERS:
------
Read docs/GETTING_STARTED for an introduction to the bot.  Read
docs/CAPABILITIES to see how to use capabilities more to your
benefit. 

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 commands written for the bot.
Read INTERFACES to see what kinds of objects you'll be dealing with.
Read STYLE if you wish to contribute; all contributed code must meet
the guidelines set forth there..

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? :))

Be sure to run "test/test.py --help" to see what options are available
to you when testing.  Windows users in particular should be sure to
exclude test_Debian.py and test_Unix.py.