Re: Support for unittest -k option

2019-03-11 Thread Arthur Rio
I’m +1 on no short-hand. Also “kdb” is a little to close to “pdb” and doesn’t really make sense to me. — Arthur On March 11, 2019 at 3:33:50 PM, Dan Davis (dansm...@gmail.com) wrote: I personally don't think a short-hand is needed. On Mon, Mar 11, 2019 at 10:41 AM Tim Graham wrote: > -kdb

Re: Support for unittest -k option

2019-03-11 Thread Dan Davis
I personally don't think a short-hand is needed. On Mon, Mar 11, 2019 at 10:41 AM Tim Graham wrote: > -kdb could be a suitable short option. > > On Monday, March 11, 2019 at 9:20:37 AM UTC-4, Tobias McNulty wrote: >> >> Agreed it's probably better to make the switch now, and I'd be fine >>

Re: Support for unittest -k option

2019-03-11 Thread Tim Graham
-kdb could be a suitable short option. On Monday, March 11, 2019 at 9:20:37 AM UTC-4, Tobias McNulty wrote: > > Agreed it's probably better to make the switch now, and I'd be fine > without a replacement shorthand alternative for --keepdb. > > Cheers, > > > *Tobias McNulty*Chief Executive

Fellow Reports - March 2019

2019-03-11 Thread Tim Graham
Week ending March 9, 2019 Triaged --- https://code.djangoproject.com/ticket/30232 - Correct expected format in invalid DurationField error message (fixed) https://code.djangoproject.com/ticket/30231 - Field's verbose_name is ignored in FilteredSelectMultiple widget for inlines created

Re: Support for unittest -k option

2019-03-11 Thread Tobias McNulty
Agreed it's probably better to make the switch now, and I'd be fine without a replacement shorthand alternative for --keepdb. Cheers, *Tobias McNulty*Chief Executive Officer tob...@caktusgroup.com www.caktusgroup.com On Mon, Mar 11, 2019 at 8:19 AM Carlton Gibson wrote: > Thanks François,

Re: Support for unittest -k option

2019-03-11 Thread Adam Johnson
+1 from me, I'm okay with the small breaking change to keep in-line with upstream unittest. Since it's restricted to tests, it's unlikely to break anyone's production site. On Mon, 11 Mar 2019 at 12:19, Carlton Gibson wrote: > Thanks François, > > Just on this, my thought is that if we don't

Re: Use CDN for djangoproject.com

2019-03-11 Thread Adam Johnson
Looking good! Thanks for your work Tobias. I get 30ms through CDN instead of 230ms from here in London, UK. I take back my bad comments about Fastly, since they are giving free credits :) If you don't need custom Varnish code they are quite easy to configure and easy to contact on IRC.n On Mon,

Re: Use CDN for djangoproject.com

2019-03-11 Thread Tobias McNulty
Hi all, These changes have been deployed (though we're not yet using a CDN for the primary domain, docs.djangoproject.com, so you shouldn't notice a change). The alternate URL (https://django-docs.global.ssl.fastly.net/en/2.1/) will now cache docs pages for up to a week, and the hourly docs

Re: Support for unittest -k option

2019-03-11 Thread Carlton Gibson
Thanks François, Just on this, my thought is that if we don't follow `unittest` in changing `-k` for this, we have a steady trickle of confusion forever-more. I'd rather avoid that. C. On Monday, 11 March 2019 13:14:01 UTC+1, François Freitag wrote: > > Hi Django Devs, > >

Support for unittest -k option

2019-03-11 Thread François Freitag
Hi Django Devs, https://code.djangoproject.com/ticket/30245 suggests supporting Python unittest `-k` option, to selectively run tests matching a keyword. Currently, `-k` is the shorthand for `--keepdb` in Django. A `--filter` flag was suggested to preserve backward compatibility. Carlton