-
Notifications
You must be signed in to change notification settings - Fork 209
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
make medium use a label as identifier #36
base: master
Are you sure you want to change the base?
Conversation
@sherzberg I actually like this change. Sorry for not merging it sooner. |
@sherzberg i'll try to update it and get it merged but if you could do me a favor and rebase your branch to get it updated so that I can merge it through GitHub it might make things faster. Thanks. |
this commit uses the backends label from NOTIFICATION_BACKENDS setting for easier to rearrange backends Conflicts: notification/backends/__init__.py pinax/notifications/models.py
b832c3f
to
057a311
Compare
@paltman cool! i rebased and had to fix a few conflicts. tests seem to pass locally on python 2.7 and django 1.7-1.8. I dont have python 3 setup on my home machine, so just waiting to see if the the travis build works out ok. |
@paltman Can this be merged? |
@sherzberg i tested this PR with python3 and it works.. hope it gets merged sometime |
@paltman @ossanna16 can this be merged? |
fixes #21 this commit uses the backends label from NOTIFICATION_BACKENDS setting
for easier to rearrange backends
for upgrades, you may have to write a custom alter statement to turn integers into varchars and then change the labels in your NOTIFICATION_BACKENDS to the string equivalent of the order