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
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 r
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
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 w
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 annoy
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 bec
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 it
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
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
"D
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
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 s
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 necess
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 Djang
t (so developers can hopefully "see"
the warnings if just logged as such) and MySQL has moved more towards
having strict mode be the default.
I think it would make sense to get rid of this behavior and just log MySQL
warnings as warnings.
Karen
--
You received this message because you ar
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 e
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 receiv
--
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@goog
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
>
>
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 fr
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 he
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 re
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 receiv
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 receiv
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 receiv
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 receiv
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 receiv
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 receiv
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 e
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
inte
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 a
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
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
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 receiv
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 receiv
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 receiv
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 receiv
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
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 receiv
bjects 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 subs
own 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 beca
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 receiv
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 receiv
s 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
d 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 ra
ed 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 mess
ure "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
nnection 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 t
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 receiv
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
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 receiv
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 receiv
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 receiv
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
"D
ode__ 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 subscrib
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 me
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-
ment #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
t; =
"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
itten
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 subsc
On Sun, Nov 18, 2012 at 12:21 AM, Jared Martin wrote:
> I don't mean to wake a dead dog, but what has become of this? I came
> across this problem today. For now, I've subclassed. But it should be
> fixed, right?
>
>
Yes, it should be fixed. Per the ticket referenced it was fixed two years
ago. Th
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-
eleted 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 recollec
ightening 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
On Tue, Sep 25, 2012 at 11:24 AM, maxi 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
e 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.
Ka
ly 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@g
ader (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 fr
e,
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 unsu
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-
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-
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
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-
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-
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-
t 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 m
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"
der 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
) 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
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
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-
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-
f 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-de
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 pos
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"
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-
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-
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
r 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"
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-
ests, 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
oproject.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-developer
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-
y 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
&q
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-
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
ython 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
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-
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-
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.
Kare
>
>
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 unsubscr
1 - 100 of 464 matches
Mail list logo