Hello everyone, Here are some thoughts on the unsettings issue. If you haven't heard about unsettings, it is an attempt to move away from using the settings global. There was a discussion at djangocon (which I wasn't there for, but I was told about it) which led to some of my colleagues and I working on it.
Our github repository: https://github.com/SlashRoot/django The remaining problems in removing settings seem to fall into one of three categories: -Settings that are too heavily entwined with Basesettings, Lazysettings, getattr and setattr... etc. DEBUG is an obvious example. I'm not sure if we can solve this with the decorator, or if we're gonna need a different solution or methodology. -Peculiar pieces of code. I'll include some examples below. This includes functional programming, lambda statements, optimizations, and code that clever. I think we're gonna need to consult people with more experience with this code on a case by case basis. -Code that is not well tested. There's not too much we can do about this code. We're just going to have to deal with it when it presents itself. Some examples: https://github.com/SlashRoot/django/blob/master/django/db/utils.py#L135 https://github.com/SlashRoot/django/blob/master/django/utils/translation/trans_null.py#L25 -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAKNAAemmxeQG-304%3DzUowPw%2B_fOVp6P3cab67jd0YBQOQSzPfw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
