tag:blogger.com,1999:blog-21332048.post7013062882775237494..comments2023-08-24T09:22:20.836-04:00Comments on Developing Upwards: How To Influence Twisted With DjangoCalvin Spealmanhttp://www.blogger.com/profile/07161631946662126734noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-21332048.post-43164464329590499362010-12-20T11:07:40.707-05:002010-12-20T11:07:40.707-05:00I think the phrase is 'bear with me', unle...I think the phrase is 'bear with me', unless you're in a naturalist beach. ;-)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-21332048.post-30639713666803395212010-12-19T23:34:00.538-05:002010-12-19T23:34:00.538-05:00Hey Calvin,
I can't help but love the idea of...Hey Calvin,<br /><br />I can't help but love the idea of learning from other projects. Please keep thinking and writing about this topic! :)<br /><br />About the specific idea of having something like `settings.py`, I have to disagree though. `settings.py` is one of my least favorite things about django projects. I don't want a pile of Python code defining a heap of global state for my project. Global state sucks! The problem settings.py is tackling is the same as the problem .tac files are tackling, I think. I think that neither one solves the problem _particularly_ well. Moving to a settings.py-like thing would just be lateral movement at best.<br /><br />As far as manage.py goes, maybe you can talk about how having a copy of manage.py in every project is better than having one copy of twistd. What does manage.py get me that twistd doesn't?Jean-Paul Calderonehttps://www.blogger.com/profile/15144405957500773467noreply@blogger.com