bss/dr.botzo
1
0
Fork 0
Code Issues 3 Pull Requests Releases 2 Wiki Activity
12a031aed6
dr.botzo/requirements.txt

59 lines
1.1 KiB
Plaintext
Raw Normal View History

requirements.txt: py3 related (?) version bumps this has been tested in a python 3.4 environment. i'm not sure if all of these changes were necessary to make this py3 compatible, but it works, so i'm committing it
2016-01-16 19:40:18 -06:00
astroid==1.4.4
caniusepython3==3.3.0
colorama==0.3.6
distlib==0.2.1
Django==1.8.8
dispatch: port to django REST framework this moves the dispatcher functionality that used to be in the old ircbot directly to django REST framework, which is more robust and allows for cooler stuff down the road. this still retains the ability to have the bot privmsg, that still happens over the XML-RPC interface, this is just a more convenient frontend to that
2015-06-18 23:57:43 -05:00
django-adminplus==0.3
convert the very basic UI we had to bootstrap
2016-03-30 16:00:49 -05:00
django-bootstrap3==7.0.1
bump django-extensions to 1.5.3
2015-05-08 22:32:54 -05:00
django-extensions==1.5.3
dispatch: port to django REST framework this moves the dispatcher functionality that used to be in the old ircbot directly to django REST framework, which is more robust and allows for cooler stuff down the road. this still retains the ability to have the bot privmsg, that still happens over the XML-RPC interface, this is just a more convenient frontend to that
2015-06-18 23:57:43 -05:00
django-filter==0.10.0
add django-registration-redux and use some of it for the moment this is for the password change url used in the auth dropdown, and a better login page, but this might become other stuff eventually too. the signup page exists and is linked to, even if i don't have a great reason for this to exist bunch of templates added now to support the intentional and unintentional stuff
2016-03-30 15:36:56 -05:00
django-registration-redux==1.4
dispatch: port to django REST framework this moves the dispatcher functionality that used to be in the old ircbot directly to django REST framework, which is more robust and allows for cooler stuff down the road. this still retains the ability to have the bot privmsg, that still happens over the XML-RPC interface, this is just a more convenient frontend to that
2015-06-18 23:57:43 -05:00
djangorestframework==3.1.3
add prospector and config
2015-06-20 02:00:56 -05:00
dodgy==0.1.7
requirements.txt: py3 related (?) version bumps this has been tested in a python 3.4 environment. i'm not sure if all of these changes were necessary to make this py3 compatible, but it works, so i'm committing it
2016-01-16 19:40:18 -06:00
futures==3.0.3
add requirements.txt for pip and virtualenv happiness
2012-07-26 20:34:47 -05:00
httplib2==0.7.4
start the new ircbot framework
2015-05-09 18:56:26 -05:00
inflect==0.2.5
irc==12.1.4
jaraco.apt==1.0
jaraco.classes==1.2
jaraco.collections==1.1
jaraco.context==1.3
jaraco.functools==1.3
jaraco.itertools==1.3
jaraco.logging==1.2
jaraco.text==1.3
requirements.txt: py3 related (?) version bumps this has been tested in a python 3.4 environment. i'm not sure if all of these changes were necessary to make this py3 compatible, but it works, so i'm committing it
2016-01-16 19:40:18 -06:00
jaraco.timing==1.2.2
lazy-object-proxy==1.2.1
add pylint and pyflakes to requirements.txt
2012-07-27 17:22:28 -05:00
logilab-astng==0.24.0
add prospector and config
2015-06-20 02:00:56 -05:00
logilab-common==0.63.2
requirements.txt: py3 related (?) version bumps this has been tested in a python 3.4 environment. i'm not sure if all of these changes were necessary to make this py3 compatible, but it works, so i'm committing it
2016-01-16 19:40:18 -06:00
Markdown==2.6.5
add prospector and config
2015-06-20 02:00:56 -05:00
mccabe==0.3.1
start the new ircbot framework
2015-05-09 18:56:26 -05:00
more-itertools==2.2
requirements.txt: py3 related (?) version bumps this has been tested in a python 3.4 environment. i'm not sure if all of these changes were necessary to make this py3 compatible, but it works, so i'm committing it
2016-01-16 19:40:18 -06:00
oauth2==1.9.0.post1
oauthlib==1.0.3
pep257==0.7.0
add prospector and config
2015-06-20 02:00:56 -05:00
pep8==1.6.2
requirements.txt: py3 related (?) version bumps this has been tested in a python 3.4 environment. i'm not sure if all of these changes were necessary to make this py3 compatible, but it works, so i'm committing it
2016-01-16 19:40:18 -06:00
pep8-naming==0.3.3
add requirements.txt for pip and virtualenv happiness
2012-07-26 20:34:47 -05:00
ply==3.4
add prospector and config
2015-06-20 02:00:56 -05:00
prospector==0.10.2
pyflakes==0.9.2
requirements.txt: py3 related (?) version bumps this has been tested in a python 3.4 environment. i'm not sure if all of these changes were necessary to make this py3 compatible, but it works, so i'm committing it
2016-01-16 19:40:18 -06:00
pylint==1.5.4
add prospector and config
2015-06-20 02:00:56 -05:00
pylint-celery==0.3
requirements.txt: py3 related (?) version bumps this has been tested in a python 3.4 environment. i'm not sure if all of these changes were necessary to make this py3 compatible, but it works, so i'm committing it
2016-01-16 19:40:18 -06:00
pylint-common==0.2.2
pylint-django==0.7.1
add prospector and config
2015-06-20 02:00:56 -05:00
pylint-plugin-utils==0.2.3
requirements.txt: py3 related (?) version bumps this has been tested in a python 3.4 environment. i'm not sure if all of these changes were necessary to make this py3 compatible, but it works, so i'm committing it
2016-01-16 19:40:18 -06:00
python-dateutil==2.4.2
start of gitlab code review/merge bot the intent of this thing is to scan configured projects' merge requests, and automatically assign them to designated code reviewers. if someone says "LGTM" in the merge request thread, that counts as a review and the bot either selects another reviewer or assigns the thing to a designated merge approver for the final approval and merge this is most of the way there, but not done yet. things still to do: 1) more strings than "LGTM", but we should be careful to avoid things that someone might actually say 2) i'm trying to avoid it but i probably need to track the 2 of 2 reviewer message separate from the message assigning the merge request to an approver. it's plausible that a reviewer is also an approver, and if the last reviewer is a candidate approver, the script does nothing, but we probably want it to still log the 2 of 2 part. i could track the "nagging" for 2 of 2 messages, to avoid the bot repeating itself, but that seems unfortunately annoying
2016-06-23 23:49:38 -05:00
python-gitlab==0.13
requirements.txt: py3 related (?) version bumps this has been tested in a python 3.4 environment. i'm not sure if all of these changes were necessary to make this py3 compatible, but it works, so i'm committing it
2016-01-16 19:40:18 -06:00
pytz==2015.7
add prospector and config
2015-06-20 02:00:56 -05:00
PyYAML==3.11
requirements.txt: py3 related (?) version bumps this has been tested in a python 3.4 environment. i'm not sure if all of these changes were necessary to make this py3 compatible, but it works, so i'm committing it
2016-01-16 19:40:18 -06:00
requests==2.9.1
requests-oauthlib==0.6.0
requirements-detector==0.4.1
add prospector and config
2015-06-20 02:00:56 -05:00
setoptconf==0.2.0
requirements.txt: py3 related (?) version bumps this has been tested in a python 3.4 environment. i'm not sure if all of these changes were necessary to make this py3 compatible, but it works, so i'm committing it
2016-01-16 19:40:18 -06:00
six==1.10.0
tempora==1.4
twython==3.3.0
wrapt==1.10.6
yg.lockfile==2.1
start the new ircbot framework
2015-05-09 18:56:26 -05:00
zc.lockfile==1.1.0
Reference in New Issue Copy Permalink