Re: Removing url() ?

[Karen Tracey]

On Tue, May 5, 2020 at 11:42 AM Collin Anderson 
wrote:

> Hi All,
> Are we _sure_ we want to completely get rid of url()?
>
>
I'm not! I'd be much happier with fewer tedious upgrade tasks and the
ability to use client's money for new features rather than "keeping up",
sigh.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CACS9raeOR7QdVHZA0ojzzu5MvdFfNw9%2B4kxuxfZ8OP93ZUbgzw%40mail.gmail.com.

Re: RANDOM PICKING OF TWO DIFFERENT LISTS, ASSIGNING ONE ITEM FROM ONE LIST TO THE OTHER ITEM IN ANOTHER LIST

[Karen Tracey]

Please ask questions about using Django on Django-users. The topic of this
list is the development of Django itself.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CACS9rafeajAtmP_-uYM2%2BC10-_DoWJSAKfO3tNX1dbHETQF8SA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Template handling of undefined variables

[Karen Tracey]

On Sat, Feb 25, 2017 at 8:21 PM, Fred Stluka  wrote:

> I agree that use of undefined variables should raise an exception.
> The incompatibility with previous versions will mostly catch errors
> that have been going undetected.
>

I disagree, unless you are limiting this change specifically to arguments
to non-builtin template tags. (Which I thought already raised exceptions,
so I'm still confused here as to what change is being proposed.)

Given the documented behavior of evaluating undefined variables to empty
strings its been common practice to use:

{% if var_that_may_not_exist %}
...stuff that should only show when var exists...
{% endif %}

or to include {{ var_that_may_not_exist }} somewhere in a template and rely
on it evaluating to an empty string. (admin itself was documented as not
working correctly if you set the setting to evaluate undefined to something
other than empty string).

Changing either of these now to raise exceptions would be a huge backwards
incompatibility going against previously documented behavior.  Please don't
do that.

It may well be friendlier to developers (I've never been a fan of the
"templates shouldn't raise exceptions" philosophy) but the fact is for many
years now it's been perfectly acceptable to use what might be undefined
variables in templates and the behavior has been documented as to how it
will work. Changing that now to start raising exceptions would be
incredibly unfriendly to existing code that has been written to rely on it.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CACS9raeFmaZQqtH3wyT6abRsXSHFjL2%2B-VfGnjgG2-18_M%2BRsg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Template handling of undefined variables

[Karen Tracey]

On Sat, Feb 25, 2017 at 2:10 PM, Tim Graham  wrote:

> I think any use of undefined template variables should raise an exception.
> In the long run, keeping a setting to allow some other behavior seems
> confusing and, considering the case of templates that might be reused in
> different projects with different settings, even dangerous.
>

I think I'm confused...Django templates have allowed use of undefined
variables and documented their use as evaluating to the empty string for as
long as I recall. Wouldn't a change to instead raise exceptions be a major
backwards-incompatibility?

https://docs.djangoproject.com/en/1.7/topics/templates/#variables said "If
you use a variable that doesn’t exist, the template system will insert the
value of the TEMPLATE_STRING_IF_INVALID setting, which is set to '' (the
empty string) by default."

https://docs.djangoproject.com/en/dev/ref/templates/api/#invalid-template-variables
has refined that doc to note that the behavior is slightly different in
some tags.

Are we really considering changing this behavior to now raise exceptions?

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CACS9rad-TtehoMxLCruRv5M8yT_GHH-nZxvBETcVaRrLfHVkUw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Use of HTML autofocus attribute in admin (#27692)

[Karen Tracey]

On Fri, Jan 6, 2017 at 12:48 PM, Tim Graham  wrote:

> Do you think we should remove autofocus from the search box to remedy this
> complaint (and possibly go back to using JavaScript for that) or are there
> any better solutions here?


I personally find the existing auto-focus behavior more annoying than
helpful, as it seems I'm much more likely to want to navigate by cursor or
page down than search when I land on an admin list page, and it forces me
to first get the focus away from the search box before I can do what I
want. So I wouldn't mind if auto-focus went away entirely.

Having it not only grab the focus but scroll back to to the top of the page
would be extraordinarily annoying, let's please avoid doing that.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CACS9radGBOdtFs6YbOgyMX%3DPL%3DqtK6kVYM-7bNUYAU2Z33RwEg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django 2.0 Python version support (Python 3.6+ only?)

[Karen Tracey]

On Wed, Dec 28, 2016 at 2:41 PM, Claude Paroz  wrote:

> Any idea why my message in this thread was deleted?
>

No idea. It was held in moderation as "possible spam" for reason only
Google Groups knows. When GG does this, it does not send moderators a note
about it until 3 or 4 days later. This one I happened to see when I went to
moderate a post from a first-time poster, and I sent both through. It came
through in email. No idea why in the group it shows up as "deleted". Maybe
it will re-appear in the group eventually...

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CACS9raeLU%2BtPGTx4ZQWmf0XhS7b-%2BK7b%3DykXGQsn8GvLjfDRsw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: how to design custom forms in django with bootstrap

[Karen Tracey]

Please do not cross post to both this list and django-users. This list is
for discussing the development of Django itself, usage questions are
appropriate on django-users.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CACS9radJ%3D9%2BBnxEPyMZunHhdhB3D18SCicEP%2B%2BRM73xXFAwbgQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: MySQL data loss possibility with concurrent ManyToManyField saves

[Karen Tracey]

This is the 2nd major issue I can recall caused by MySQL default of
REPEATABLE READ transaction isolation level. I think Django should simply
switch itself to a default of using READ COMMITTED, consistent with (all?)
other supported database backends, and document how, if a user really
really wants to use REPEATABLE READ, they can do so (I assume Django could
allow that?), and what known problems when using basic Django functions
they may run into if they do so.

I fear our existing approach of documenting how certain functions don't
work by default on MySQL (e.g. get_or_create) is not really helping the
majority of our users. I believe switching instead to making Django code
itself work by default on MySQL would be a better long-term solution for
those who use MySQL with Django, and avoid future cases like this one that
has been discovered (years after we knew get_or_create was broken by
default transaction isolation level on MySQL).

On Mon, Mar 14, 2016 at 11:15 AM, Tim Graham  wrote:

> Could some MySQL users take a look at ticket #26347 [0] and recommend how
> to proceed? I think it's probably not a new issue but I'm a bit surprised
> it hasn't come up before if so.
>
> [0] https://code.djangoproject.com/ticket/26347
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/286b0efb-673f-42d7-a1f3-5de76fc039c5%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CACS9rae4U0e80-h%3DesTXFUi%3DLxWQ-XiMAp%3DAdkXcR0FnJVT2Cg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Looking for NYC based Django to complete project

[Karen Tracey]

The topic of this list is the development of Django itself. For questions
about Django, or looking for developers who can help you with developing a
Django site, please email djang-users, not here.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CACS9racYFDehddRu4%2BYu0%2BAmqeb5YTf2ycEJG218%2Bj5YAKxmaA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Ticket #25236: Remove ifequal from the template language

[Karen Tracey]

We certainly weren't discussing removing without deprecating, were we? I'm
saying removing isn't worth the hassle to users, period. My opinion from
working on a fair number of inherited sites, plus sites where I don't get
to choose who contributes code I'm responsible for maintaining. I've
reported I have code I have to maintain written last year that uses these
tags, it's not just ancient crufty old stuff. These tags don't cause a
massive "brain stop" to figure out what "ifequal" might mean when
encountering them in existing templates.They are not that bad. This wart
isn't worth the pain to users to remove, in my opinion. Finding and fixing
all templates used by a site is NOT trivial. Fixing url was worth it. This
is not.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CACS9radxTh4mNtkQ%3Dfg5yUg_MF_EUu6Yqo%3DNGNqJg7e5vAwbwQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Ticket #25236: Remove ifequal from the template language

[Karen Tracey]

Believe me I understand what technical debt is. In my opinion the cost of
this debt in Django is not sufficient to warrant the cost to users of
Django to remove it. Find and fix (or figure out if it's necessary to fix)
all templates (some of which may be coming from 3rd party packages)  used
in a site is not that trivial of a task for a large site with many 3rd
party dependencies. By contrast documenting why these two tags exist is
pretty painless.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CACS9rafSuot0xati8HLOe2QEV7QpNny7d4bZDnVGzwsiAgDP7A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Ticket #25236: Remove ifequal from the template language

[Karen Tracey]

On Thu, Aug 6, 2015 at 12:15 PM, Daniel Greenfeld  wrote:

> No modern project uses ifequal. No one recommends it. I argue it is taking
> up valuable bytes in the project. Let's remove it.
>

I maintain (did not write) a project written last year that has ifequal and
ifnotequal. Is it really necessary to make it harder to upgrade this
project to a more recent Django?

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CACS9radErjkfJHC0wVvPJWK4HpzVQiAyj0s_2ykG57EAG1%2BqLA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: CSRF REASON_NO_REFERER with meta referrer tags

[Karen Tracey]

This has bee brought up before, see:
https://code.djangoproject.com/ticket/16870

I am not aware of any change in this area that would affect the decision
made in that ticket.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CACS9rafr6f01-9c7vBNprnz1CTJGgOUyZvfSbOw_da0b_4i4%2BQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Custom 400 error handler or capture broken URLs

[Karen Tracey]

There is a ticket open on this issue:

https://code.djangoproject.com/ticket/19508

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CACS9rae5RCbaFTMKGyHF6R2U6Vb0%2B9-cf41j4Y_m7UAs25fACQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Newsletter in django (MailChimp)

[Karen Tracey]

Please ask questions about using Django on django-users. The topic of this
list is the development of Django itself.

Thanks,
Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CACS9rae0pNwVGr6%2BvdMUR%2BUBOZPddPKuFN%2BFa6NPQyiT%3D7cNZg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[no subject]

[Karen Tracey]

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CACS9radTPubXAPCz2_ZccMg1oq6DtDJXxWy8-PshnAPXtR%3DjQg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: python-social-auth partial pipeline can not resume

[Karen Tracey]

Please don't crosspost to both django-developers and django-users. The
topic of this list is the development of Django itself, django-users is for
usage questions such as this one. Thanks,
Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CACS9raduzW9h-R9iEP1rPOHFat9Vfu_TewfZYXahixLEMU%2Bm8Q%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Django ORM support for NoSql databases

[Karen Tracey]

On Tue, Dec 17, 2013 at 2:05 PM, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:

> On 17 déc. 2013, at 19:53, Javier Guerra Giraldez 
> wrote:
>
> > On Tue, Dec 17, 2013 at 12:16 PM, Aymeric Augustin
> >  wrote:
> >> Django’s ORM is entirely designed to translate between an object
> oriented API and SQL. That’s what its name says. It achieves this through
> roughly five layers that bride the abstraction gap.
> >>
> >> Django’s ORM is fundamentally tied to SQL. It isn’t a choice, a policy
> or a wish. It’s a fact.
> >
> > hum  i think you know more than anybody about the ORM, but
> > recently (March 26) i said something similar on the Django-users list,
> > just to be immediately corrected by Russel:
>
> I’m likely to stand corrected as soon as the sun rises in Perth, then…
>
>
No need to wait that long:

https://groups.google.com/d/msg/django-developers/0IuJssTt8tc/TxdXQ2D0thcJ

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CACS9rafW7qPq2oNUbcQzO8pEJcMNRgoqXRZ9Pbrnt-XznkcQKA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Enable storing NULL in database

[Karen Tracey]

On Thu, Nov 7, 2013 at 5:37 AM, Vlastimil Zíma  wrote:

> I don't want to enforce anybody to use only NULL as empty value, I just
> want Django to store NULL in database when I told it to. And I don't mean
> the way of overriding all the form fields as I have to now.
>

A concrete proposal would help here.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CACS9raeFW1X3AV2yq_tF%2By3tf6-ZVCDL-fQDyXeu%2BFxDd5OvGw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Backwards compatibility and field validation

[Karen Tracey]

On Wed, Oct 16, 2013 at 7:03 PM, Russell Keith-Magee <
russ...@keith-magee.com> wrote:

>
>> 1) Without taking backwards compatibility into consideration, is it
>> reasonable to expect field validation automatically upon calling
>> model.save()
>>
>
> Yes. Based on the original discussions (as I recall them), this wasn't in
> question -- the problem was entirely backwards compatibility.
>
>


Wasn't there also concern for double validation performed during form clean
and then model instance save?

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CACS9rad0m22maOKrpn-T6vU7ZC2Y%3DK3V9P9%3DP_5Qf%3DEt0k4yTA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Nginx and Ubuntu Service Define

[Karen Tracey]

Please ask questions about using Django on django-users. The topic of this
list is the development of Django itself. Thank you.
Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CACS9rafgpk4bi5Xs2TR3zWHiyQTRh85AmSdo1K0EdG%3DMjQwktg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Django session not saved

[Karen Tracey]

Please ask questions about using Django on django-users. The topic of this
list is the development of Django itself.
Thanks,
Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CACS9rac0%2BvdBHvMgvpvrR%2BL_FVCqv7043nxo2Y5tAWYX8C_P_g%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: track user behavior in a django application

[Karen Tracey]

Please ask questions about using Django on django-users. The topic of this
list is the development of Django itself.
Thanks,
Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
For more options, visit https://groups.google.com/groups/opt_out.

Re: A help for development

[Karen Tracey]

Please ask questions about using Django on django-users. The topic of this
list is the development of Django itself.

Thanks,
Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Which Django library to bild fb app?

[Karen Tracey]

Please ask questions about using Django on django-users. The topic of this
list is the development of Django itself.

Thanks,
Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
For more options, visit https://groups.google.com/groups/opt_out.

Re: custom auth user

[Karen Tracey]

Please ask questions about using Django on django-users. The topic of this
list is development of Django itself.

Thanks,
Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Any Tutorials on Django similar to Web2py ????????????????

[Karen Tracey]

Please do not crosspost to both django-users and django-developers, pick
the right list and post there only. If you're interested a such a tutorial
from a learning perspective the correct list is django-users, not here. The
topic of this list is the development of Django itself (so if you were
interested in writing a tutorial, this might be the right place to post).

One question mark would also likely have been sufficient.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
For more options, visit https://groups.google.com/groups/opt_out.

Re: how get user session name in models django??

[Karen Tracey]

Please ask questions about using Django on django-users, and please do not
crosspost to both lists. The topic of this list is the development of
Django itself.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Django runfcgi umask: what is it meant to do and why?

[Karen Tracey]

git blame on the line that sets the umask shows it was as a result of
ticket #6994:

https://code.djangoproject.com/ticket/6994

Discussion in that ticket is probably the best information you are going to
get on rationale.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
For more options, visit https://groups.google.com/groups/opt_out.

Re: selected admin actions for a user, who is owner of one of the tenants in a multi tenant django crm app

[Karen Tracey]

Please do not crosspost to both django-users and django-developers: pick
the correct list and post there. The topic of this list is the development
of Django itself, questions about using Django are suited to django-users,
not here.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Send Mail Group Select from Employee Model

[Karen Tracey]

Please ask questions about using Django on django-users. The topic of this
list is the development of Django itself.

Thanks,
Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Question on Template Tags

[Karen Tracey]

Please ask questions about using Django on django-users. The topic of this
list is the development of Django itself.

Thanks,
Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: The _imaging C module is not installed. Anybody can help me?

[Karen Tracey]

Please ask questions about using Django on django-users. The topic of this
list is the development of Django itself.

Thanks,
Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Django+GoogleAppengine(datastore)

[Karen Tracey]

The topic of this list is the development of Django. Please ask questions
about (possibly) using Django on django-users. Thanks,
Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Making __repr__ safe by default

[Karen Tracey]

I agree with Anssi, repr should stay as-is. I do a lot of shell/pdb work
and I can't recall ever encountering a problem with "unsafe" repr. I think
many people would find it annoying if suddenly repr would tell you no more
than the pk of the object.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Adding a simple yes/no confirm before committing instance to database

[Karen Tracey]

Please ask questions about using Django on django-users. The topic of this
list is the development of Django itself.

Thanks,
Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re:

[Karen Tracey]

You posted this here less than an hour after posting on django-users, that
hardly seems time enough to consider it "ignored" there.

Also, you might want to include a subject in your emails, particularly for
high-traffic lists I would not be surprised if some people simply scan the
subjects for stuff that they think might be interesting or something they
may be able to answer. items with "(no subject)" as the subject may very
well get fewer readers than a subject that actually describes the
post/question/whatever.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: tutorial url broken

[Karen Tracey]

On Mon, Apr 29, 2013 at 1:52 PM, gilberto dos santos alves  wrote:

>
> Hi. on this url:: [1] we have this link url:: [2] broken.
>
> url:: [1] https://code.djangoproject.com/wiki/Tutorials
>
>
That's in the wiki, which is (generally, except for some pages which are
locked down due to abuse in the past) editable by the community.  If you
scroll to the bottom of the page, you'll see an "Edit this page" button, if
you press that you'll be able to edit the content and remove the no-longer
functioning link.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Newbie: import start end edit an existing django project

[Karen Tracey]

Please ask questions about using Django on django-users. The topic of this
list is the development of Django itself.

Thanks,
Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: facebook/twitter sharing, and testing

[Karen Tracey]

Please ask questions about using Django on django-users. The topic of this
list is the development of Django itself.

Thanks,
Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Implementing Full Text Search in Django --Ticket #3254

[Karen Tracey]

On Thu, Mar 21, 2013 at 9:51 PM, Luke Sneeringer wrote:

> I would expect that the biggest problem with implementing something like
> this would be that MySQL is going to be a tough cookie to address. InnoDB
> supports foreign key constraints but not full-text indexing, while MyISAM
> supports full-text indexing but not foreign-key constraints.
>
> So, either you can have data integrity, or you can have full-text
> indexing, but not both. And what happens when someone defines one or the
> other in Django and expects it to actually work…?
>

Django already supports full-text index searching on MySQL:
https://docs.djangoproject.com/en/1.5/ref/models/querysets/#search

The issue of creating the index is handled by punting to the user -- doc
notes you've got to create the full-text index yourself.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: memory leak in django 1.5

[Karen Tracey]

On Thu, Mar 21, 2013 at 9:00 PM, Craig de Stigter wrote:

> Hi everyone
>
> (cross-posted because this seems relevant to both django-users and
> developers, and both might have experienced this problem)
>
> We've noticed a gradual increase in memory usage for our apache processes
> since upgrading to django 1.5.
>
> Here is a graph  showing memory usage
> before and after we upgraded to django 1.5 on our web server. (the upgrade
> occurs at 12:30 on the graph).
>
> I'm hoping someone else has noticed a similar thing and is able to provide
> some insight.
>

https://code.djangoproject.com/ticket/19895#comment:6

notes a memory leak due to a fix that went into 1.5.

The fix was reverted on the 1.5.x branch about two days ago, so one thing
to try would be to run current 1.5.x branch level rather than released 1.5.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Django 1.4.4 and contrib/sessions/management/__init__.pyc

[Karen Tracey]

On Tue, Feb 19, 2013 at 10:12 PM, Nick Popoff  wrote:

> In the case of ./contrib/sessions/management/__init__.pyc an __init__.py
> is not provided.
>
> Is it possible compiled 2.7 .pyc files were included instead of .py files
> by mistake?
>

The .pyc files were certainly included by mistake, the tarballs should not
contain them. In the case of contrib/sessions/management, that directory
shouldn't exist in 1.4 at all, it's new in 1.5. So the corresponding .py
file isn't missing, the .pyc file is just (even more) extraneous.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Database pooling vs. persistent connections

[Karen Tracey]

On Mon, Feb 18, 2013 at 5:33 PM, Alex Gaynor  wrote:

> As far as I know, the MySQL timeout time is configurable, and the default
> is 8 hours.
>

Assuming this is what does:
http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html#sysvar_wait_timeoutthat
sounds right. I guess I have just managed to encounter a fair number
of servers who lowered that number. (I've mainly seen it from mysql shell
sessions, where I get a message about the server having gone away and the
connection being re-established if I've waited "too long" between
commands...pretty sure "too long" has never been anywhere near 8 hours).

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Database pooling vs. persistent connections

[Karen Tracey]

Just a couple of random quick thoughts:

Will persistent connections be able to ensure that "bad connections" (e.g.
those in state "current transaction is aborted, commands ignored until end
of transaction block") don't leak from one request to another?

MySQL, at least, will close a connection from the server side if it is idle
for too long (no idea if that is configurable, I've never had reason to
investigate...have just noticed the behavior). In the pull request it looks
like we only check for the need to close at the end of a request cycle? For
a very low activity site it seems those two behaviors could interact badly,
with the request cycle finishing code deciding to keep the connection
around since it's not too oldlong delay until next request while MySQL
server closes what it sees as an idle connection...next request tries to
use a connection that the server has closed?

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: PROBLEM WITH MY CUSTOMIZED save() method

[Karen Tracey]

Please ask questions about using Django on django-users. This list is for
the discussion of developing Django itself.

Thanks,
Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Error with GET 200 and GET 304

[Karen Tracey]

Please ask questions about using Django to django-users. This list is for
discussion of the development of Django itself.

Thanks,
Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Guidance regarding Django Deployment Process

[Karen Tracey]

Please ask questions about using Django on django-users. The topic of this
list is the development of Django itself.

Thanks,
Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Problem with Custom Manage.py command and Crontab

[Karen Tracey]

Please ask questions about using Django on django-users. The topic of this
list is the development of Django itself.

Thanks,
Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: How can i use Knockout Java Script with my Django Project?

[Karen Tracey]

Please ask questions about using Django on django-users. The topic of this
list is the development of Django itself.

Thanks,
Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: search across models

[Karen Tracey]

You also posted this to django-users, which is where it belongs. Please do
not crosspost usage questions to django-developers; the topic of this list
is the development of Django itself.

Thanks,
Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: python_2_unicode_compatible pitfalls

[Karen Tracey]

On Thu, Dec 27, 2012 at 7:15 PM, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:

> 2) under Python 2.x __str__ is implemented as __unicode__
>encoded to utf8.
>
>
> Yes, this is a legacy behavior that I strongly disagree with. It
> makes __str__ / __unicode__ handling for Model subclasses
> exceedingly sketchy.* The only reason why I didn't remove
> it is backwards compatibility.
>

I'm curious what would you do instead, if backward-incompatibility were not
a concern?

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: A regression that isn't a regression

[Karen Tracey]

This has come up before, see: https://code.djangoproject.com/ticket/17974

1.3 is security-fix only at this point, we'd have to make a pretty big
exception to put anything into 1.3 to warn users of their mis-use of an
undocumented parameter to distinct

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: New to Django; walking through djangoproject tutorial; can't get poll to work

[Karen Tracey]

Please ask questions about using Django on django-users. The topic of this
list is the development of Django itself.

Thanks,
Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Charset for URL decoding (#19468)

[Karen Tracey]

On Tue, Dec 18, 2012 at 3:34 AM, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:

>
> Currently, Django uses utf-8. As far as I can tell, that's more a
> side-effect of (ab)using force_str than anything else. It also has the
> drawback of making it impossible to serve perfectly legit HTTP URLs such
> as /caf%E9/ — try it: https://www.djangoproject.com/caf%E9/ — that
> returns a 400 with no content. I think I once saw a ticket about this, but
> I can't locate it right now.
>


I think it is:

https://code.djangoproject.com/ticket/5738

Comment #10 notes that utf-8 is what Django will use but with the last fix
noted against that ticket it is easier for the request class to be
subclassed to change things for an installation where a different charset
for decoding might be desired.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Possible bug with GenericRelations and values_list

[Karen Tracey]

On Mon, Dec 10, 2012 at 8:58 PM, Skylar Saveland
wrote:

>
> I posted this in the django-users group but I think it may merit posting
> here, as well. I have a test case which I think should pass.
>
>
> https://github.com/skyl/django/commit/556df1c46146c2fc9c4022d838fa23f652f0ea8d
>
> Is this a bug? If so, is it a bug that is not in the tracker?
>
>
I'd say it's a bug. I can't find an exact match in trac but I'd guess the
root cause is similar to what's underlying:

https://code.djangoproject.com/ticket/11387

The SQL for the query in your test case that attempts to fetch the Animal
object tags using values_list is:

SELECT "generic_relations_taggeditem"."id" FROM "generic_relations_animal"
LEFT OUTER JOIN "generic_relations_taggeditem" ON
("generic_relations_animal"."id" =
"generic_relations_taggeditem"."object_id")

This suffers from the same problem as the sql in #11387: it's not including
any restriction on content type in the query, thus you can get tags that
are pointing to non-Animals.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Blocker for 1.5 - representation of filesystem paths in Django

[Karen Tracey]

My preference is for option 2: convert file system paths to unicode and use
unicode internally as much as possible. This is consistent with what we
have been doing/recommending for years, even if it is at odds with Python's
default for 2.X. See for example:

https://code.djangoproject.com/ticket/9579

fixed by:

https://github.com/django/django/commit/dfa90aec1b

which converts the file system paths returned by Python to unicode for
future use.

#9579 was essentially the same problem we are again facing in #19357, only
the unicode literals change has made it way more widespread. I think we
should approach #19357 in a consistent fashion with recommendations we have
made ever since adding unicode support to Django: convert to/from unicode
at the edges, use unicode internally. True, this is somewhat at odds with
Python's 2.X behavior/default, but we found Python's behavior in 2.X to be
unworkable for practical unicode support so I'm not particularly concerned
with "going against" the way Python 2.X does things...Python 2.X is broken
here, in my opinion.

It is true this approach may introduce regressions for people who do not
have their environment locale properly configured such that os.
getfilesystemencoding() returns a value that can be used to decode their
file system paths. But these systems are already broken and it's just
accident that they have not run afoul of the problem yet. We have been
noting the need for proper system configuration for years:

https://code.djangoproject.com/ticket/11030#comment:5
https://code.djangoproject.com/ticket/9696#comment:10
https://code.djangoproject.com/ticket/13550#comment:3

The current documentation on this need, however, is still buried (though at
least is is no longer in the mod_python doc only) and makes it sound like
this is only necessary in some rare cases:

https://docs.djangoproject.com/en/dev/howto/deployment/wsgi/modwsgi/#if-you-get-a-unicodeencodeerror

That note should be moved to somewhere more prominent (
https://docs.djangoproject.com/en/dev/howto/deployment/ ?) and re-written
since the problem will now be more widespread and not only crop up during
file uploads of files with non-ascii characters in their names. Likely the
release notes should have an item noting this, assuming we go with option 2
to fix it.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: how to write a text editing in the webpage using django

[Karen Tracey]

Please ask questions about using Django on django-users. The topic of this
list is the development of Django itself.

Thanks,
Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Google groups - possible issues with deleted posts.

[Karen Tracey]

On Fri, Nov 16, 2012 at 12:25 PM, Tom Christie wrote:

> Be aware that there may be issues with google groups at the moment...


Sigh.


> There are two messages in this 
> thread
>  that
> are marked as deleted, apparently not 
> intentionally
> .
>

These got caught in the sometimes inexplicable "this looks like spam even
though it came from an allowed poster" filter. For these GG puts them in
the moderation queue but does not send an immediate email to
moderatorsit sends email sometimes days later, though in this case it
seems to have sent that email the email with only a 12 hour or so delay.
The emails in the "moderator's spam report" note were:

--- 1 of 3  ---
> Subject: django.contrib.redirects customisation
> From: "Лебедев Илья" 
> Date: Nov 15 03:22PM +0400
>
> Recently I needed functionality just like in django.contrib.redirects -
> redirects table, that can be edited in admin. I was sad to find out that
> its strongly not configurable. For example, I dont need status 301, but
> need something else.
>
> Approve:
> http://groups.google.com/group/django-developers/pendmsg?view=full_id=3390956786051711982
>
> --- 2 of 3  ---
> Subject: Re: Class based views: A standard hook for
> http-method-independent code
> From: George Hickman 
> Date: Nov 15 04:27AM -0800
>
> I have a slightly different proposal, one where we can avoid the extra hook
> but hopefully cover everyone's use cases too.
>
>
> https://github.com/ghickman/django/commit/85ac39a481074c25af1ed72a7a12e62ff5425e54
>
> I've personally never liked the
>
> Approve:
> http://groups.google.com/group/django-developers/pendmsg?view=full_id=548044182767120459
>
> --- 3 of 3  ---
> Subject: Re: Class based views: A standard hook for
> http-method-independent code
> From: George Hickman 
> Date: Nov 15 01:24PM -0800
>
> Apologies if this is a double reply, I think Google Groups might have
> deleted my last post...
>
> I'd like to suggest a slight tangent to the proposed feature that hopefully
> covers what everyone seems to be looking for.
>
>
> Approve:
> http://groups.google.com/group/django-developers/pendmsg?view=full_id=7023679753100488970
>

(Can anyone see anything in any of these messages that would cause GG to
think they were spam??)

Anyway, I did delete the last of these, since it was a duplicate due to the
moderation hold up. The other two I moderated through. The first shows up
in both the group and my email records for the list. The second apparently
only got sent out via email, I have no idea why it doesn't show up in the
group (but it did go out to email subscribers -- I have it and there's a
response to it in the group). I know the same thing has happened before,
where something held in this "might be spam" filter, after being approved,
went out in email but never appeared in the group archive. But that
apparently doesn't happen all the time since the first message in this
batch does appear in the group.


> There are also three messages in this 
> thread,
> all around the same timeframe which are marked as deleted, which seems a
> little suspect.
>

I have no idea what those might have been. I do recall deleting 4 spam
messages, I think yesterday, I think from the dev group. Two had subjects
along the lines of "sexy teen hot bodies" and two were google talk invites.
Ordinarily I would have just deleted the google talk invites as
non-intentional spam, but they were from the same address as the real spam
so I marked them all as spam, which has the side-effect of banning the
poster. It's possible that even with the different subject lines they were
posted to that thread..but from my recollection there were 4, not 3, so I
have no idea if those that I remember connect to the three deletions noted
in that thread. I don't recall deleting any other messages from the dev
group moderation queue in the last few days.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Feature request: collectstatic shouldn't recopy files that already exist in destination

[Karen Tracey]

On Thu, Sep 27, 2012 at 12:51 PM, Dan Loewenherz wrote:

> The problem I've run into is that collectstatic copies all files,
> regardless of whether they already exist on the destination.


No, as noted in the ticket, which has been closed needsinfo, staticfiles
already only copies modified files. And I don't think that's a
recently-added feature, so I suspect the behavior you are seeing has more
to do with the S3 side than the staticfiles code. This post:

http://stackoverflow.com/questions/6618013/django-staticfiles-and-amazon-s3-how-to-detect-modified-files

looks enlightening though even that is not all that new. It sounds like the
problem here is efficiently getting the last-modified time for the files
out in S3, not with staticfiles.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: DatabaseFeatures and supports_transactions

[Karen Tracey]

On Tue, Sep 25, 2012 at 11:24 AM, maxi <maxiroba...@gmail.com> wrote:

> El martes, 25 de septiembre de 2012 09:05:47 UTC-3, Karen Tracey escribió:
>
>> First, this method is used during testing, generally not during normal
>> operation. It's implemented as a cached property so regardless of how many
>> times the value is tested the underlying code which creates and drops a
>> table is only actually called once per database. Is it needed? We need to
>> know if the database actually supports transactions or if
>> commit/rollback/etc are simply no-ops. If you know of an alternative way of
>> determining this, that works across all databases, please share. I added
>> that code and I've never liked it but I don't know of another way to
>> accomplish what it needs to do.
>>
>>
> No, I just answer because it caught my attention. Why not just trust in a
> True/False property ?
> BTW, What do you mean with "commit/rollback/etc are simply no-ops" ?
>
>
We have no single value we can set for this property for MySQL; whether
that DB supports transactions is dependent on the configuration of the DB
server. If the MySQL server is configured to use the MyISAM storage engine,
then all transaction methods such as commit and rollback simply do nothing
(are no-ops).


> I'm working on django-firebird backend implementation (now using the new
> firebird python-driver "fdb") and I need reimplement supports_transactions,
> because I need to commit any work before drop the table, otherwise, I fall
> into "Object in use" error.
>

That seems odd. What does "object in use" mean? The routine is currently
coded to:

1 - create table
2 - commit #1
3 - insert row into table
4 - rollback #3
5 - select count of rows in table
6 - read result of #5
7 - drop the table

You need to commit before #7? Doesn't seem like that should be necessary.
Can you elaborate on why Firebird thinks it is necessary?

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: DatabaseFeatures and supports_transactions

[Karen Tracey]

On Mon, Sep 24, 2012 at 10:15 PM, maxi  wrote:

> Hi,
>
> DatabseFeatures class has a supports_transactions property for test if the
> db engine support transactions.
> supports_transactions implementation makes  some metadata alters to check
> this behaivor.
>
> Now, is really needed to do this to check transaction support?
> I don't know exactly how many times this supports_transactions is called
> but I think what it produce unnecessary alterations in database structure,
> or I'm misinterpreting how it supposed works.
>
>
First, this method is used during testing, generally not during normal
operation. It's implemented as a cached property so regardless of how many
times the value is tested the underlying code which creates and drops a
table is only actually called once per database. Is it needed? We need to
know if the database actually supports transactions or if
commit/rollback/etc are simply no-ops. If you know of an alternative way of
determining this, that works across all databases, please share. I added
that code and I've never liked it but I don't know of another way to
accomplish what it needs to do.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: #3011 - Custom User Models -- Call for final review

[Karen Tracey]

On Sun, Sep 16, 2012 at 9:13 AM, Anssi Kääriäinen
wrote:

> I meant to say that after this is committed to 1.5, should we allow for
> some polishing changes to get in after feature freeze even if they are
> technically feature additions.
>

The kinds of changes you are describing can, I believe, be made after alpha
(i.e. feature freeze). Major features like this one may very well need some
additions/polishing after landing on master, once many more people start to
experiment with them and find out what is needed/useful/etc. The intent of
"feature freeze" is to stabilize the code base in general and not introduce
side-effect bugs that may go unnoticed until after release if made late in
a release cycle.

For big brand-new features, sticking to a hard "feature freeze" line after
alpha is more likely to be harmful than helpful, and I don't believe we've
ever taken that sort of hard line for major features. It's even possible
(though clearly not desirable) to introduce backwards-incompatible changes
in the public interfaces for a new feature between alpha/beta/final. In
this phase we're seeking to gather feedback from early adopters and
experimenters, and not being able to incorporate that feedback into the
in-progress release would be silly.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Is there any plan to improve the performance of "render"?

[Karen Tracey]

On Wed, Sep 12, 2012 at 12:56 PM, 富弘刘  wrote:

> I use django-debug-toolbar to analyze my website and noticed a lot of time
> is consumed by template render. In my each page, I have about 10ms in
> database queries, and about 100 ms in render.


Have you tried using the cached template loader (see
https://docs.djangoproject.com/en/1.4/ref/templates/api/#loader-types)?

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: DJango and OrientDB

[Karen Tracey]

On Tue, Sep 11, 2012 at 10:22 PM, Sajjada Akhter wrote:

> My question was should I write db driver etc but I do so I will need to be
> able to participate in framework Dev right?
>
>
You'll have a wider audience who may be able to answer this question:

> I am not sure if i should just use simiple pyorient like library to
access orientDB or should i write new db driver etc

on django-users. This seems to be asking if you should use an existing
library (not Django ORM interface) to access this OrientDB or if you should
write a new Django DB backend (this providing Django ORM interface) to
access this DB. The answer to that question in large part depends on
whether it is worthwhile, for you, given your anticipated needs, to go to
the effort of writing a new backend to get the Django ORM interface or if
the existing library you mention might be easier and sufficient for your
needs.

If you do decide to go the route of writing a new DB backend, that does not
have to be added as part of core Django. While Django has a set of
core-included backends (PostgreSQL, MySQL, Oracle, sqlite) there are others
that are not part of Django and externally maintained (mssql, IBM DB2,
firebird). This list might be useful for asking specific technical
questions when embarking on writing a new DB backend, but for the larger
question you seem to be asking first I think django-users would offer more
useful feedback on your question. There's a greater chance, for example,
that someone on django-users already has experience with the library and DB
you are looking at.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: DJango and OrientDB

[Karen Tracey]

Please ask questions about using Django on django-users. The topic of this
list is the development of Django itself.

Thanks,
Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Example on bitmap charts

[Karen Tracey]

Please post questions about using Django to django-users. The topic of this
list is the development of Django itself.

Thanks,
Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: After form validation, need to post and call a perl program to display to a log file

[Karen Tracey]

Please do not crosspost to both django-users and django-developers. -users
is for discussions centering around using Django, that was the right list
for this question. -developers is for discussions of the development of
Django itself.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Can someone help me on how to handle this scenario ?

[Karen Tracey]

Please ask questions about using Django on django-users. The topic of this
list is the development of Django itself.

Thanks,
Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: ManyToManyField

[Karen Tracey]

Please ask questions about using Django on django-users. The topic of this
list is the development of Django itself.

Thanks,
Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Need Django experts to explain some of my questions in bay Area, CA

[Karen Tracey]

Please ask for help like this on django-users, not here. The topic of this
list is the development of Django itself.

Thanks,
Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: #18557: get_or_create() causes a race condition with MySQL

[Karen Tracey]

On Thu, Aug 9, 2012 at 5:58 PM, Cal Leeming [Simplicity Media Ltd] <
cal.leem...@simplicitymedialtd.co.uk> wrote:

> Sorry, please ignore that last message, I see now that you
> were referring to this:
>
> https://docs.djangoproject.com/en/dev/ref/databases/#autocommit-mode
>
> So essentially, the official documentation would state that to resolve
> this problem, you would use the following for your db settings:
>
> 'OPTIONS': {
> 'autocommit': True,
> }
>
> Is that correct?
>

No...that syntax is pulled out of a PostgreSQL doc note and I don't think
it would work with MySQL, though I am not entirely sure of that.

Also I am not sure I would recommend a global DB level setting for this --
you're dispensing with any transactions at that point, which may well be
inappropriate for an app that is having trouble with get_or_create. It's
very hard for Django to give explicit instructions for what is best to do
"in general" since it all depends on the needs of the application with
respect to transactions. I would say in general I'd recommend "read
committed" isolation level vs. database-level autocommit, but the ticket
noted that read committed "can break legacy apps" (why, I'm not sure, and
it doesn't explain), so for the sake of completeness I mentioned that
database level autocommit would also fix the race condition that exists in
get_or_create.

I don't believe the doc can give a blanket "do this and your code will
work" statement here. It can say Django's own code in get_or_create
requires either that the transaction isolation level be set to "read
committed" or DB level autocommit be used. Whether that is best done for
the project globally via an init_command or only for certain requests via
explicit cursor commands (see
http://groups.google.com/group/django-users/msg/55fa3724d2754013) depends
on the project itself and what else it is doing besides calling
get_or_create.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Separate file stream from request input stream during file uploading

[Karen Tracey]

This question was answered on the django-users list where it was also
posted. Please do not cross-post to both lists. The right list for usage
questions like this is django-users.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: #18557: get_or_create() causes a race condition with MySQL

[Karen Tracey]

On Wed, Aug 8, 2012 at 9:25 AM, Cal Leeming [Simplicity Media Ltd] <
cal.leem...@simplicitymedialtd.co.uk> wrote:

> I'm not entirely sure that suggesting every query needs to be committed is
> the right way forward either, given that you only need to commit once
> before get_or_create() is called to prevent the issue.
>
> Could you expand on why you feel every query would need to be committed?
>

get_or_create does:

1 - get
2 - if get fails due to DoesNotExist, create
3 - if create fails due to IntegrityError, get again

The problem with repeatable read transaction level is that step 3 can never
return something other than what was found (or not) in step 1. If some
other thread, between the times at which 1 and 2 happen, creates what this
thread is attempting to get_or_create, then the get_or_create is going to
fail, because the get will still find nothing in step 3, causing
get_or_create to re-raise the IntegrityError from step 2.

Issuing a commit before calling get_or_create doesn't fix this race
condition that exists within the get_or_create code itself. Such a pre-call
commit is only going to be helpful if the current transaction has already
done a read that has fixed what is going to be returned by the DB in step
1. If that has happened, then committing before calling get_or_create will
reduce the likelihood of hitting the race condition, since step 1 may then
read a row that has been created subsequent to the last read by this thread
but before this thread gets to step 1 in get_or_create. Essentially the
pre-commit narrows the race condition window in this case. (If no read has
yet been done by the transaction to already set in stone what this
transaction will read in step 1, then committing before calling
get_or_create does not help at all.)

Regardless of what's done before the call into get_or_create, there's still
a small window of opportunity, between steps 1 and 2, for get_or_create to
fail. get_or_create requires either DB level autocommit or read committed
transaction isolation level in order for it to be free of this race
condition. Recommending anything else in Django's docs would be misleading.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: #18557: get_or_create() causes a race condition with MySQL

[Karen Tracey]

On Wed, Aug 8, 2012 at 8:13 AM, Cal Leeming [Simplicity Media Ltd] <
cal.leem...@simplicitymedialtd.co.uk> wrote:

> Does anyone else have any input at this stage??
>
> It seems to me that the most appropriate way forward is a documentation
> update which explains that get_or_create() is not atomically safe across
> all databases, and may need a commit() before hand, or a read isolation
> change (with warnings about both).
>
>
The docs should note that READ COMMITTED isolation level, or database-level
autocommit of every query, is required for get_or_create() to work properly
under MySQL. Recommending an alternative of a commit beforehand strikes me
as wrong.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Add a form to admin side

[Karen Tracey]

Please ask questions about using Django on django-users. The topic of this
list is the discussion of the development of Django itself.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: how a field and its value can be found in a queryset object

[Karen Tracey]

Please ask questions about using Django on django-users. The topic of this
list is the development of Django itself.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: horizontal alignment of forms in a formset without ajax

[Karen Tracey]

Please ask questions about using Django on django-users. The topic of this
list is the development of Django itself.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: (Model)Forms localize=True violates DRY

[Karen Tracey]

On Fri, Jun 22, 2012 at 7:23 AM, Klaas van Schelven <
klaasvanschel...@gmail.com> wrote:

> I've created a ticket, but have always understood that calling
> attention to tickets should be done separately on the Django-
> developers mailinglist


It's not necessary nor encouraged to call attention to newly-opened tickets
on the -developers list. People are asked to post to the list in preference
to "contesting" a resolution the don't agree with (e.g. wontfix).
Newly-opened tickets on the other hand don't need to be announced on the
list, plenty of people monitor the flow of incoming tickets.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: ModelForms and the Rails input handling vulnerability

[Karen Tracey]

On Tue, Jun 12, 2012 at 10:10 PM, Alex Ogier  wrote:

> No one can sneak extra unexpected fields past a developer by editing HTML
> client side, because if the field wasn't rendered to HTML it's not
> going to validate.
>

But it may. If you have a template which renders specific fields, and yet
the form is set to allow a wider set of fields than are actually rendered,
client-side editing CAN result in the form allowing change to a field that
had not been rendered in the template. The Django ModelForm doesn't know
what fields were actually rendered in the HTML, it only knows what fields
have been included/excluded from the ModelForm. You can post data for a
field that was not rendered and it may pass validation and get saved.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Custom ForeignKey which does not require referential integrity?

[Karen Tracey]

Please do not crosspost to both django-users and django-developers. Pick
the right list and post there. This seems to be more appropriate for
discussion on django-users than here.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: DJango 1.3 - BundleError while rendering

[Karen Tracey]

Please ask questions about using Django on django-users. The topic of this
list is the development of Django itself.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Django models and different types

[Karen Tracey]

Please ask questions about using Django on django-users. The topic of this
list is the development of Django itself.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: NoneType object has no attribute in POST/PUT a resource with nested resources (django, tastypie)

[Karen Tracey]

Please ask questions about using Django on django-users, not here. The
topic of this list is the development of Django itself. (Also when you post
to django-users for this problem it would help people help you if you
included the full traceback you are getting.)

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Test reordering and TransactionTestCase cleanup

[Karen Tracey]

On Mon, May 7, 2012 at 5:50 PM, Anssi Kääriäinen wrote:

> I would like to just get rid of the sequence resets. Oracle doesn't do
> it currently, TestCase doesn't do it, and IMO assuming the IDs are
> going to start from 1 is an assumption one should not make.
>
> Objections to just getting rid of the sequence resets altogether (with
> the opt-in flag)?
>

I did not realize Django code was doing something explicit to reset
sequences during the database flush between TransactionTestCases, I thought
it just happened as a side-effect of the method used to clear the DB. I
don't believe tests should be relying on pk values starting with 1, if
that's the only reason the sequence resets are there I think we should get
rid of them.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: How to serve staticfiles with full URL for local development?

[Karen Tracey]

Please ask questions about using Django on django-users. The topic of
this list is the development of Django itself.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Test reordering and TransactionTestCase cleanup

[Karen Tracey]

On Fri, May 4, 2012 at 4:46 AM, Andreas Pelme  wrote:
>
> That's a good question. Anyone who wrote to original 
> TransactionTestCase/reordering implementation that wants to chime in? :-)

I worked on the test speedups that introduced TransactionTestCase and
I added the re-ordering, but the behavior of database flush being done
at the beginning of a test existed before that work. The conversation
that led to addition of the reordering is here:

http://groups.google.com/group/django-developers/browse_thread/thread/1e4f4c840b180895/

doctests (which we have no more?) play a prominent role in that
discussion. While we have gotten rid of doctests in Django's own
suite, we still support apps which may use doctests in their code, so
anything we do to change when the DB is cleared needs to take that
into account. On the table then was the idea of adding cleanup after
doctests, possibly that would need to be re-considered if you want to
move the database clearing to the end of everything rather than the
beginning of TransactionTestCase.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Test reordering and TransactionTestCase cleanup

[Karen Tracey]

On Thu, May 3, 2012 at 12:29 PM, Andreas Pelme  wrote:
>
> Djangos default testrunner reorders the test suite to run all TestCase tests 
> before TransactionTestCases, which avoids this problem. I cannot find this 
> reordering documented anywhere,

It is documented:
https://docs.djangoproject.com/en/1.4/topics/testing/#django.test.TransactionTestCase

Mentioned in both the 3rd paragraph and the note.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: (List object(Recently Added - Most Common

[Karen Tracey]

Please ask questions about using Django on django-users. The topic of
this list is the development of Django itself.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: GitHub migration planning

[Karen Tracey]

On Wed, Apr 18, 2012 at 6:55 PM, Dalton Barreto  wrote:
>> Maybe the best way to avoid that people create issues on github is to
>> disable it for the
>> official repository. This is possible through the Github's Admin interface.
>>
>
> Hmm, this would probably disable pull requests too

No, it does not, unless I am mis-understanding what you are saying.

https://github.com/django/django/

has no issues (issues is unchecked in admin area), but it has pull requests.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Admin custom function calls

[Karen Tracey]

Please ask questions about using Django in django-users. The topic of
this list is the development of Django itself.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: list of function to django view

[Karen Tracey]

Please ask questions about using Django on the django-users mailing
list. The topic for this list is the development of Django itself.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Django participation in Google Summer of Code 2012

[Karen Tracey]

On Thu, Mar 8, 2012 at 10:29 AM, Joe & Anne Tennies  wrote:
> [snipped] It's mostly done at this point. It got done just before
> the 1.4 lockdown, but it was too much risk to take on that late in the
> release cycle.

Also it's more cleanly done if we can drop support for Python 2.5,
which argued for targeting Django 1.5 (and dropping Python 2.5 support
in that release).

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: no fixtures found error

[Karen Tracey]

Please ask questions about using Django on django-users. The topic of this
list is the development of Django itself.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: How to show the template reserved keyword on html.

[Karen Tracey]

Please ask questions about using Django on django-users. The topic of this
list is the development of Django itself.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Moderation broken

[Karen Tracey]

On Sat, Jan 28, 2012 at 3:53 AM, Alec Taylor  wrote:

> Ah great, well at least now we know it won't happen again :D
>
>
Except the moderation emails are still broken -- we're not getting any.
Google groups help/problem reporting facilities are nonexistent. All I can
find is reports of other people with other groups experiencing the same
issue, posting on their groups that moderation is likely to be slow until
if/when Google wakes up and fixes the problem. Right now moderation relies
on moderators remembering to check periodically if there are messages in
the queue.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Multi-TZ should be in release notes

[Karen Tracey]

On Mon, Dec 26, 2011 at 12:58 AM, Jeremy Dunck  wrote:

> I think Multi-TZ should get soms love in the release notes.
>
> https://code.djangoproject.com/changeset/17106
>
> https://docs.djangoproject.com/en/dev/releases/1.4-alpha-1/
>
> Was it an oversight?
>
>
It's here:

https://docs.djangoproject.com/en/dev/releases/1.4-alpha-1/#support-for-time-zones

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Django-nonrel patches

[Karen Tracey]

On Mon, Dec 12, 2011 at 9:53 AM, Wilfred Hughes wrote:

> Following up on #17338 ([nonrel] supports_deleting_related_objects
> database feature flag):
>
> carljm said that:
>
> > [Django] is (sort of) _emulating_ SQL cascading deletes, but it does so
> in a way that doesn't assume anything at all from the backend.
>
> I'm not sure this is correct. If I define the following models:
>
> from django.db import models
>
> class Person(models.Model):
>name = models.CharField(max_length=100)
>
>
> class Car(models.Model):
>name = models.CharField(max_length=100)
>owner = models.ForeignKey(Person)
>
> Related objects are indeed deleted on a sqlite Django project:
>
> In [1]: from vortaro.models import Person, Car
>
> In [2]: p = Person.objects.create(name='bob')
>
> In [3]: c = Car.objects.create(name='robin reliant', owner=p)
>
> In [4]: p.delete()
>
> In [5]: Car.objects.all()
> Out[5]: []
>
> In [6]: from django.db import connection
>
> In [7]: connection.queries
> Out[7]:
> [{'sql': u'INSERT INTO "vortaro_person" ("name") VALUES (bob)',
>  'time': '0.001'},
>  {'sql': u'INSERT INTO "vortaro_car" ("name", "owner_id") VALUES
> (robin reliant, 1)',
>  'time': '0.001'},
>

This SELECT:


>  {'sql': u'SELECT "vortaro_car"."id", "vortaro_car"."name",
> "vortaro_car"."owner_id" FROM "vortaro_car" WHERE
> "vortaro_car"."owner_id" IN (1)',
>  'time': '0.001'},
>  {'sql': u'DELETE FROM "vortaro_car" WHERE "id" IN (1)', 'time':
> '0.000'},
>

And the above subsequent delete of a votaro_car are Django finding the cars
referencing the to-be-deleted Person and deleting them, before deleting the
Person, which comes next.


>  {'sql': u'DELETE FROM "vortaro_person" WHERE "id" IN (1)', 'time':
> '0.000'},
>  {'sql': u'SELECT "vortaro_car"."id", "vortaro_car"."name",
> "vortaro_car"."owner_id" FROM "vortaro_car" LIMIT 21',
>  'time': '0.000'}]
>
> This isn't making a second query to deleting the Car model, it is
> depending on the database to do this.


Django did explicitly find-and-delete the Car. It did not rely on the
underlying database to do that.


> For comparison, here's the same
> on App Engine:
>
> In [1]: from test_app.models import Person, Car
>
> In [2]: p = Person.objects.create(name='bob')
>
> In [3]: c = Car.objects.create(name='robin reliant', owner=p)
>
> In [4]: p.delete()
>
> In [5]: Car.objects.all()
> Out[5]: []
>
> In [6]: c = Car.objects.get()
>
> In [7]: c.owner
> ---
> DoesNotExist  Traceback (most recent call
> last)
> /home/wilfred/bleeding_edge/django-testapp/ f94c13ea1b0a> in ()
> > 1 c.owner
>
> /home/wilfred/bleeding_edge/django-testapp/django/db/models/fields/
> related.pyc in __get__(self, instance, instance_type)
>313 rel_obj = rel_mgr.using(db).get(**params)
>314 else:
> --> 315 rel_obj =
> QuerySet(self.field.rel.to).using(db).get(**params)
>316 setattr(instance, cache_name, rel_obj)
>317 return rel_obj
>
> /home/wilfred/bleeding_edge/django-testapp/django/db/models/query.pyc
> in get(self, *args, **kwargs)
>349 if not num:
>350 raise self.model.DoesNotExist("%s matching query
> does not exist."
> --> 351 % self.model._meta.object_name)
>352 raise self.model.MultipleObjectsReturned("get()
> returned more than one %s -- it returned %s! Lookup parameters were
> %s"
>353 % (self.model._meta.object_name, num, kwargs))
>
> DoesNotExist: Person matching query does not exist.
>
> Have I horribly misunderstood?
>
>
It seems the problem here is that Django's attempt to find the Cars
referencing the to-be-deleted person is failing here, so it did not delete
the associated Car. It would if it could find it though, really it's not
using database cascade delete for this.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Adding Support for PyMySQL (for Python 3)

[Karen Tracey]

On Thu, Dec 8, 2011 at 2:40 AM, Vinay Sajip  wrote:

> On Dec 8, 6:46 am, Ian Clelland  wrote:
> >
> > There also seem to be a number of unicode-related errors there (mixed
> > collations; unrecognized characters) -- Could that be related to the
> lines
>
> I'm also getting the same errors on 2.x with the 2.x adapter on
> unpatched Django - so it might well be to do with my MySQL
> installation (stock 5.1.58 for Ubuntu 64-bit).


For all the Django test suite tests to pass, you must have a test database
that uses the utf-8 encoding, not latin1. (The tests uses characters that
have no encoding in latin1.) See the note under:
https://docs.djangoproject.com/en/1.3/internals/contributing/#using-another-settings-module.
If your MySQL install hasn't been configured to use utf8 instead of latin1
by default then you can set TEST_CHARSET to get the test database created
with the necessary encoding.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Bug: When editing unique_togethers in a modelformset you can't reverse values

[Karen Tracey]

On Wed, Dec 7, 2011 at 6:21 PM, Russell Keith-Magee  wrote:

> I don't consider it a bug
> that Django exposes a database error in this case.
>

I didn't hear what sounded like a database error in this case. The original
note says:

Upon attempting to save, you'll receive an error message stating,
"Production with this Person and Title already exists."

That sounds like pre-save validation refusing to attempt to save because it
believes an IntegrityError will be raised. I haven't checked the code but I
wouldn't be surprised if the unique validation works by checking for an
existing dupe among the other submitted/modified inlines and the db,
excluding just the pk of what it is currently attempting to verify will not
be a dupe with its new values. That approach would flag this direct swap
case as a validation error.

Whether that's a bug, I'm not convinced.

While it is true that the final state here won't violate the unique
together constraint, the intermediate state of getting there, given initial
state, WILLL violate the unique together constraint. There's no way (I
don't think, though I could be wrong) for the unique checking code to know
if current to final state is going to be done in a single transaction (nor
whether the DB in use is going to support deferring the constraint checking
to the end of the transaction). Seems to me safest thing for the unique
validation code to do is raise the validation error here.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.