ButterDB
pypi.python.org
ButterDB
1–10 of 45 posts
Re: ButterDB
#2This is a potentially useful project but I could never use it for fear of "FuckItDB" appearing in an exception call trace that a client might see.
Names don't have to mean anything, but certain names are still unacceptable.
Re: ButterDB
#3I'm surprised this was released under the MIT License. The WTFPL would be more appropriate.
Re: ButterDB
#4This is a potentially useful project but I could never use it for fear of "FuckItDB" appearing in an exception call trace that a client might see. Names don't have to mean anything, but certain names are still unacceptable.
Based on the "don't use this for anything important" note, I think that's probably intentional. If someone spends the time to build this into something production-ready, they can change the name, too.
Re: ButterDB
#5This is a potentially useful project but I could never use it for fear of "FuckItDB" appearing in an exception call trace that a client might see. Names don't have to mean anything, but certain names are still unacceptable.
According to this commit, the name was changed to butterdb about three months ago.
https://github.com/Widdershin/butterdb/commit/6a73c9199d53f5...
Digging on PyPI, I found the new package named butterdb. The version is bumped from .13 to .14, though that might just be the name change. In any case, it might be a good idea to change the submission to reflect the new name and the new package.
Re: ButterDB
#6I'm surprised this was released under the MIT License. The WTFPL would be more appropriate. http://www.wtfpl.net/
It would have been more inappropriate. Which could be the goal, I don't know.
But more seriously, it's legally risky to have anything to do with code licensed under WTFPL because it does not actually specify that you can do anything with the code without possible legal reprisals, from which no protection is offered. Probably safe to point and laugh at it, though.
Re: ButterDB
#7I'm surprised this was released under the MIT License. The WTFPL would be more appropriate. http://www.wtfpl.net/
It would have been more inappropriate. Which could be the goal, I don't know. But more seriously, it's legally risky to have anything to do with code licensed under WTFPL because it does not actually specify that you can do anything with the code without possible legal reprisals, from which no protection is offered. Probably safe to point and laugh at it, though.
Although the WTFPL website (http://www.wtfpl.net/faq/) does note somewhat ominously that it hasn't been tested in courts, it seems legitimate enough to me. Is there any evidence outside of its lack of history in court that would indicate it isn't suitable for production use?
EDIT: gnu.org also says "We do not recommend this license" ,pointing to the Apache license as providing better protection against 'patent treachery'. (https://www.gnu.org/licenses/license-list.html)
Re: ButterDB
#8I expected it to be a new NoSQL, "eventually consistent" database server.
Re: ButterDB
#9This was posted to the NZ Python User Group a couple of months back, where a bit of discussion around the name took place, https://groups.google.com/d/msg/nzpug/womO01rqF58/niM48Fn8QA...
Re: ButterDB
#10Earlier quoted context omitted.
It would have been more inappropriate. Which could be the goal, I don't know. But more seriously, it's legally risky to have anything to do with code licensed under WTFPL because it does not actually specify that you can do anything with the code without possible legal reprisals, from which no protection is offered. Probably safe to point and laugh at it, though.
Although the WTFPL website ( http://www.wtfpl.net/faq/ ) does note somewhat ominously that it hasn't been tested in courts, it seems legitimate enough to me. Is there any evidence outside of its lack of history in court that would indicate it isn't suitable for production use? EDIT: gnu.org also says "We do not recommend this license" ,pointing to the Apache license as providing better protection against 'patent trea…
Track down what 'DannyBee has to say about WTFPL and licenses like it. There are good reasons not to use it even if you don't care what happens with your code.