Re: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

2016-12-08 Thread Zach
On Thursday, December 8, 2016 at 8:16:02 AM UTC-8, Florian Apolloner wrote: > > On Thursday, December 8, 2016 at 5:04:46 PM UTC+1, Zach wrote: >> >> How about a PACKAGE setting similar to npm's package.json >> . >> > > Seems to be yet another way to do w

Re: Guidelines to name python modules of Django applications?

2016-12-08 Thread Raphaël Barrois
If I understand correctly the input, would the following proposal be an acceptable middle ground? Replace: > It’s often useful to prepend django- to your module name when creating a > package to distribute. This helps others > looking for Django apps identify your app as Django specific With: >

Re: Guidelines to name python modules of Django applications?

2016-12-08 Thread Michael Manfre
As some one who maintains django packages, I wouldn't use "django_" and don't think it should be an official recommendation. I do support documenting the potential collisions to let package maintainers make a more informed decision. On Thu, Dec 8, 2016 at 7:17 AM Adam Johnson wrote: > +1 (to wha

Re: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

2016-12-08 Thread Florian Apolloner
On Thursday, December 8, 2016 at 5:04:46 PM UTC+1, Zach wrote: > > How about a PACKAGE setting similar to npm's package.json > . > Seems to be yet another way to do what custom management commands already over (with less overhead for sure, but also more

Re: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

2016-12-08 Thread Zach
How about a PACKAGE setting similar to npm's package.json . PACKAGE = { 'scripts': { 'test': 'test --keepdb', 'runserver': 'runserver --ipv6', }, } On Thursday, December 8, 2016 at 6:32:19 AM UTC-8, Tim Graham wrote: > > I've

Re: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

2016-12-08 Thread Tim Graham
I've had a similar thought that it would be nice to have some way to specify some default command arguments for management commands (such as --keepdb when running tests), however, adding settings (and/or environment variables?) for every such use case doesn't feel like it'll keep things simple.

Re: Guidelines to name python modules of Django applications?

2016-12-08 Thread Adam Johnson
+1 (to what Aymeric and Florian said) On 7 December 2016 at 19:54, Robert Roskam wrote: > +1 > > On Wednesday, December 7, 2016 at 11:25:05 AM UTC-5, Marc Tamlyn wrote: >> >> What Aymeric and Florian sayid. >> >> On 7 December 2016 at 15:58, Florian Apolloner >> wrote: >> >>> On Wednesday, Dece

Re: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

2016-12-08 Thread Kamal Velan
Considering how the secret key is still in the settings.py giving the user the option to make it an env variable this can follow the same suit. On Monday, 28 November 2016 21:15:17 UTC+5:30, Florian Apolloner wrote: > > -1 on a setting for that. I'd be okay with a DJANGO_RUNSERVER_BINDHOST > env