Re: The low down on the "Unsettings" project

Google "django-development unsettings". It's been discussed at length on list. Cheers Tom On Fri, Jun 20, 2014 at 8:06 PM, Andy Baker wrote: > This sounds really interesting. Is there anything about this in writing? I'm > not a fan of listening to audio on tech subjects

Re: The low down on the "Unsettings" project

This sounds really interesting. Is there anything about this in writing? I'm not a fan of listening to audio on tech subjects (must... skim... read...). Not sure if anyone else shares this prejudice but do post here if there is a follow-up blog post or similar. -- You received this message

The low down on the "Unsettings" project

Hello, Just sending general heads up that this bit of knowledge exists, but this is Justin Myles Holmes talking about the "unsettings" project, that is the idea of removing `settings.py`. https://soundcloud.com/elena/django-news-podcast-18-may-2014#t=7m33s This is actuall

Re: The unsettings project

Not sure whether this has already been covered. Maybe it is. I'd like to specify the settings as a class instead of a module. Mostly because I don't like the "from settings_local import *" pattern to extend some base settings with machine specific settings. By having the possibility to define

Re: The unsettings project

Hi, I'd like to describe how we've solved the per-package settings issue at our company. Here's a little source code example: https://gist.github.com/wkornewald/9109270 Every Python package defines a module with a Config instance and then sets default settings on it. Instead of defining

Re: The unsettings project

Hi Schuyler, On 14 févr. 2014, at 15:18, Schuyler Duveen wrote: > TLDR: Django modules should work as libraries (e.g. ORM, mail, etc). "from > django.conf import settings" bootstrap undermines this. > My use-case is Django's awesome (yes, I know opinions differ),

Re: The unsettings project

On Friday, February 14, 2014 10:53:11 AM UTC-5, Florian Apolloner wrote: > > Hi, > > On Friday, February 14, 2014 3:18:08 PM UTC+1, Schuyler Duveen wrote: >> >> This work started at the Chicago DjangoCon sprint this past September. >> Justin Holmes and I were talking to Adrian (and then roped

Re: The unsettings project

Hi, On Friday, February 14, 2014 3:18:08 PM UTC+1, Schuyler Duveen wrote: > > This work started at the Chicago DjangoCon sprint this past September. > Justin Holmes and I were talking to Adrian (and then roped in Jacob). > After discussing the problem and working out a possible way to move >

Re: The unsettings project

Hi folks, Let me make a stab at the 1000ft view for this. TLDR: Django modules should work as libraries (e.g. ORM, mail, etc). "from django.conf import settings" bootstrap undermines this. unsetting begins a path to support the legacy structure, but still allows for the 'librarification' of

Re: The unsettings project

On Tuesday, February 11, 2014 8:33:09 AM UTC+1, Aymeric Augustin wrote: > > On 11 févr. 2014, at 03:27, James Farrington > > wrote: > > If you haven't heard about unsettings, it is an attempt to move away from > using the settings global. There was a discussion at

Re: The unsettings project

On 11 févr. 2014, at 03:27, James Farrington wrote: > 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

Re: The unsettings project

Diff https://github.com/SlashRoot/django/compare/django:master...master On Monday, February 10, 2014 6:59:41 PM UTC-8, Russell Keith-Magee wrote: > > > On Tue, Feb 11, 2014 at 10:27 AM, James Farrington > > wrote: > >> Hello everyone, >> >> Here are some thoughts on the

Re: The unsettings project

On Tue, Feb 11, 2014 at 10:27 AM, James Farrington < jamestfarring...@gmail.com> wrote: > 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