Hi Bill,
We ended up using a package called Django-audit-log:
https://pypi.org/project/django-audit-log/.
It’s outdated now, but we used the source code for their CreatingUserField,
LastUserField, CreationDateTimeField, and ModificationDateTimeField. More
modern packages may have enhanced
I reviewed some of the history of this ticket. I tend to agree with the
criticisms of adding something akin to an AdminURL to the Django admin.
However, the idea of custom views to apps in the admin is an idea that I find
appealing. The history of this ticket features a comment from Tim Graham
I personally like the current behavior. If I don't have a translation prepared
for a certain text, I want it to fall back on the default text. Saying that,
how about Django incorporate a management command of some sort that can be used
to examine the translation files and return the texts that
I agree with your sentiment, Tom. I would add that we could get a more
“SPA-feel” by using HTML over the wire or htmx, which requires minimal
JavaScript.
From: django-developers@googlegroups.com
On Behalf Of Tom Carrick
Sent: Wednesday, April 19, 2023 5:07 AM
To:
Happy New Year!
I've been reading this thread with keen interest since James first brought it
up. I think James's rationale is on point and that the back port to fix the bug
needs to be done.
To the future of async,
Matthew
-Original Message-
From: django-developers@googlegroups.com
I’m not on the technical board or of any important part of the Django ecosystem
at all, but I do have an idea. It would be nice to revamp the “name” field in
the default user model, perhaps to have one field for the name as suggested
here from the W3C:
Hello,
I ran into an issue with a models.URLField because it limits the size of the
field to 200 characters. I find this too short to my use case. I have a valid
URL to an external website (in academia), and it won't fit in the Django
URLField.
This took me down a rabbit hole and this very
I wonder if maybe you should look at the APPEND_SLASH setting.
https://docs.djangoproject.com/en/4.1/ref/settings/#append-slash
From: django-developers@googlegroups.com
On Behalf Of Meiyer
Sent: Monday, September 19, 2022 8:59 AM
To: Django developers (Contributions to Django itself)
Please see:
https://docs.djangoproject.com/en/dev/ref/django-admin/#sqlsequencereset
Also, this question is more for the Django Users mailing list than the Django
Developers mailing list.
From: django-developers@googlegroups.com
On Behalf Of mohamad ali mehdizadeh
Sent: Wednesday, May 25,
I will always suggest that we use the Subquery API to make CTEs. To make them
recursive, just add a keyword argument (recursive=True) and/or use a union.
It’s been a while since I looked at CTEs, so I might be missing something.
I would hate to see us create an entirely separate API for CTEs.
I agree with Tim’s sentiment here. Had a solid SQL Server backend been
available 7 or 8 years ago, I would probably have used that due to the
requirements from my supervisor. I had to convince him that PostgreSQL would be
just as good.
Based on what I read on the Git page, though, the backend
Currently, I just use the migrations to do a RunSQL and then I make a model
with the Meta option managed set appropriately. It works for me, but perhaps
something a bit more convenient is in order these days.
From: django-developers@googlegroups.com
On Behalf Of Vasanth Mohan
Sent: Monday,
Ctrl + Break and Ctrl + C are treated slightly differently by Windows. Ctrl +
Break is always a signal, but an application can override the functionality of
Ctrl + C.
Please see
https://docs.microsoft.com/en-us/windows/console/ctrl-c-and-ctrl-break-signals
I’ve dealt with this issue many
I've had similar issues. I just avoid squashing anymore. It's just not with the
pain, and having so many little files that get looked at a minimal amount of
time isn't worth fretting over. Saying that, I'd love to get it fixed...
Sent from my Verizon, Samsung Galaxy smartphone
Get Outlook for
> Thoughts on deprecating it?
It seems like a good idea. However, it leads us to another question. Do we
really need the is_staff field on the User Model if it is deprecated?
From: django-developers@googlegroups.com
On Behalf Of Timothy McCurrach
Sent: Tuesday, March 9, 2021 3:22 PM
To:
The filter states that it expects plain text. In Python, str(None) = "None". To
get the behavior you are seeking use the default_if_none filter, and chain your
other filters.
https://docs.djangoproject.com/en/dev/ref/templates/builtins/#default-if-none
{{ text|default_if_none:""|linebreaksbr }}
Thank you so much for sharing that, Adam. I’ve always wondered what the best
way was to deal with names. The systems I work with should be able to handle
names from all countries of the world. I find you kalzumeus link only slightly
helpful, though. It explains what we shouldn’t do. I’d rather
It is my opinion that the Subquery object that already exists in Django should
act as a CTE.
There is a ticket for this feature already:
https://code.djangoproject.com/ticket/28919
I have noticed that several developers have proposed several different patches
for CTEs, but I do not know why
I did read your post, and I did come to that conclusion. I may have ultimately
misunderstood, and I’ll certainly take the blame for my own misunderstanding.
The example you provided can be done without multiple template inheritance. So
far, my thoughts on the design concept is that multiple
In your example, you could just inherit from generic-list.html since it already
extends base.html. You would be repeating yourself in your current example.
orders/list.html
{% extends 'generic-list.html' %}
{% block list-item %}
Order # {{ order.id }} (total: {{ order.total }})
{% endblock
It's an interesting idea, and I'm not opposed to it myself; however, keeping
the settings as Python code is not an abnormal practice compared to other
software.
I've been working with some Drupal stuff lately, and it is written in PHP.
Drupal is a content management system that can be extended
“In my opinion there are not many good reasons to have to change behaviour if a
request is made via XHR. I think the most common usage is to have a single view
that returns a JSON response or a HTML response depending on if XHR is used
(https://github.com/search?l=Python=request.is_ajax=Code),
I’d just like to point out that Redis support on Windows is limited at best.
All other technologies that Django uses, as far as I can recall, do support
Windows.
From: django-developers@googlegroups.com
[mailto:django-developers@googlegroups.com] On Behalf Of Jacob Rief
Sent: Thursday,
I had a use for such a feature, though I used an implementation more specific
to my application.
Basically, I have a model and then I have several other models that are
directly related to that model. So in the base model I would have a field to
determine if the instance was marked as deleted.
Just a thought: If Django were to adopt black (and I'm not saying it should),
shouldn't it wait until it is out of the beta classification?
-Original Message-
From: django-developers@googlegroups.com
[mailto:django-developers@googlegroups.com] On Behalf Of Markus Holtermann
Sent:
This is more for the ORM side of things. Something I would like to see is the
Subquery object morphed into the equivalent of common table expressions and the
possibility of having recursive common table expressions. See
https://code.djangoproject.com/ticket/28919.
The patches that I’ve seen
that to this day. I would love to become a more consistent
contributor, but my own lack of time prevents it.
Thank you,
Matthew Pava
From: django-developers@googlegroups.com
[mailto:django-developers@googlegroups.com] On Behalf Of Tim Graham
Sent: Tuesday, January 8, 2019 10:45 AM
To: Django
I think the idea is that some developers may have fields on their models called
“url” or “absolute_url” and having a property by that name would cause naming
conflicts. (Actually, I think I ran into this issue once with my own projects.)
Creating any property on a model in the Django core
Right. I just use python manage.py…
I just checked python3 manage.py and it doesn’t work.
From: collinmander...@gmail.com [mailto:collinmander...@gmail.com] On Behalf Of
Collin Anderson
Sent: Wednesday, April 11, 2018 7:46 AM
To: django-developers@googlegroups.com
Subject: Re: Shouldn't
> It includes ajax file upload which every user expects in the modern web which
> seems to be the feature which defines feature-completion of a UI framework,
> compared to what HTML offers out of the box.
Bandwagon logical fallacy (“every user expects”)
In my project, I have no need for file
Hi everyone,
I've been working on ticket 28643 specifically adding Ord, Chr, Left, and Right
to Django's built-in database functions. I've done the PR #9583. I am a new
contributor, and I've never really contributed code to any project through pull
requests ever before. I appreciate your
You asked me to join in on this conversation as I had an issue using Django
1.11. My third party apps do not yet all support Django 2.0.
I have an unmanaged model that is connected to a view in PostgreSQL. I
attempted to create an annotated version of the model manager using the
.annotate()
I wonder if we should put that in this ticket:
https://code.djangoproject.com/ticket/28643
From: django-developers@googlegroups.com
[mailto:django-developers@googlegroups.com] On Behalf Of Joey Wilhelm
Sent: Friday, November 17, 2017 2:02 PM
To: django-developers@googlegroups.com
Subject:
I handle that situation quite differently.
I have a model manager that annotates different fields to the queryset
depending on when I need them.
For your example, I would have something like this:
class CustomerQuerySet(models.QuerySet):
def with_allowed_to_drink(self):
return
I don’t use Field.validators much myself, but it seems that the Form clean
method also calls Field.validators, so the redundancy is already there in the
Form class. For consistency’s sake, I suggest we either add
Model.clean_fieldname(), or we remove Form.clean_fieldname(). Both suggestions
You might want to look at stuff that has already been developed. (No need to
reinvent the wheel, right?)
Check out this jQuery plugin for making a dynamic formset:
https://github.com/elo80ka/django-dynamic-formset
You might find some answers there.
From: django-developers@googlegroups.com
36 matches
Mail list logo
