Re: unblocking #17277

I'm in support of fixing the problem, and this narrowly scoped solution seems like a reasonable way to go about that. -Paul On Fri, Feb 10, 2012 at 11:45 AM, David Lowe wrote: > Django devs - > > I would love to see my patch in > https://code.djangoproject.com/ticket/17277 applied. It's a pretty

unblocking #17277

Django devs - I would love to see my patch in https://code.djangoproject.com/ticket/17277 applied. It's a pretty small change, doesn't break backwards compatibility, and includes test coverage. It does introduce a new pattern which isn't used elsewhere in the django code (wrapping a broad exceptio

Re: Why recommend to include project name in settings?

You're right. Something similar "from .something import SomeThing". Like, https://github.com/django-nonrel/djangotoolbox/blob/develop/djangotoolbox/tests.py#L1 On Fri, Feb 10, 2012 at 9:52 AM, Alex Gaynor wrote: > > > On Fri, Feb 10, 2012 at 10:57 AM, Carl Meyer wrote: > >> -BEGIN PGP SIGNE

Why recommend to include project name in settings?

On Feb 10, 2012 3:47 PM, "Adam "Cezar" Jenkins" wrote: > > On Fri, Feb 10, 2012 at 9:50 AM, Carl Meyer wrote: >> >> "import .module" > > > Not arguing one way or another, but the above has always worked for me from a Python standpoint. It shouldn't work - the Python 2.7.2 documentation says that

Re: Why recommend to include project name in settings?

On Fri, Feb 10, 2012 at 10:57 AM, Carl Meyer wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 02/10/2012 08:47 AM, Adam "Cezar" Jenkins wrote: > > On Fri, Feb 10, 2012 at 9:50 AM, Carl Meyer > > wrote: > > > > "import .module" > > > > > > Not arguing o

Re: Why recommend to include project name in settings?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/10/2012 08:47 AM, Adam "Cezar" Jenkins wrote: > On Fri, Feb 10, 2012 at 9:50 AM, Carl Meyer > wrote: > > "import .module" > > > Not arguing one way or another, but the above has always worked for me > from a Pytho

Re: Why recommend to include project name in settings?

On Fri, Feb 10, 2012 at 9:50 AM, Carl Meyer wrote: > "import .module" Not arguing one way or another, but the above has always worked for me from a Python standpoint. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group

Re: Why recommend to include project name in settings?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/10/2012 08:25 AM, Chris Wilson wrote: > On Fri, 10 Feb 2012, Carl Meyer wrote: >>> Is there any reason not to drop the project name part of >>> DJANGO_SETTINGS_MODULE and ROOT_URLCONF, to reduce the risk of >>> confusion, pollution, double import

Re: Why recommend to include project name in settings?

Hi Carl, On Fri, 10 Feb 2012, Carl Meyer wrote: Is there any reason not to drop the project name part of DJANGO_SETTINGS_MODULE and ROOT_URLCONF, to reduce the risk of confusion, pollution, double imports and bad practice app coding in Django? If you follow that quoted thread to the end, yo

Re: Why recommend to include project name in settings?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Chris, On 02/10/2012 05:36 AM, Chris Wilson wrote: >> But "mysite" is a package, and Django wants us to be able to import >> "mysite.settings" and "mysite.urls" (in fact, the latter is the >> default ROOT_URLCONF setting). In order to make that pos

Why recommend to include project name in settings?

Hi all, I'd like to inquire about the design decision to recommend users to include the project name in DJANGO_SETTINGS_MODULE and ROOT_URLCONF, for example: When using django-admin.py, you can either set the environment variable once, or explicitly pass in the settings module each time you

Re: ticket/15926, advice

2012/2/7 Jonathan Paugh > I think this patch deserves some attention. I'd also appreciate some > guidance on contributing, as needed. > Hi Jonathan, You're on the right track. I've added some comments on the ticket. Thanks for your contribution! -- Aymeric. -- You received this message bec