eign key inside Profile and Post.
>
> Do I have another solution?
>
> --
> 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 sto
user
>
> I'd be happy to raise a ticket and work on a patch if this change would be
> useful.
>
> Thanks
> Mark
>
> [1]
> https://docs.djangoproject.com/en/dev/topics/auth/customizing/#custom-users-and-the-built-in-auth-forms
>
> --
> You received this messag
for it to
> get merged into core. I believe that instead targetting a smaller scope
> means we can at least provide a workable answer to the DATABASE_URL question
> in the near term. And when consensus coalesces around a good overall answer
> to settings, the actual URL parsing logic
;
Could you (or others) provide some examples of the needs this solution
doesn't address (not necessarily complete, just to give an idea)?
Many thanks,
Tobias
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself
[0] — and that would
>> likely be good enough.
>>
>> Can we move now?
>>
>> Thanks.
>>
>> Kind Regards,
>>
>> Carlton
>>
>>
>> [0]: I'd happily do this.
>>
>> --
>> You received this message because you are subsc
's a minor increment to my
> effort
> for a good return I think.)
>
>
> No urgency but, can I ask you to put your grey cells into action? 🙂
>
>
> Thanks.
>
> Kind Regards,
>
> Carlton
>
> --
> You received this message because you are subscribed to t
include folks from the wider ecosystem in previous years.
>> Two years ago
>> we had both Wagtail and django-stubs projects. Wagtail then (last year)
>> applied in their own right, to great success. I'd like to offer that
>> help
>> again to e.g. Jaz
gt; Florian
>>> On Friday, November 25, 2022 at 10:04:36 AM UTC+1 Mariusz Felisiak wrote:
>>>
>>>> Thanks!
>>>>
>>>> Reminder: according to DEP 10 voting will end on *December 2nd, 2022*
>>>> *AoE* (members of the Technical Boar
ve as a third-party package.
>>>
>>> - I've tried to include folks from the wider ecosystem in previous
>>> years. Two years ago
>>> we had both Wagtail and django-stubs projects. Wagtail then (last year)
>>> applied in their own right, to great s
I’m happy with this approach, it’s a little step forwards towards
maintainable settings files.
On Sun, 27 Nov 2022 at 20:37, 'Tobias McNulty' via Django developers
(Contributions to Django itself) wrote:
> Hi Raphael,
>
> Thanks for taking this on.
>
> Starting with a l
ond
> (optional) parameter named "instance"? The form could then just decide
> in __init__ if (user|instance) is present, and save the one that is
> present as self.user.
>
> This would ensure that the view could also call it with "instance", both
> would work.
Big +1 from me, I love the forum. It’s a lot more discoverable and powerful.
On Mon, 28 Nov 2022 at 15:22, 'Tobias McNulty' via Django developers
(Contributions to Django itself) wrote:
> As someone who only just joined the forum -- I'm +1:
>
>- The forum has seen gr
' via Django developers
(Contributions to Django itself) , wrote:
> As someone who only just joined the forum -- I'm +1:
>
> • The forum has seen great adoption from what I can tell (nearly half the
> number of posts as django-developers during the same time period, not bad
..
Cheers,
Tobias
--
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...@googlegrou
pattern. It's much more obvious to
>> me if e.g. `MIDDLEWARE` is configured in a single location and not modified
>> in other files.
>>
>> Thanks,
>> Matthias
>>
>>
>>
>>
--
You received this message because you are subscribed to the Goog
tter than having no
>>> timeout at all; especially because what the OP posted:
>>>
>>> > so at least if and when this happens, developers will find error
>>> traces in the logs and quickly understand where the problem is coming from,
>>> instead of spend
; --
> 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.co
d 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
hone
> user_profile_obj.address = address
> user_profile_obj.save()
>
> user_obj.username = username
> user_obj.email = email
> user_obj.save()
> user_obj.refresh_from_db()
>
> --
> You received this message because you are subscribed to the Goo
n
> fact justified, and which anticipated and addressed several arguments
> now being raised here. So I ask that people actually read and engage
> with that in future replies. This is the bare minimum of respect and
> good faith that can be expected of participants in discussions on thi
Manager()
> editors = EditorManager()
>...
>
> The first is more readable and nicer .. yeah ?
> Code is working and ready at github
> <https://github.com/django/django/compare/main...RamezIssac:django:feature/get_manager_shortcut>
> ,
>
> Do i get +1(s) to m
t;>
>>> I think it would be a good thing for progress on this issue to happen.
>>>
>>> You might also want to check the ticket history for any work on
>>> multi-value keys.
>>>
>>> --
>>> Curtis
>>>
>>>
>>> --
> You
responsibility to the front end.
>
> What do you folks think? I've been bitten by this issue several times, in
> a production environment after smoothly running for a while. The first time
> was a complete surprise to me, and I believe it's may surprise quite a lot
> of
to the life, universe and everything, whether a new
> t-shirt could be produced?
>
> Yours hopefully,
>
> Stephen
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsu
application can be referenced.
>
> --
> 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-develope
Django knowledge so I'd question whether it's worthwhile.
>
> I'm happy to contribute if advised on the preferred option.
>
> Cheers
> Mark
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Con
y the Disclaimer Terms of somaiya.edu
<http://somaiya.edu> which may be viewed at
https://www.somaiya.edu/en/email-disclaimer
<https://www.somaiya.edu/en/email-disclaimer>
Finally, please do not
print this email unless it is necessary. Every unprinted email helps the
environment.
ertainly don’t do the community
> > > any favours in terms of getting more people on board.
> > >
> > > Kye
> > > On 28 Nov 2022 at 11:40 PM +0800, 'Tobias McNulty' via Django developers
> > > (Contributions to Django itself) , wrote:
&
ribute.
> Please assign me a task or issue.
>
> --
> 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
>
an ORM age thingy, still think that a more
>> general impl covering other vendors as well might be more helpful.
>>
>> Cheers,
>> Jerch
>>
>>
>> [*] Again speculative (TM) - I know that Daniele Varrazzo does a really
>> great job in maintaining psycopg an
sure what would be the best / usual way for a user to
customize HttpRequest (get_raw_uri, build_absolute_uri) to deal with it.
Thanks,
Marc
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubsc
, **kwargs):
value = func(*args, **kwargs)
# change value appropriately
return value
return wrapper
On Tue, Jan 24, 2023 at 9:58 PM 'Marc Perrin' via Django developers
(Contributions to Django itself) wrote:
> Hi,
> I've been looking at the current su
will always be the "How do I start?" posts. The Forum at
>> least has a pinned post for that. ...
>>
>> On Thu, 19 Jan 2023 at 01:04, 'Kye Russell' via Django developers
>> (Contributions to Django itself)
>> wrote:
>>
>> Hi all,
>>
>&g
>> Another approach would be to move the functionality of method render
>> into the class AdminSite. This would
>> allow Django implementers to override the way, log entries are rendered.
>>
>> This would be a minimalistic change to the existing code base but would
>&g
uld
think.
https://forum.djangoproject.com/t/release-4-2a-async-querysets-with-prefetch-related/18767
baj
--
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
different
database table name for Group, I’d say that would be grounds to implement
your own Group model - which really isn’t much code.
Thanks,
Adam
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)"
[permission_class]
> return func(self, *args, **kwargs)
> return decorated_func
> return decorator
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe
Thank you
>>
>> with regards
>> Mohammed Shoaib S.T
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django developers (Contributions to Django it
>> ...
>> {{model.icon}} {{model.name}}
>> ...
>>
>> Final result:
>> [image: admin navbar.png]
>>
>> Maybe own icon could have even the parent app (AppConfig). And the model
>> icon could be in breadcrumbs.
>>
>> What do you think abou
ty must be strongly guaranteed, and I share the approach of
> keeping it as minimal as possible. It is probably easier to override Now in
> your project when needed but I would like to hear your feedback on this.
>
> --
> Matteo Vitali
> https://trottomv.me
>
> --
> You r
er. Can anyone help me for my first Open Source Contribution...?
>
> Thank you!
>
> Linktree: https://linktr.ee/siddhirajkolwankar
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)"
nores the environments, test files
>
> --
> 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-de
/vuejs/create-vue> generates one
>>>
>>> Perhaps it's time for Django to reconsider and catch up with the times?
>>>
>>> Cory
>>>
>>>
>>>
>>>
>>> On Fri, Mar 10, 2023 at 7:03 AM Mariusz Felisiak
>>> wrote:
&g
the same as `datetime.datetime`
> and that Django is definitely adding some magic here and I have to use
> `datetime` from Django. This is of course not true.
>
> Best,
> Mariusz
>
> --
> You received this message because you are subscribed to the Google Groups
> "D
github.com/shangxiao/stupid-django-tricks/tree/master/column_check_constraints>
>for some experimentation with this idea.
>
>
> Cheers,
> David
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions
> creating a new one.
>
> Initial -1 from me.
>
> Best,
> Mariusz
>
> --
> 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 ema
;> to me, I think it is worth discussing it in a separate issue or on the
>> developer mailing list."
>>
>> I remain of the opinion that continued attempts to automatically abandon
>> valid issues are not helpful and do not reflect project maintenance best
>>
7;s the Configuration with all detected errors types ignored.
> https://github.com/django/django/compare/main...obi-jerome:django:Ruff
>
> What do you think ?
> Is it done the proper way ?
>
> --
> You received this message because you are subscribed to the Google Groups
> "
Natalia.
>
> --
> 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+
=11,
>>> validators=[validate_phone_number])
>>> name = models.CharField(max_length=255)
>>>
>>> after adding a field "name" when i run "makemigrations --update" it
>>> shows a error:
>>>
>>> CommandError: Cann
s I'm aware you can use:
>
> CreateCollation("case_insensitive", "und-u-ks-level2",
> provider="icu", deterministic=False)
>
> to create a case insensitive collation on PostgreSQL.
>
>
--
You received this message because you are subscribed to the
oject.com/en/4.1/howto/deployment/
>
> --
> 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 dj
ase someone can create 3rd party package
>> with them.
>>
>> Unless something is fundamentally broken I'm against reverting.
>>
>> Best,
>> Mariusz
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>>
what do you think about this
> approach? Are there any other ideas or concerns?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group an
CSRF Middleware from the default settings template file?
--
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
'Adam Johnson' via Django developers
(Contributions to Django itself) wrote:
> Just to note, for anyone that finds it useful, that I wrote a blog post on
> migrating to collations:
> https://adamj.eu/tech/2023/02/23/migrate-django-postgresql-ci-fields-case-insensitive-collation/
>
Lowering the barrier to entry is worth a lot.
--
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-dev
uld at
>> least mention the need for the developer to handle this explicitly.
>>
>> Regards,
>> Arthur P.
>>
>>
>>
>> [1]
>> https://groups.google.com/g/django-developers/c/J5O28jB5D3Q/m/KLLgllFS7v0J
>> [2] https://docs.djangoproject.com/e
;st...@jigsawtech.co.uk' via Django
> developers (Contributions to Django itself) <
> django-developers@googlegroups.com> wrote:
>
>> As someone whose worked on various projects in different languages over
>> the last 15 years that heavily involved deciphering IP sent
;s likely
some details I'm missing in laying out this scenario, but it felt
interesting enough to mention in the context of this conversation.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
eprecate support for the db type, a 3rd party package
>> seems the bast choice for me.
>> With the downside of me having to maintain yet another package. But I can
>> understand if the Django project has no interest in maintenance.
>>
>> In any event, I opened a ticke
ds like too specific a note to add. Many different data types in
many different databases fail to work with some existing lookups, such as
several custom fields in Django-MySQL:
https://django-mysql.readthedocs.io/en/latest/model_fields/index.html
On Sat, May 6, 2023 at 9:50 AM 'Johannes Maro
ForeignKey(author_cls,
> on_delete=models.CASCADE)
>
> class Author(models.Model):
> name = models.CharField(max_length=256, unique=True)
>
> class Book(BaseBookModel, author_cls=Author):
> pass
>
> --
> You received this message because you are subscribed to the Google Grou
e fields (in the screenshot "Lokaler Zeitpunkt" and
> "Bewertung"), but not the text below the values.
>
> May this be reconsidered?
>
> Best regards,
> Carsten
>
> --
> You received this message because you are subscribed to the Google Groups
> &qu
developers
(Contributions to Django itself) wrote:
>
> What I am struggling now with is whenever I specify
>> `db_collation="case_insensitive"` on the field and this field is used in
>> `ModelAdmin.search_fields` - Django simply breaks (as it by default uses
>> `icontain
asy for them to answer.
Thanks for your understanding and all the best,
Adam
On Sat, Jun 10, 2023 at 11:37 AM Atul Tiwari
wrote:
> solve this
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django it
work.
>>>
>>> Shouldn't this be a complete feature?
>>>
>>> I've re-checked https://docs.djangoproject.com/en/4.2/howto/deployment/
>>> and there's no information on the topic (that I could find).
>>>
>>> Arthu
lass to customise class creation, hence this PR.
>>>>
>>>> Hope that makes sense and appreciate any feedback. Thanks!
>>>>
>>>>
>>>> class BaseBookModel(models.Model):
>>>> class Meta:
>>>> abstract = True
>>
x27;management/', include('apps.management.urls')),
>
> # native admin URLs
> path('', admin.site.urls), # must be last if admin URL is empty!
> ]
>
> Notice that I had to add the extra
>
> *path('accounts/password_reset/', Pass
in/docs/ref/models/class.txt
> - https://github.com/django/django/blob/main/docs/topics/db/models.txt -
> perhaps within a new subheading in the Model inheritance section?
>
> Once confirmed I'll amend the PR
>
> Thanks
>
>
> On Wed, 28 Jun 2023 at 10:28, 'Adam
e
> the kwarg `reason`
>
> which is extremely minimal risk, and should be anyway easily detected
> through already present testing
>
> Do I have go ahead to propose a PR?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django
://proton.me/) secure email.
--- Original Message ---
On Monday, August 7th, 2023 at 14:09, 'Adam Johnson' via Django developers
(Contributions to Django itself) wrote:
> This sounds reasonable, but unfortunately, it's backwards incompatible and so
> we cannot ma
le, so I suggest that an *AdminSite.ui_toggle* (or the like) boolean
>> be added. What do you think?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe fr
2000 :-)
>>
>> Anyway, tornado to talk about Database, SQL Server is a third-party package
>>
>>>> I, therefore, suggest that we start a discussion on removing Oracle from
>>>> supported databases.
>>> This was already discussed. I'm still s
the admin theme, and that
>>>>>> is
>>>>>> if I heavily customized it. I haven't found a way to disable that
>>>>>> specific
>>>>>> toggle, so I suggest that an *AdminSite.ui_toggle* (or the like)
>>>>
this journey would be a tremendous help.
>
> I'm excited about the potential to collaborate and contribute. Thank you
> for considering my inquiry.
>
> Warm regards,
>
> Nikita Bansal
>
> --
> You received this message because you are subscribed to the Google Gro
temporary solution to provide an
> async interface when we don't have all async elements ready.
>
> Best,
> Mariusz
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
>
PR to alter the documentation, to point
> towards this option. This should allow users to choose, and will probably
> easy migration to Django 5 for some.
>
> But first, I gotta play Tears of the Kindom….
>
> Cheers!
> Joe
>
>
> On Fri, May 12, 2023 at 1:37 PM 'Ad
re of that. Some help would be great!
>
>
> --
> 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
> ema
hon.
>
> It's not technical, but something that I noticed along the way.
>
> What do you folks think? Do you have any recommendations?
>
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developer
> Best,
> Mariusz
>
>
> --
> 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-
n
>> detail
>> https://stackoverflow.com/questions/77280149/not-able-to-upload-file-to-django-server-from-service-worker-in-react-js
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django developers (
ions scheduling updates.
>
> Thanks for considering this, and for the awesome work on making Django better
> and better!
>
> Warm regards,
> Wim
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developer
f.stop()
>
> klass.setUpClass = setUpClass
> klass.tearDownClass = tearDownClass
>
> return klass
>
> def decorate_callable(self, callable_obj):
> @functools.wraps(callable_obj)
> def wrapper(*args, **kwargs):
>
ted tests
>>
>> Ah well, just some quick thoughts on that...
>>
>> Cheers,
>> Jörg
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django developers (Contributions to Django itself)" gr
ok forward to hearing
> your thoughts and suggestions. Let's discuss how we can make Django even more
> powerful in the realm of real-time communication!
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (
;>>> If you have any other pointers, feel free to leave an issue report.
>>>>
>>>> Thanks!
>>>> Joe
>>>>
>>>>
>>>> On Fri, May 12, 2023 at 5:19 PM Johannes Maron
>>>> wrote:
>>>>
>>>&g
False" settings.TIME_INPUT_FORMATS seems to be
>>> ignored.
>>>
>>> How does one use settings.TIME_INPUT_FORMATS ?
>>>
>>> Arthur Pemberton
>>>
>>>
>>> --
>>> You received this message because you are sub
similar issues, or knowledge of potential Django nuances
that we might not be considering would be incredibly valuable.
We appreciate your time and any feedback or suggestions you can offer.
Thanks
Bill
django v5.0.2
python 3.12.2
db is postgres
--
You received this message be
auto_now_add fields.
From: 'William Palin' via Django developers (Contributions to Django itself)
Sent: Sunday, March 17, 2024 9:59 AM
To: Django developers (Contributions to Django itself)
Subject: Intermittent IntegrityError on Model Save with auto_now and
auto_now_add Fields
He
sue
> between auto_now and auto_now_add fields.
>
>
>
> *From:* 'William Palin' via Django developers (Contributions to Django
> itself)
> *Sent:* Sunday, March 17, 2024 9:59 AM
> *To:* Django developers (Contributions to Django itself) <
> django-d...@goo
difficult to parse properly.
--
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.co
o:django-developers%2bunsubscr...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/726fce28-2273-4672-8e00-f8619b95b0d9%40netzkolchose.de.
>
--
You received this message because you are subscribed to the Google Groups
&q
x27;re on your way, but I'm
here trying to help, and I've got a record of doing so here and elsewhere
in various ways.
Sorry to others here for the off topic response. Though I probably should,
I can't let that kind of comment go in the Django discussion group.
Thank y
tibility (for API users):* django.core.mail largely
>>>> insulates callers from the underlying Python email package. There are a
>>>> few places where this leaks (e.g., attachments
>>>> <https://docs.djangoproject.com/en/5.0/topics/email/#django.core.mail.E
<https://github.com/nekonaq/djangoexpack/blob/6ad39bb305cbac7cafbbc323a9db21830f69b811/djangoexpack/mail/__init__.py#L34>
>>>• Proposal: remove without deprecation
>>> • *ADDRESS_HEADERS* is not documented, not exposed in django.core.mail
>>>• Used to implem
י
> u...@speedy.net
>
>
> --
> 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
ware would ever become a default-enabled middleware,
>> since people would probably be upset about suddenly having their sites
>> login-walled by a Django upgrade.
>
> OK, I understand. Thank you. I read the documentation but I misunderstood and
> thought that LoginRequired
to make celery working again on
windows so that the developers can use it effeciently and produces
more productivity
Regards
--
You received this message because you are subscribed to the Google
Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this
ps://firebirdsql.org/en/community-news/django-firebird-driver-update-for-django-5/
>
>
> --
> 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
101 - 200 of 554 matches
Mail list logo