I wonder if there's a middle ground between minimizing code churn and
having a standardized formatter. Our team recently switched to yapf after
carefully configuring a .style.yapf file that's included in the root
directory of every new repo. Once that config file is done, the workflow
for yapf
Thank you, akki, for this project! Have enjoyed following your progress.
It'll be something I'm going to make significant use of.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this gr
Wonderful! I make heavy use of btree_gin in one of my projects; will be
great to have these new Index classes!
On Monday, June 27, 2016 at 6:51:31 PM UTC-4, Tim Graham wrote:
>
> Support for more index types is planned. This is only part 1 of the work.
> Please see https://gist.github.com/akki/
Will it be possible to create indexes other than btree? In reviewing the
code it doesn't look like it but I hope I'm wrong. It'd be awesome to
support the many more specific index options without using run_sql.
--
You received this message because you are subscribed to the Google Groups
"Djang
That looks interesting - I might be able to use your module for a project
I'll be working on soon. Two questions I had about data transformation from
the temp column to model column.
1. Can you create datetime stamps from the text data?
2. Can you skip rows where a column == "unwanted data"?
Pa
