nically I'd think only core devs would vote. So neither here or there
> would make a diff imo.
>
> P.S.: That said I am not sure we have a formal policy on how we act on
> DEPs yet (or maybe I should just read DEP 001 more carefully ;))
>
> Cheers,
> Florian
>
> On Wedn
Now that there is a DEP, where do we voice our support (cast +1 votes)?
Here, on the DEP pull request, on the original ticket?
T
On Wednesday, April 16, 2014 10:14:25 PM UTC-4, Loic Bistuer wrote:
>
> On Thursday, April 17, 2014 5:47:10 AM UTC+7, Josh Smeaton wrote:
>>
>> And for the last month
ommon. Again, best practice vs common practice I don't know.
But again, I'm not proposing my settings.py file as the default, just
provided for context.
T
On Wednesday, January 2, 2013 4:17:41 PM UTC-5, Florian Apolloner wrote:
>
> Hi,
>
> On Wednesday, January 2, 2013
> A modern Django project is a collection of apps. Files are looked up under
> conventional paths within apps. Modules (especially the settings module)
> can live anywhere on $PYTHONPATH. Actually, there's not such thing as a
> project root.
>
> For instance, instead of using TEMPLATE_DIRS, p
cases where people explicitly decide not to
use os.path.join and a PROJECT_ROOT variable?
Ted
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-develop
ng a python entry point, and would
love to see django docs/tutorials do more to acknowledge that python might
be new.
Ted
On Sunday, December 23, 2012 12:12:18 AM UTC-5, Jason Goldstein wrote:
>
> I'm jumping in because I initially learned Django on Windows, and used it
> for develop
to change the 2 lines of code required. I
hope you'll consider it for the next release.
thanks
ted
+
Though apparently pg 9.1's trigram indexes can be used for ILIKE
searches (but aren't a win for all query patterns). It seems to me it'd
be worthwhile to have a set
1 million records. ILIKE gets
better the more columns you're comparing, too (30% better, in my example). See
my examples below.
Anyway, I changed it in my implementation because it helped significantly in my
specific case. Hope this helps.
thanks
ted
sdb=# explain analyze select * from
;t have done that, performance wise?
2) Should this be changed in the codebase going forward?
thanks, and I hope this helps,
ted
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develope
Were I work we have had to do this very thing to support I18N in our
forms. Something as simple as a ":" is not a given. Maybe I want a
" :" instead? This could be a form parameter or even a locale setting.
My 2 cents,
Ted
On Mar 29, 9:10 am, "Todd O'Bryan"
Excellent John Thanks!
As we approach 0.96 any chance of getting a pre-release newforms based
version?
Ted
On Feb 13, 5:24 am, "John Sutherland" <[EMAIL PROTECTED]>
wrote:
> Hi all,
>
> Firstly, sorry for the cross-post.
>
> My employer, Mercurytide [1], as s
11 matches
Mail list logo
